Insights
Planning a web or mobile app: questions to answer first
Before you brief a developer: the questions that shape cost, timeline and success for a new website, web app or mobile app.
A clear brief saves more time and money than any technology choice. Before you talk to a developer, work through these questions. You don’t need perfect answers, but having a view on each makes every conversation faster and every quote more accurate.
Who is it for, and what do they need to get done?
Describe your main users and the two or three jobs they come to do. “Customers book and pay for a service” is more useful than a list of screens. Everything else follows from these jobs.
Website, web app or mobile app?
- A website explains who you are and helps people get in touch or buy.
- A web app lets people log in and do work: manage bookings, see their account, run a process.
- A mobile app makes sense when people use it often, on the go, or need the phone’s features such as notifications, the camera or location.
Many businesses start with a web app that works well on phones, and add a native app later if usage justifies it.
What does it connect to?
List the systems it must talk to: payments, accounting, your CRM, email or an existing database. Integrations are often where the real effort sits, so naming them early avoids surprises.
What is the smallest useful version?
Separate “must have at launch” from “nice to have later”. A smaller first release gets into users’ hands sooner, and their feedback tells you which of the later ideas matter.
Who looks after it after launch?
Apps need updates, security patches, hosting and the odd fix. Decide early who owns that work, and budget for it as an ongoing cost, not an afterthought.
How will you know it’s working?
Pick a few signs of success you can observe: fewer phone bookings, faster quotes, fewer manual steps. Agree on them before you build so you can judge the result fairly.
Accessibility and speed are not extras
A good app works for everyone, including people using screen readers or keyboards, and loads quickly on an ordinary phone connection. Building these in from the start is far cheaper than fixing them later.
Where we can help
Our web and mobile app team can turn your answers into a scoped first release, with design, build and support handled by one team.