1. Native vs cross-platform
Why it matters: The wrong stack choice locks you into higher burn for years — or under-delivers on performance and platform UX.
What it affects: Performance, UI fidelity, hiring, release cadence, and total cost of ownership. We score fit across iOS, Android, Flutter, and React Native against your roadmap — not our bench.
Affects: architecture · budget · timeline · UX
2. MVP vs full product
Why it matters: Shipping everything in v1 delays learning. Shipping too little fails the market test.
What it affects: Scope, first-release date, and whether the foundation can absorb the next three releases without a rewrite.
Affects: timeline · budget · scalability
3. Backend architecture
Why it matters: A thin BaaS may be enough for an MVP; a multi-tenant API with queues and workers is not optional for marketplaces, logistics, or regulated products.
What it affects: Scalability, ops cost, integration surface, and how hard later modules are to add.
Affects: architecture · scalability · maintainability
4. Authentication and user roles
Why it matters: Consumer OTP is trivial; enterprise SSO, multi-role permissions, and audited access are not bolt-ons.
What it affects: Security model, admin tooling, compliance reviews, and onboarding UX.
Affects: security · UX · compliance
5. Offline-first requirements
Why it matters: Field, logistics, and emerging-market apps fail when they assume always-on connectivity.
What it affects: Local storage, sync conflict rules, QA matrix, and perceived reliability.
Affects: architecture · performance · UX
6. Real-time functionality
Why it matters: Chat, live tracking, bidding, and presence need sockets or streams — polling will not hold under load.
What it affects: Infra cost, battery use, backend complexity, and device testing depth.
Affects: architecture · budget · performance
7. Payment architecture
Why it matters: Store IAP rules, subscriptions, marketplaces, and payouts each carry different compliance and chargeback risk.
What it affects: Revenue model, PCI scope, store policy risk, and refund/ops workflows.
Affects: budget · security · compliance
8. Push notifications
Why it matters: Generic blasts get muted. Event-driven, preference-aware pushes drive retention — and require clean event taxonomy.
What it affects: Engagement, privacy consent, and marketing/ops tooling.
Affects: UX · maintainability
9. Analytics and event tracking
Why it matters: If you cannot measure funnel drop-off, you cannot prioritize the next sprint.
What it affects: Product decisions, A/B readiness, and privacy/compliance obligations.
Affects: UX · maintainability · compliance
10. Third-party integrations
Why it matters: Maps, CRM, ERPs, KYC, and messaging vendors dominate timeline risk when contracts and sandboxes lag.
What it affects: Schedule, contingency budget, and failure modes when a vendor is down.
Affects: timeline · budget · maintainability
11. AI: on-device vs cloud
Why it matters: On-device models protect privacy and latency; cloud LLMs unlock richer reasoning at ongoing token cost.
What it affects: Latency, privacy posture, infra spend, and model-update strategy. See our AI-powered mobile apps practice when intelligence is core to the product.
Affects: architecture · budget · performance · security
12. Security and compliance
Why it matters: Healthcare, fintech, and enterprise buyers will not accept “we’ll harden later.”
What it affects: Encryption, audit logs, retention policy, penetration-test window, and launch blockers.
Affects: security · compliance · timeline · budget