mobile-app-engineering

Produce a reproducible signing, versioning, and store-declaration pipeline so an iOS or Android build passes App Store Connect / Play Console submission. Use when building or uploading a distribution .ipa/.aab, fixing signing/provisioning-profile or entitlement errors, bumping CFBundleVersion/versionCode, filling App Privacy / Data safety forms or PrivacyInfo.xcprivacy, wiring Fastlane lanes, or diagnosing a store rejection. Do NOT use for general (non-mobile) release steps like changelogs, tagging, or backend deploys — use prepare-release instead; do NOT use for store listing titles, descriptions, or keywords — use app-store-copy instead.

Architects Flutter widget trees and Riverpod or Bloc state so rebuilds are scoped, build() stays pure, and const widgets skip recomposition. Use when building or refactoring Flutter screens in .dart files, fixing jank or rebuild storms, choosing between Riverpod and Bloc, or wiring StatelessWidget/StatefulWidget, Consumer, or BlocBuilder. Do NOT use for Android Jetpack Compose UI — use jetpack-compose-builder instead; do NOT use for React Native — use react-native-pro instead.

Builds Android Jetpack Compose UI with hoisted state, unidirectional data flow, and recomposition-safe patterns. Use when writing or refactoring @Composable functions, Compose screens in Kotlin/.kt files, ViewModel/StateFlow wiring, LazyColumn lists, or fixing Compose recomposition jank. Do NOT use when the screen targets Flutter or a generic cross-platform mobile UI — use flutter-widget-architect instead.

Build local-first mobile storage with an optimistic local store, durable mutation outbox, deliberate conflict resolution, incremental pull, and idempotent background retry. Use when a mobile feature must keep working offline, when edits made offline must reconcile with the server later, or when reconciling a local database (Room, SwiftData, SQLite, Realm) against server state. Do NOT use for simple response caching of read-only data or for strong-consistency operations like payments and inventory counts — disable those offline instead.

Diagnoses and fixes mobile jank, dropped frames, and growing memory by capturing a trace or heap snapshot, isolating the worst frame or leak, fixing it, and re-measuring against the frame budget. Use when a mobile app stutters or drops frames, scrolling a long list is slow, memory grows over repeated navigation, or the UI feels laggy on a real device. Do NOT use when the bottleneck is a server-side or web hot path (slow endpoint, query, render time) — use optimize-performance instead.

Wires native mobile push end to end on APNs and FCM — device-token registration, alert and silent payloads, permission priming, server send path, and tap routing into the app. Use when you are adding push to an iOS or Android app, debugging why a push never arrives or never wakes the app, wiring the .p8/service-account server sender, or handling a notification tap. Do NOT use for web/browser push (Web Push/VAPID), in-app banners, or platform notification dashboards — and for navigating a tapped payload into a specific screen, use a deep-link router instead.

Build and ship production React Native apps.

Build clean, performant, accessible SwiftUI views.