# Mobile App Order Checklist: 10 Questions to Answer First

**Most app-project disputes start on day one, not in the code. Have you answered these ten questions before ordering?**

> Before commissioning a mobile app, ten things must be clear: goal and user, platform, first-version features, data source and admin panel, login and payment, design, code and publishing-account ownership, distribution in Iran, schedule and maintenance. With these, cost and time estimates become far more accurate.

Author: Saman Ghahreman · Published: 2026-10-08 · Updated: 2026-10-08 · Canonical page: https://solocodelab.com/en/blog/mobile-app-order-checklist/

Most disputes in app projects come from ambiguity at the start, not from coding. If you answer the ten questions below, [the cost and timeline of your app](https://solocodelab.com/en/blog/mobile-app-cost-guide/) can be estimated much more accurately and you avoid surprises.

## Ten questions to answer before you order

1. What problem does the app solve, and for whom? (one sentence)
2. Android, iPhone or both? To decide, compare [Flutter and native development](https://solocodelab.com/en/blog/flutter-vs-native-app/).
3. What is the minimum feature set the first version must have? (Leave the rest for version two.)
4. Where does the data come from and who manages it? Do you need an admin panel?
5. How do users sign in (mobile number with SMS, email) and do you need in-app payment?
6. Who provides the design? Send your logo, colours and examples of apps you like.
7. Who owns the source code and the publishing accounts (Google Play, Apple, Bazaar)? It should be you.
8. How will the app be distributed in Iran? [Options for iPhone in Iran](https://solocodelab.com/en/blog/iphone-app-for-iran/) are different.
9. When do you need it, and can delivery happen in a few visible milestones?
10. Who fixes bugs and updates the app after launch, and on what terms?

### Ten questions in four groups
1. **Goal**: Who is the app for and what problem does it solve? Android or iPhone? What must version one include? (questions 1–3)
2. **Data and sign-in**: Where does the information come from? How do users sign in and do you take payments? (questions 4–5)
3. **Look and ownership**: Who provides the design? Whose name are the code and publishing accounts in? (questions 6–7)
4. **Launch and after**: Where will people install it? When do you need it? Who looks after it after launch? (questions 8–10)
_Answer these four groups and the price and timeline estimate becomes much more accurate._

## Why do publishing accounts and code ownership matter so much?

Publishing on the App Store requires membership in the Apple Developer Program, and publishing on Google Play requires a Play Console account. If those accounts aren’t in your name, the app and its users depend on someone else, so open them in your own name from the start.

## What should you send for an accurate estimate?

- A one-paragraph description of the idea and users
- A list of must-have and nice-to-have features
- Similar apps you like
- Approximate timeline and budget

For a simple example with no server, look at [Chekyar](https://solocodelab.com/en/products/chekyar/), which works entirely offline on the phone; and to see how we work, read [the case study of our offline Persian apps](https://solocodelab.com/en/blog/solo-built-persian-apps-case-study/).

To see what testing on a real phone actually catches, read [the story of building the Koja Barim travel app](https://solocodelab.com/en/blog/kojabarim-offline-iran-travel-safety-app/).

See a real example of a simple offline app for managing cheques in [managing received and issued cheques with Chekyar](https://solocodelab.com/en/blog/cheque-management-app-offline-chekyar/).

> If your answers are ready, [send the project brief](https://solocodelab.com/en/contact/?service=android-app-development) to get a written proposal for [an Android app](https://solocodelab.com/en/services/android-app-development/) or an iPhone app.

## Frequently asked questions

### What should I prepare before ordering an app?

Goal and user, platform, first-version features, data source, examples of similar apps, and an approximate timeline and budget. We clarify the rest in the first call.

### Whose name should the Google Play or Apple account be in?

Yours or your business’s, so you keep ownership of the app and its users.

### Will I receive the source code?

It must be clear in the contract; our recommendation is that you own the source code and the publishing accounts.

### What if I don’t know every feature yet?

Start with the smallest useful set and add features after you see how users behave; a small, complete first version beats a large, unfinished one.

## Sources

- [Apple Developer Program](https://developer.apple.com/programs/) — Apple
- [Play Console help](https://support.google.com/googleplay/android-developer/) — Google
