Plan & design
Feature scope, state ownership, and API contracts.
Moin Omer Habib
Senior Mobile
Engineer.
AI-Assisted Engineering · 10 Years
I build reliable mobile products with AI-assisted planning, implementation, testing, and telemetry-driven debugging.
Based in Pakistan · Open to European remote roles and relocation with sponsorship.
Let's talk →
10 yearsMobile engineering experience
MillionsUsers of products I’ve contributed to
99.2%+Crash-free sessions on edX Android
Featured project · AI-assisted mobile engineering
AI-Assisted Mobile
Engineering Playbook.
My AI-Assisted Mobile Engineering Playbook brings reusable agent skills, a Kotlin/Compose client, and a Node.js expense-claims demo into one practical workflow—from a feature brief to reviewed, tested changes.
AI-assisted build
Focused tasks with engineer review.
Verify & deliver
UI/API tests, CI evidence, PRs, and artifacts.
Debug & improve
Events + request IDs → reproduce → fix → regression checks.
01 / From idea to reviewed delivery
AI supports the work. Acceptance criteria, engineer review, and automated checks guide what gets accepted.
- 01 / DEFINE
Feature brief
Scope, acceptance criteria, offline behavior, and failure cases.
- 02 / DESIGN
State & API contracts
Ownership, response types, persistence, and retry guarantees.
- 03 / IMPLEMENT
AI-assisted changes
Bounded implementation tasks grounded in the agreed contracts.
- 04 / REVIEW
Engineer review & PR
Check correctness, document evidence, and use Conventional Commits.
- 05 / VERIFY
GitHub Actions
API and browser UI checks, plus Android build, lint, and unit tests.
- 06 / PREPARE
Artifacts & release plan
Package reviewed changes and define recovery before release.
When checks fail: logs + request IDs → reproduce → fix → review and verify again.
How AI makes everyday work easier.
Less time starting from a blank page. More time for product decisions, architecture, and verified delivery. These are practical ways AI can support an engineer’s day.
From request to action
Turn client notes into a feature brief, clarify missing requirements, surface edge cases, and prepare a task plan for team discussion.
Code, tests & review
Draft focused implementation options and Given–When–Then tests, explore unfamiliar code, and use review prompts to catch gaps before a PR.
Find the next useful check
Organise sanitised logs and request IDs into a timeline, propose hypotheses, and turn a reproduced failure into regression coverage.
Communicate & learn
Prepare PR descriptions, release notes, meeting summaries, and clear technical explanations. Use structured practice to learn a new concept.
My working principle: AI helps draft and investigate; I validate behavior, review code, and own the final decisions. Sensitive client data stays out of prompts.
Explore the system architecture, debugging & agent skills
02 / A claim that can survive a retry
The expense-claims demo explores offline recovery and a lost server response without creating a second claim.
Client interface
Kotlin / Jetpack Compose
or mobile web client
Shows loading, success, and recoverable failure states.
State & pending claim
Save the payload and operation key before sending.
Persistent storage
Android: SharedPreferences
Web: localStorage
Android: SharedPreferences
Web: localStorage
Node.js claims API
Retry with the same key and payload to retrieve the original result.
Process-local idempotency store
Replay returns the same claim ID.
Replay returns the same claim ID.
Debugging loop: client state events + server request ID → correlated timeline → regression test.
03 / Debug with analytics & telemetry
Use evidence from the client and API to understand where a submission failed, then verify the fix.
Collect the signals
Client state transitions and failure events, alongside server logs and request IDs.
Capture the outcome and context.
Keep amounts, tokens, and personal details out of events.
Keep amounts, tokens, and personal details out of events.
Correlate the timeline
Connect client behavior to the server response. Check what happened before the failure.
Example investigation
Did the server accept the claim while the response was lost?
Did the server accept the claim while the response was lost?
Reproduce & fix
Test the hypothesis, make a bounded change, and review the affected contracts.
Confirm recovery
Retry the original operation without creating a duplicate.
Retry the original operation without creating a duplicate.
Close the loop: fix → API + UI regression checks → CI evidence → engineer review.
Plan the feature
Turn requirements into acceptance criteria and a practical task plan.
Design the contracts
Define state ownership, API behavior, caching, and safe retries.
Review the change
Inspect lifecycle, concurrency, error handling, and implementation risks.
Verify delivery
Map Given–When–Then cases to unit, UI, and API checks.
Debug with telemetry
Use logs, request correlation, and reproductions to verify a fix.
Ship with GitHub Actions
Prepare Conventional Commits, PRs, CI evidence, and artifacts.
One coordinator skill connects the six focused workflows into the full delivery process.
Featured Projects.
edX Android App (Open edX)
edTech
edX / Open edX
Kotlin & Compose modernization · Mobile learning at scale
Built and maintained the Android learning experience for a global education platform. Contributed to Java → Kotlin → Compose modernization, modular architecture, and video playback analytics. Integrated WebView course content with JavaScript injection, file uploads, notifications, and offline support.
Cheetay Android App
Food Delivery, Logistics
Cheetay Delivery
Java-to-Kotlin migration · Maintainability & performance
Modernized and stabilized a high-traffic delivery platform. Led the transition to Kotlin and Clean Architecture modules, reducing the crash rate from ~6% to under 0.8%. Enhanced cart, checkout workflows, and real-time rider tracking.
CERP Survey App
Data Collection, Research
CERP Survey
Offline-first field data collection · Room & secure uploads
Built a custom Android app for field data collection. Designed for offline-first usage with an encrypted Room database. Integrated BLE device support for biometric data and handled complex UI flows with dynamic form generation.
Sentimeter Feedback Kiosk
Retail, Customer Experience
Sentimeter Kiosk
Customer feedback · Firebase & localized kiosk experiences
Created a kiosk-mode feedback app locked to a single-app mode with remote config support. Enabled real-time survey updates, Firebase remote logging, and robust offline operation with delayed sync.
About Me.
I'm a Senior Mobile Engineer with 10 years of experience building mobile products used by millions. My core expertise is Android, Kotlin, Jetpack Compose, and maintainable architecture, complemented by cross-platform, hybrid, and backend work.
My work spans the Open edX Android ecosystem, React Native features, Angular and Ionic apps, and WebView integrations. I've also built PHP REST APIs integrated with Moodle and worked on a Node.js reimbursement claims portal. I collaborate with international product teams on architecture, reliable delivery, and mentoring.
I use AI for planning, implementation, code review, and test design. My AI-Assisted Mobile Engineering Playbook connects reusable agent skills with UI/API testing, GitHub Actions, and telemetry-assisted debugging. Engineer review and verification guide acceptance.
Experience highlights & engineering practices
Key Highlights
- Maintained 99.2%+ crash-free rate
- Led code reviews to ensure quality and team standards
- Led CI/CD adoption and improved release workflows
- Migrated apps from Java to Kotlin & XML to Jetpack Compose
- Mentored developers and led Compose migration initiatives
- Delivered critical features for global edTech & finTech platforms
Open Source Contributions
-
Open edX Android App
Official Contributor
- Migrated legacy code to Jetpack Compose & Kotlin
- Improved app performance and accessibility
- Worked on modularization & clean architecture
Engineering Practices
Process & Quality
- Agile Methodologies Proficient in Scrum and Kanban for iterative and collaborative development.
- Clean Code & Performance Committed to Clean Code principles and performance optimization for robust applications.
- Scalable Architecture A strong focus on creating testable, scalable, and maintainable app architectures.
Collaboration & Delivery
- Code Reviews & Mentorship Lead constructive pull request reviews and mentor junior developers to elevate team skills.
- Team Collaboration Skilled in project estimation, cross-functional team collaboration, and communication.
- Continuous Learning Actively explore emerging Android technologies to drive innovation and modern practices.
Engineering expertise
Native Android
Kotlin · Java · Jetpack Compose · XML · Material 3
Architecture & async
Clean Architecture · MVVM · Modules · Coroutines / Flow · Hilt
Cross-platform & hybrid
React Native · Ionic / Angular · WebView · JavaScript bridges
Backend & APIs
Node.js · PHP · Moodle APIs · REST · Retrofit / OkHttp
Testing & delivery
JUnit · MockK / Mockito · Espresso · GitHub Actions · Play Console
AI & production insight
Agent skills · AI-assisted review · UI / API verification · Crashlytics · Analytics
Beyond Native Android.
Cross-platform delivery, hybrid integration, and practical backend development.
Schoolgram & Cross-Platform Apps
Angular · Ionic · React Native
Led Schoolgram development with Angular and Ionic, delivering a shared codebase for Android and iOS. Additional cross-platform work includes React Native features and Workstream.
Hybrid Apps & Learning APIs
WebView · JavaScript · PHP · REST APIs
Integrated web course content with native Android capabilities, including input handling, file uploads, notifications, and offline support. Built PHP REST APIs integrated with Moodle for education features.
Reimbursement Claims Portal
Node.js · Backend Development
Worked on an ERP portal covering expense reimbursement, claims, and authentication. This experience complements my mobile work with practical understanding of backend workflows and API boundaries.
System design + cross-team delivery
From a feature request
to production feedback.
Reliable delivery connects product thinking, system design, mobile implementation, and production operations. This is the complete cycle I use to structure feature work—with shared decisions and clear evidence at each handoff.
Client or product request
A user need, business requirement, or new capability.
Data-informed opportunity
Analytics, support feedback, or production behavior reveals an improvement.
Discover
Requirements, success metrics, and cross-team alignment.
Design
UI/UX, API contracts, and system boundaries.
Build & verify
Mobile implementation, testing, review, and CI.
Release & learn
Deployment, A/B rollout, analytics, and iteration.
Explore the full 12-step delivery cycle
Phase 01
Discover
- 01
Gather requirements
Understand the problem, users, business goal, and functional and non-functional needs.
Product · Client · Engineering - 02
Agree scope & success
Define acceptance criteria, edge cases, constraints, and success metrics. For experiments, agree the hypothesis and guardrails.
Product · Engineering · QA - 03
Align the teams
Discuss dependencies, ownership, risks, and delivery milestones across mobile, backend, design, and QA.
Cross-team collaboration
Phase 02
Design
- 04
Finalise UI & UX
Review flows, prototypes, accessibility, and loading, empty, offline, and error states.
Design · Product · Mobile - 05
Agree API contracts
Define payloads, response models, status codes, authentication, pagination, and retry behavior.
Mobile · Backend - 06
Design the system
Define state ownership, module boundaries, persistence, sync, security, and compatibility.
Mobile · Backend · Platform
Phase 03
Build & verify
- 07
Implement mobile
Build the UI, state handling, repository integration, local storage, and feature telemetry.
Mobile engineering - 08
Test the behavior
Validate acceptance criteria through unit, UI, API, integration, and regression checks.
Engineering · QA - 09
Review & validate CI
Review correctness and maintainability; resolve findings and require relevant checks to pass.
Reviewers · GitHub Actions
Phase 04
Release & learn
- 10
Prepare deployment
Coordinate backend readiness, environment configuration, API compatibility, and recovery steps.
Backend · Platform · Mobile - 11
Controlled rollout & A/B tests
Use staged releases and feature flags. For A/B tests, assign variants to eligible users, compare agreed outcomes, and monitor stability guardrails.
Mobile · QA · Product - 12
Observe & improve
Compare experiment results alongside stability, performance, feature events, and feedback. Use the evidence to expand, adjust, or stop a rollout.
Engineering · Product · Analytics
The cycle continues: production analytics + user feedback → investigate and prioritise → refine requirements → the next iteration. Urgent failures feed into debugging, a verified fix, and a safe release.
Reviews and cross-team collaboration continue throughout the cycle. Staged rollout manages exposure; A/B testing compares feature variants. Success metrics, experiment criteria, and release recovery are agreed before rollout.