The timelines of our packages
These are the delivery times shown on the package pages, counted from the moment you have handed over what is needed to start. For the iOS app:
- Base (showcase app, up to 5 screens): 3-4 weeks.
- Plus (user accounts, push notifications, cloud backend, offline mode): 6-8 weeks.
- Pro (payments, back-office integrations, admin panel): 10-14 weeks.
- For the Android app the times are 3-4 weeks, 6-8 weeks and 10-14 weeks.
The phases of a project
- Analysis and decisions: which screens, which features, which content. This phase shrinks the most if you arrive prepared.
- Design: how the app looks and works, screen by screen, to be approved before any code is written.
- Development: the longest part, and the one that grows with features. A login or a payment is worth many more hours than a photo gallery.
- Testing and fixes: trials on real devices and review rounds with you (2 in Base, 3 in Plus, unlimited during development in Pro).
- Publishing: store listing, screenshots, privacy policy, submission to Apple and Google review.
- After launch: fixing the first issues and shipping the first updates, which are best planned from the start.
An example calendar (illustrative)
For a Plus-level app, delivered in 6-8 weeks, a typical calendar looks like this. It is an example to get the proportions right, not a promise: every project is different.
- Week 1: analysis, list of screens and gathering of materials.
- Weeks 2-3: design and approval.
- Weeks 3-6: feature development, with first test builds on your phone.
- Weeks 6-7: testing, fixes and review rounds.
- Weeks 7-8: store preparation and submission for review.
The part that does not depend on the developer: store review
Every app goes through a review before it is published, and the timing is decided by Apple and Google.
Apple states that on average 90% of submissions are reviewed in less than 24 hours. In practice times vary and in busy periods it can take several days: leave a margin, especially for the first release. If the app is rejected, you fix it and resubmit, and the review starts again.
Google Play has an extra step for personal accounts created after 13 November 2023: before you can ask to publish, you must run a closed test with at least 12 opted-in testers for 14 consecutive days, as Google Play's official guidance explains. That is at least two weeks to plan for, even if the app is ready.
For the costs and documents of the accounts read how much it costs to publish an app on the App Store and Google Play.
What stretches the schedule
- Late content: copy, logo, photos, price list. It is the most frequent cause of delays.
- Decisions that change along the way: adding a feature halfway costs more than the feature itself; design and tests already done are affected too.
- Fragmented feedback: when several people give different directions, review rounds multiply. One point of contact is better.
- Store accounts not ready: identity or company verification takes time and should start in parallel with development, not at the end.
- Integrations with third-party systems: back-office systems and CRMs have their own rules and sometimes incomplete documentation.
How to shorten the timeline without cutting quality
- Prepare the materials before you start: the quote calculator helps you clarify what you really need.
- Decide what version 1 must do and postpone the rest: a small published app teaches more than a big one still in progress.
- Open both store accounts right away, in your own name.
- Name one person who approves and answers quickly.
- Plan the «nice to have» features as a later update.