The choice between native and cross-platform is mostly about device features and team shape. If the app is largely forms, lists, maps and payments, a shared codebase in React Native or Flutter covers both stores well. If it depends on low-latency audio, complex graphics or new operating system features, native code pays off.
Consider who will maintain it. A cross-platform app still needs people who understand each platform’s build tools, signing and quirks. Mixing approaches is common: shared screens with native modules for the few demanding features.
Store policy shapes the product
Apple and Google review every release against published policies. Rules on in-app purchases, sign-in options, account deletion, user-generated content moderation and sensitive categories such as health, finance and gambling can change which features you build and how you charge.
Read the relevant sections while scoping and keep a short compliance checklist for each release. Prepare reviewer notes and demo accounts in advance, since unclear functionality is a common cause of delay.
Designing for unreliable networks
An offline-first app stores data locally and syncs in the background, so screens load instantly and actions are not lost. That needs a local database, a queue of pending changes and rules for conflicts, such as last write wins or server decides.
Not every app needs full offline support, but every app needs graceful behaviour: cached content, clear status when actions are pending, retries with back-off and forms that survive being interrupted.
Permissions, notifications and trust
Each permission should be requested when the user reaches the feature that needs it, after a short explanation in your own words. A refused permission should leave the app usable, with a route back to settings when the user changes their mind.
Push notifications are powerful and easily abused. Let users choose categories, respect quiet hours and measure opt-out rates. A notification strategy that annoys people leads to disabled alerts and uninstalls.
Release management as a feature
Mobile releases cannot be rolled back instantly like a website. Staged rollouts, feature flags controlled from the server and remote configuration let you limit damage and switch features off without a new build.
Crash reporting and performance monitoring from the first beta show problems on devices you do not own. Track crash-free sessions, start-up time and failed network calls per release.
What drives mobile cost
Cost grows with the number of platforms, the range of devices and operating system versions supported, offline sync, real-time features, and integrations with hardware such as Bluetooth devices or wearables.
Ongoing work matters as much as the first build. Each yearly operating system release brings changes, deprecations and new review requirements, and dependencies need updating to stay supported. Budget for maintenance from the start.