How to prepare for a mobile app project
A clear brief is the cheapest part of an app project to get right. This guide covers what to decide before you order: who the app is for, what it does, which phones it runs on and what you must set up yourself.
5 min readUpdated
In short
- Write down who will use the app, the one problem it solves and the screens it needs. Start small and add features later.
- Choose iPhone, Android or both, and open your own developer accounts, because the store listing should be in your name.
- No seller can promise that an app store will approve the app. Ask what is handed over, what testing is done and who maintains the app afterward.
Start with the problem, not the features
Finish this sentence: this app helps a specific person do a specific thing faster or more easily. If you cannot, the project is not ready to be priced.
Name the main users and what they do on their first visit. Then list the features in two groups: what the first version must have, and what can wait. Every extra feature adds design, building and testing, and the package price is set for a stated scope.
Sketch the screens
Packages are often described by the number of screens, so a rough list is the most useful thing you can bring. A pencil drawing is enough.
- Sign-in and sign-up, if people need an account.
- The main screen a person lands on.
- The two or three screens for the main task.
- Settings and profile.
- Anything that needs payment, notifications or a link to another service.
If you do not have a design yet, UI and UX design is a separate service that can come first. Seeing clickable screens before building starts is a cheap way to find what is missing.
iPhone, Android or both
There are three routes, and each has a trade-off.
One platform first
Choose the phone your customers use most. Building for one is the smallest job, and you can add the other later.
Two native apps
Separate apps for iPhone and Android give each its own look and feel, at the cost of more work.
One app for both
A cross-platform app shares most of its code between the two. It is often the practical choice for a first version.
Accounts and costs that are yours
The store listing should belong to you. Apple and Google each ask developers to open an account, and the accounts and their fees are paid by you, in your own name. The seller can guide you through it, and you can invite them to your account with a limited role.
Other services an app uses, such as a database host, a push notification service or a payment provider, often have their own plans. Ask the seller to list them and say who pays. The platforms review every app before it is published, and no seller can promise approval or a date.
Typical gigs here price a basic package of a basic cross-platform app at $999, with a delivery time of 35 days. Each gig shows its own prices and delivery times, and those are the ones you pay and plan around.
What to ask a seller
Put these questions to each seller in the chat before you order.
- What exactly is included: screens, a backend, a database, an admin area?
- What do I receive at the end: the source code, the design files, documentation?
- How will the app be tested, and on which phones?
- How many rounds of changes are included?
- What happens if I want a feature added after the order starts?
- Who fixes bugs after delivery, and for how long?
Extra features and changes of mind after work begins are normally priced on top of the package, so agree the scope in writing in the chat.
Testing and approving
Delivery time counts from when work starts, and work starts once your payment is confirmed and the gig's questions are answered. Install each test version on a real phone and walk through every screen as a new user would. Try it with a poor connection, and try to break it.
Write down problems with a screen name, what you did and what happened. Once the order is completed and paid in full, our Terms say the finished work is yours to use for any purpose. Music, stock clips and fonts inside it stay under their own licenses. A delivery you do not answer is accepted automatically after 3 days, so set time aside to review it when it arrives.
Before you order
- I wrote one sentence on who the app is for and what it does for them.
- I split my features into must-have now and later.
- I sketched the main screens.
- I chose iPhone, Android or both.
- I know the store and service accounts will be in my name.
- I know what I receive at the end and who fixes bugs afterward.
Questions people ask
How much does it cost to build a mobile app?
It depends on the number of screens, the features, the platforms and the backend. Open the category page, compare the packages and read what each includes. Extra features after the order starts are priced on top.
Will my app definitely be approved by the app stores?
No one can promise that. The stores review each app against their own rules and decide for themselves. A seller can build to the published guidelines and help you prepare the submission.
Do I need a developer account before I order?
Not always before, but you will need one to publish. The accounts are opened in your own name and paid by you. Ask the seller when they need it so it does not hold up the project.
Can I get the source code?
Ask the seller to confirm in the chat before you order what is handed over. Our Terms say the finished work is yours once the order is completed and paid in full, and packages list what is delivered.
How paying works on SkillSellUp
You pay SkillSellUp, never the seller. Your payment is held until you approve the delivery, or until it is accepted automatically after 3 days if you do not respond.
Every seller is approved by an administrator before their gigs go live. SkillSellUp adds no service fee at checkout.
Refunds are guaranteed under the written Refund Policy and paid by SkillSellUp, not left for the seller to agree to.
Find a seller for this
Compare packages, read reviews and ask a question before you order.