make room for it.
I build the architecture, release path, and production feedback that make repeated delivery safer, not harder.
AI-first mobile engineer
I ship mobile products that hold up at scale.
Flutter, native platforms, and AI-assisted delivery for products used by 100K+ people.
Decision briefClarity before complexity
- Constraint
Protect what the product cannot compromise.
- Decision
Make the trade-off visible and actionable.
- Evidence
Verify the result against production behaviour.
Accountable pathReady for production
100K+users supported
10K+daily watch users
5+years shipping
From product architecture to production triage, across iOS, Android, and watchOS.
Selected product systems
Real products, real constraints, and the engineering decisions behind their delivery.
Clear boundaries keep the product changeable.
Interface, state, domain, and data move as one system without becoming one tangled system.
Native power where Flutter needs backup.
watchOS, StoreKit, secure storage, and platform channels, integrated without compromising the product.
Signals close the loop after release.
Observable, recoverable delivery turns production feedback into the next reliable release.
Engineering range
One owner across the mobile product lifecycle.
01
Architecture that stays changeable
BLoC, Riverpod, Provider, MVVM, and boundaries chosen for the product instead of habit.
UI State Domain Data
02
Native when it matters
Swift, watchOS, secure storage, platform channels, and app hardening.
03
Revenue-critical flows
Stripe, RevenueCat, subscriptions, authentication, and recoverable failure states.
04
Production is part of development
Sentry signals, structured errors, CI/CD, store delivery, and issue triage are built into the work, not left for launch week.
One stack, from interface to intelligence.
The product, backend, data, delivery, and AI tools I use to move from an idea to a monitored release.
Mobile and web interfaces
Cross-platform product work with native depth where the platform experience demands it.
- Flutter
- Dart
- React Native
- React
- Expo
- Swift
- Kotlin
iOSAndroidwatchOSResponsive UIAccessibility
Services that support the product
Runtimes, typed APIs, and integration layers that keep client experiences connected and recoverable.
- Node.js
- Elysia
- .NET
- Python
- TypeScript
- GraphQL
REST APIsWebhooksOAuth2 / OIDCJSONSecure storage
Signals before and after release
Persistence, analytics, messaging, and telemetry that turn product behavior into useful decisions.
- Firebase
- MongoDB
- PostgreSQL
- Mixpanel
- OneSignal
- Sentry
Cloud FirestoreSQLProduct analyticsPush notificationsCrash reporting
From feature branch to store release
Commerce, automation, security, and release tooling across the production delivery path.
- RevenueCat
- Stripe
- Codemagic
- Git
- GitHub
CI/CDStore deliverySubscriptionsVAPT deliveryProduction triage
A faster loop with accountable review
Agents and developer tools accelerate exploration, implementation, testing, and review without outsourcing judgment.
- Codex
- GitHub Copilot
- CodeRabbit
- Cursor
- Claude
- Android Studio
- Xcode
- VS Code
Prompt engineeringAgentic workflowsTest designCode reviewTechnical direction
AI speeds up the loop. Engineering judgment closes it.
I use agents for exploration, test design, review, and repetitive implementation. Architecture, security, and release decisions stay accountable to a human.
Explore
Compare approaches before code hardens.
Verify
Tests and platform behavior settle the argument.
Ship
Small, observable releases reduce risk.
Architecture with intent. Delivery with discipline.
Writing from the work
Practical engineering articles across mobile, backend systems, agentic AI, automation, and technical leadership.
Debugging StoreKit 2 JWS verification in Flutter
A practical path from an opaque subscription failure to a testable verification boundary.
Read 1 min readWhat changes when a watch app reaches 10K+ daily users
Reliability becomes a product feature when small sync assumptions turn into visible friction.
Read 1 min read