About the work A large consumer-facing mobile product is being rebuilt from the ground up as two fully native applications. The existing app was built on a cross-platform framework; the current iOS and Android apps will be independent native codebases. This role owns the technical shape of both.
The role You are the single technical owner across both platforms. You set the architecture, the module boundaries, the API contract, the testing strategy and the release process, and you write production code on both platforms while doing it. This is not a design-and-hand-off role — roughly half your time is in the codebase.
You will be the person the platform leads escalate to, the person who decides when the two apps should converge on a pattern and when platform idiom should win, and the person accountable for the two codebases not drifting apart over the life of the program.
What you will own
End-to-end architecture for both native applications: layering, modularization, dependency and navigation strategy, state management




The client-facing API contract — an OpenAPI specification treated as the source of truth, with generated Swift and Kotlin client SDKs — and the working relationship with the backend team that keeps it honest
Authentication and session architecture, secure credential storage, and token lifecycle across both platforms
Offline behavior and data synchronization strategy, including how conflicts are resolved and how it is implemented consistently on both sides
CI/CD, signing, release trains, staged rollout, feature flagging and kill-switch capability
Migration and coexistence strategy while the outgoing app remains live in both stores
Technical standards, code review culture, and the definition of done that the platform teams work to

Required
10+ years building mobile applications, with production ownership on both iOS and Android — genuine depth on each, not familiarity with one and a passing knowledge of the other
Current Swift: Swift 6 la

📌 Mobile Architect Chennai
🏢 Bounteous Digital
📍 Chennai