1. The one-line summary
In a single sentence, what does the app let someone do that their phone browser can't already do well? If you can't write that sentence, the app might not be the right tool yet.
2. Who it is for
Name the main user: a regular customer, a member, a driver, a class attendee. Describe when they would open the app. "On the way home from work" tells us more than "anyone".
3. The must-do actions
List the three to five things a user must be able to do. Order them. The first one should be obvious within ten seconds of opening the app.
4. What it connects to
- Your website or web application
- Booking, ordering, or payment systems you already use
- Any customer database or loyalty records
- Notifications: what would you send, and how often?
5. Platforms and launch
Decide whether you need iPhone, Android, or both at launch. Cross-platform is usually the right call for a first release. Mention any App Store or Play Store accounts you already have.
6. Native build or Progressive Web App?
A Progressive Web App (PWA) installs from a normal web link, runs full-screen without a browser bar, works offline and can send push notifications — without ever touching the Play Store or App Store. For loyalty cards, ordering, member portals and internal tools it is often the faster, cheaper route, with updates that go live the moment we deploy.
- Choose a native build if you need a Play Store or App Store listing for credibility, want deep hardware features (Bluetooth peripherals, advanced camera, background location), or rely on in-app payments through Apple or Google
- Choose a PWA if you want a polished home-screen app, push notifications and offline support, but would rather skip store reviews, fees and version-stuck users
- Tell us which feels closer to your business and we will sanity-check it in the first call
7. Budget and timing
A rough budget range helps a developer scope the right first version, rather than overpromising. A soft target launch date is enough. Exact dates come later.
8. What success looks like
Pick one signal: downloads in the first month, repeat opens per user, bookings taken through the app. This keeps the build focused.