Mobile app development

React Native, unless there is a specific reason otherwise. It is the right call for apps built from screens, forms, lists and a camera, which covers most business and marketplace apps, and it halves your ongoing maintenance because there is one codebase rather than two. Go native when you need sustained background execution, heavy on-device media processing, deep platform framework integration, or an interface that must feel native down to the scroll physics. We give you this assessment in writing during discovery, before any budget is committed.

A genuine minimum viable product with authentication, a handful of core screens, a backend and both stores handled is usually a three to five month engagement. The wide range you see quoted online is mostly a difference in what is included: many low quotes exclude the backend, the admin panel, store submission, and any offline behaviour — which is to say, they exclude the parts that take the time. We quote after discovery with those line items visible, so you can compare like with like.

Yours, always. You own the Apple Developer and Google Play accounts, the signing keys and the listings. This matters more than it sounds: an app published under an agency account is extremely painful to move later, and it gives the agency a veto over your product. We will help you set the accounts up if you do not have them.

Both platforms ship a major OS release every year, and each one breaks something — a permission model changes, a library goes unmaintained, a store policy tightens. An app with no maintenance budget is a depreciating asset. We usually propose a small monthly retainer that covers OS compatibility, dependency updates, store policy changes and crash triage, separate from any new feature work so the two are not competing for the same money.

Yes. It starts with an assessment: reading the code, checking dependency health and store compliance, and finding out what is load-bearing. Sometimes the answer is that the app is fine and it needs three specific fixes. Sometimes it is that the dependencies are four years unmaintained and the honest recommendation is a rebuild of the shell around the existing business logic. You get that assessment in writing before we propose any work.