App Development
Android applications built, shipped and maintained, including the store compliance work that sinks most first attempts.
The problem
Building an app is the part people plan for. Store review, data safety declarations, account deletion, content moderation and release management are the parts that stall launches for months.
- The build is finished and the store has rejected it twice over data safety.
- The store now requires in-app account deletion and yours does not have it.
- Every release goes out by hand, from one person, on one laptop.
- You have an idea that needs a phone, not another website.
What you get
- ✓React Native and Expo builds on a managed backend
- ✓Play Store compliance: data safety, account deletion, permissions, target API
- ✓Billing and in-app purchases where the model needs them
- ✓Release management and post-launch maintenance
We have five applications live on Google Play and have been through store review on each of them. The builds are React Native and Expo on a managed backend, with billing where the model needs it.
Release management continues after launch, because a shipped app is a maintenance commitment rather than a finished project. Platform requirements change on Google’s schedule, not yours.
What it costs
Scoped per project. A first release is rarely under 150 hours at $160 per hour once store compliance is included.
Frequently asked questions
Do you build for iOS as well?
Our shipped work is Android. The stack is cross-platform, so iOS is possible, but we would be honest that our store-review experience is on Google Play.
Why does compliance take so long?
Data safety declarations, account deletion flows and content moderation on user generated text are all required before review will pass. They are not optional and they are not quick, which is why first-time launches slip.
What happens after it is live?
Platform requirements change and an unmaintained app eventually stops being distributable. Ongoing releases can go on a care plan.