Frequently asked questions
Questions before building an app.
How much does app development cost, and how long does it take?
Cost and timing depend on the workflow, screens, backend and integrations. A focused React Native release may take 6-10 weeks to develop; a complex native app may take 3-6 months, subject to scope and dependencies. These are development estimates. Account verification, testing and store review separately affect publication. Defining the first release lets us estimate your project.
How do you choose between native, React Native and PWA?
Consider user experience, device capabilities, required performance and the team maintaining the code. Shared code can reduce duplicated work, but may still need platform-specific code and real-device testing on both platforms. A PWA can suit some workflows, but camera, push, offline and hardware support must be verified on the relevant browsers and operating systems. No approach is always cheaper or faster.
Should we build for iPhone or Android first?
Start with your audience's devices and the workflow you need to test. You can launch on one platform first or develop for both. Distribution, device capabilities and testing scope help determine whether a shared-code approach fits.
Who owns the source code, store accounts and hosting?
Define source rights, repository access, third-party licences and documentation handover in the agreement. Also agree who holds the Apple, Google and hosting accounts, who can publish and how access is handed over. Set this out before development so ongoing operations have clear ownership.
Do you help with App Store and Google Play submission?
Yes. Agree who prepares developer accounts, store materials, privacy declarations and submission, and what review corrections include. Apple and Google decide whether to approve an app and may require verification, testing or further changes. The approval date cannot be promised in advance.
How do you handle data and privacy?
Map what is collected, what stays on the device or backend, who can access it and what goes to external services. Define permissions, retention and deletion around the product, and prepare declarations that match the app's behaviour. If AI is included, assess its data flow separately. On-device processing alone does not establish privacy or performance.
Can the app work without an internet connection?
Some actions can be designed for offline use. Define what is available locally, which actions wait for connectivity and how conflicting changes are resolved during sync. Authentication, external services and platform support affect what is possible. Test against the network conditions users will encounter.
What happens after launch?
Agree responsibility for support, issue monitoring, operating-system and library updates, and new store submissions separately. Workflow changes and new features get their own scope. Handover should identify who handles each component and which access and documentation they need.