From the outside, having a mobile app built looks like a single job: a team writes the app, and one day you see it in the store. In reality, the process is made up of six connected steps, and each step has a decision that you need to make. Knowing the steps from the start shows you where to wait and where to step in. That makes both the timeline and the budget more predictable. Below we explain, in order, what happens at each step and what is expected of you as the business owner.
Idea and scope: who is the app for, and what will it do?
In the first step, you sit down with the software team and clarify what benefit the app will bring and to whom. Will your customers place orders, book appointments, or will your field team enter daily reports? The answer to this question determines the screens, the features and the budget. Simplifying the idea is also part of the work at this stage. Instead of putting every feature you have in mind into the first version, starting with the core features that do the app's main job is usually the best path. How the app will contribute to your business, or how it will bring in revenue, should also be discussed at this stage. By the end of the conversation, you should have a short written document that describes what the app will do, who will use it and which screens the first version will include. This document is the basis for the quote and the timeline; it also prevents later arguments along the lines of “but I wanted this too”. Here is what is expected of you at this step:
- Describe your business and the problem your customer faces in your own words; you don't need to know any technical terms.
- Show apps you like, or apps your competitors use, as examples.
- Split the features into two groups: “must have in the first version” and “can be added later”.
- Name a single person who will make decisions throughout the project. Scattered approvals are one of the things that slow a project down the most.
Screen design: seeing it before any code is written
Once the scope is clear, the app's screens are designed, along with how the user moves from one screen to the next. Most teams first prepare rough sketches, then final screens with colors and fonts. These screens are sometimes turned into a clickable sample (a prototype), so you can try the flow by tapping through it on your phone. Changes at this stage are quick and easy. The same change, if requested after the code is written, can mean days of work. When approving the design, look not only at how it looks but also at how many taps it takes the user to finish their task. For example, an order should be completed in as few steps as possible, from the menu to payment. The app's name and icon should also be settled at this stage, because the store page and your promotional work depend on them. What is expected of you: your logo, brand colors, product images, the texts that will appear in the app, and a clear approval of the design.
Development and testing: trying the working version on your phone
The approved design is turned into code. At this stage, it is not only the app on the phone that gets written; the server side where data is stored and, if needed, an admin panel where you manage the content are also set up. In projects that run well, the team regularly shows working interim versions. Thanks to TestFlight, Apple's test distribution tool, and Google Play's internal testing option, you can install the app on your own phone and use it before it reaches the store. It is natural for new ideas to come up during development. Instead of adding them right away, writing them on a list and reviewing them after the first version protects the timeline. If there is an admin panel, learning how to use it, for you and your team, should also be planned during this period. On launch day, you should be able to manage products, promotions and users yourself. During testing, the app is tried on real phones of different brands and models, on weak internet connections and on older operating system versions. The team looks for technical bugs; your contribution is to try real business scenarios. Place an order from start to finish, cancel it, have your staff use the app. Sending the problems you find with screenshots, in a single list, gets much faster results than scattered messages.
Publishing to the stores and what comes after launch
When the app is ready, it is submitted to the App Store and Google Play. This requires a developer account in both stores. We recommend having the accounts opened in your business's name; that way the app appears in the store under your company's name and ownership stays with you. At this stage, you will be asked for company details, the approvals needed to open the accounts and the contact details that will appear on the store page. A description, screenshots, an icon and a privacy policy are prepared for the store page. Then both stores review the app according to their own rules. If something does not comply with the rules, the app is rejected, fixed and submitted again. After launch, the most valuable information comes from real users. Store reviews, crash reports and usage data show what should be improved in the next version. Because phone operating systems are updated every year, regular maintenance of the app should also be planned from the start.