Native or React Native / Flutter — which should I choose?
Native (Swift + Kotlin): Highest performance + access to Apple/Google's newest features (e.g. Live Activities, App Clips, Material You). Preferred for: games, AR, video editors, 1M+ user projects, regulated fintech/health. Cross-platform (React Native / Flutter): 50% cheaper + single codebase + 2x faster development. Preferred for: MVPs, e-commerce, B2B field apps, content apps. We recommend based on your specific scenario in the discovery call — we won't push native if there's no need.
How does the Apple/Google in-app purchase commission work?
Digital goods (subscriptions, credits, premium content) sold inside the app must use Apple IAP / Google Play Billing — 30% standard commission, dropping to 15% under the Small Business Program (under $1M/year revenue; we handle enrollment for both stores, and Apple's subscription rate also falls to 15% after a subscriber's first year). Physical goods and real-world services (e-commerce, food delivery, bookings) are exempt — they run through Stripe/PayPal with no store commission. Post-ruling external purchase links have opened up on iOS in the US as well. We architect your payment routing around these rules so you keep the maximum share.
Children will use our app — what does COPPA require?
COPPA applies to apps directed at children under 13 (and to knowingly collecting their data). It requires verifiable parental consent before collecting personal information, no behavioral advertising to kids, a kid-appropriate privacy policy, data minimization and deletion rights. The FTC actively fines violators — settlements have reached tens of millions. Apple's Kids Category and Google Play's Families policy add their own rules (no third-party trackers, curated ads only). We've shipped COPPA-compliant builds and design the consent flow, SDK diet and store submission for the Kids/Families track from day one.
What do CCPA/CPRA mean for our app?
California's privacy law (strengthened by the CPRA) gives users the right to know, delete, correct, and opt out of the sale or sharing of their data. If your app crosses the thresholds, you need: a "Do Not Sell or Share My Personal Information" link, Global Privacy Control (GPC) signal handling, a data-deletion endpoint, third-party SDK disclosure and an up-to-date privacy policy. Other states (Colorado, Virginia, Texas and more) now follow the same pattern. Our builds ship with a CCPA/CPRA-safe analytics configuration and consumer-rights flows as standard — the same setup satisfies Apple's privacy nutrition labels and Google's Data Safety form.
We want to send push notifications and SMS — what is TCPA and why should I care?
The TCPA governs automated calls and SMS marketing — sending texts without prior express written consent exposes you to statutory damages of $500-$1,500 *per message*, and class actions are a cottage industry. Our builds capture express consent with timestamped records at opt-in, include clear opt-out (STOP) handling via Twilio, and keep marketing pushes behind a separate toggle from transactional notifications. Push notifications also require the OS-level permission prompt — we sequence it for maximum opt-in rates without dark patterns.
Do you hand over the code, or do we stay locked in?
Code is 100% yours. GitHub repository transferred free of charge. You can continue with any other US mobile app developer or hire in-house. App Store and Google Play accounts open in your name with your W-9/EIN and ACH payout details — 100% ownership yours. Vendor lock-in is not our business model.
Are payments, push, analytics included? What about Apple Pay and Google Pay?
Part of the standard package: Stripe (cards + ACH) with Apple Pay and Google Pay one-tap checkout, PayPal, OneSignal/Firebase push, Twilio SMS with TCPA consent capture, Firebase Analytics + Mixpanel (CCPA/CPRA-safe configuration), Sentry crash reporting, biometric login (Face ID/Touch ID/Android Biometric). Additional integrations (Plaid, Zendesk, Intercom, Branch.io deep linking, MapKit/Google Maps, ARKit/ARCore) become part of scope — no extra charge.
I have a website — how does the mobile app integrate?
Three options: (1) Shared backend — web + mobile fed from a single API; a cart built on web shows up on mobile. The most common approach. (2) Hybrid with web views — on tight budgets some screens render web pages (Apple discourages this; it must be done carefully). (3) Brand-new mobile — mobile-native UX, syncs with web via API. We recommend based on your scenario in discovery.
What about accessibility — is ADA a real risk for apps?
Yes. US courts have treated apps of businesses as places of public accommodation, and ADA demand letters over inaccessible apps are common — retail and food-service brands get hit most. Every build ships with WCAG 2.2 AA alignment: VoiceOver/TalkBack labeling, dynamic type, contrast-safe theming, focus order, captions for media. It's not an add-on — it's in the definition of done, and it also widens your market.