Mobile
From an idea to an icon on a phone: the app, the server behind it, in-app purchases, and getting through store review.
Mobile
The app itself is roughly half the work. The other half: the server, authentication, sync, push notifications, purchases and subscriptions, analytics — and then App Store and Google Play review, where a rejection on a formality can cost a week.
I do both halves. That saves real time: no negotiating the API contract between two vendors, and no argument about whose side is at fault when something doesn’t line up.
Nine iOS and Android apps shipped — Cam&Cam, Findee, ScanFood, ScanMe and others, taken to the stores and to real users.
The app on both platforms: interface, offline behaviour, correct handling of poor connectivity and low-end devices.
The server behind the app: authentication, cross-device sync, push notifications, user data storage.
In-app purchases on the App Store and Google Play: one-off purchases, subscriptions, credit models, server-side receipt validation so purchases can’t be forged.
Accounts, builds, listings and screenshots, and getting through review — including untangling rejections that arrive as a single line of text.
Counters, crash reporting, staged rollouts. You can see where users drop off and what breaks on which devices.
Updates for new iOS and Android versions, fixes, further features. An unsupported app stops working within a year or two.
What ships in the release and what waits. An overloaded first release is the most common reason an app never reaches the store at all.
Data model, API and sync scenarios. Mistakes at this level cost the most later — you can’t fix them with an interface update.
Builds go out for testing as they’re ready — TestFlight and Google Play internal tracks, rather than one big handover at the end.
Review, launch, then watching crash reports and reviews. Updates follow as fixes accumulate.
It depends on the number of screens, whether there’s a backend, and whether there are in-app purchases. Billing is hourly, for actual working hours. Describe the job and I’ll give an orientation broken down by stage.
A simple app with a backend: from about six to eight weeks. Plus review — App Store review takes anywhere from a day to a week, and a rejection restarts the cycle.
Yes — Apple Developer and Google Play accounts are best registered to you, so the app and its purchases stay yours. I’ll help set them up.
No — review makes that call and its rules change. What I do is meet the requirements during development and work through rejections when they arrive. It usually resolves in one or two iterations.
Yes. It starts with an audit of the code and the build, then an honest call on extending versus rewriting. The estimate comes before any work.
Yes, if that’s the cheaper way to test the idea. Shipping one platform first, gathering feedback, then doing the second is often the sensible order.
This site uses cookies and Yandex Metrica to understand traffic. By continuing to use the site you agree to this. Learn more