Mobile App Development

It depends on four things: how many screens, how much of the design is custom, which integrations you need, and whether you want one platform or both. We scope before quoting — after a discovery call you get a written estimate tied to a specific scope, usually within 48 hours, rather than a range that moves later.

Our 90-day track takes a defined scope from kickoff to a first release. Wider scope, heavy integrations or compliance requirements extend that. You get the timeline together with the estimate, before development starts.

If you're building cross-platform, you don't have to choose: both ship together. If budget forces one, pick by audience — iOS users spend more on in-app purchases, Android has wider reach outside North America. We'll tell you which way your market points before you commit.

Cross-platform covers most products: if the app is screens, data, forms and standard device features, one codebase is faster to build and cheaper to maintain. Native makes sense when the app leans on hardware — heavy camera work, background processing, complex Bluetooth. Often we mix the two.

Both are solid. We work in React Native because it shares a language and ecosystem with the web side of most products, which matters when one team maintains both. Flutter is a reasonable choice too — if you already have Flutter engineers, that's usually the stronger argument.

You do, both. The code sits in your repositories from the first commit, and the App Store Connect and Google Play Console accounts are registered in your company's name, not ours. If the engagement ends, nothing has to be transferred — the app, the listings and the reviews are already yours.

Yes — the store listing, screenshots, privacy declarations, age ratings and the review itself. Apple's review usually takes one to three days, Google's is normally faster. We submit from your account, so the app publishes under your name.

It happens to almost every app at least once, and it's rarely serious. Most rejections come from missing privacy disclosures, unclear demo credentials, or a guideline the app brushes against. We fix and resubmit, usually within a day or two. It's part of the release, not an extra.

Yes. We start with a short audit — the code, the build pipeline, the store accounts and what's actually deployed — then give you a written picture of the state and what it costs to move forward. Sometimes the answer is to continue, sometimes to rebuild one layer. You see that assessment before committing to either.

It depends on the domain. In healthcare that means HIPAA and GDPR in how data is stored and transmitted, not just a policy page. Across all apps: no secrets in the app bundle, encrypted local storage, token-based auth, and the privacy declarations both stores now require.

That's your call. iOS and Android ship a major version every year, and apps that aren't maintained quietly break — so most products need some ongoing work. We can keep building, cover maintenance only, or hand over to your team with the accounts and documentation.