An app icon on a phone is easy to picture. The harder question is what customers or staff will do after they tap it, and whether a phone app makes that task easier.
A native mobile app is built for a particular phone platform, such as iPhone or Android. It can be a good choice for a service people return to regularly or a job that depends on the phone. It is worth understanding the alternatives before committing to a build.
What does “native app” mean?
A native app is built specifically for a platform. An iPhone app is built for Apple’s phone system, while an Android app is built for Android phones. It is installed on the device and designed around the way that platform works.
You may also hear about cross-platform apps. These are installed phone apps too, but they share some of their underlying code between platforms. Your developer should explain which approach they recommend and what that means for the work, the budget and future changes.
A web app is different: people use it through a browser link. Some web apps can be added to a home screen, but they still use web technology. If you are comparing all three options, start with our guide to web apps and native phone apps.
When a phone app earns its place
An installed app needs a reason for people to keep it. That reason is usually a useful task they repeat, rather than information they could find on your website.
A customer might regularly manage bookings or use a membership service. A member of staff might record work throughout the day. A product might be designed around taking photographs, finding information while travelling or receiving timely updates.
These uses can justify looking at a phone app. They do not establish the best build approach on their own. Write down the exact task so the developer can show how it will work.
Look at what the phone needs to do
“We need access to the camera” is only the beginning of a requirement. Does someone need to take one photograph, collect several pictures of a job, or scan a code? What should happen to that information afterwards?
The same applies to location and notifications. Explain when the feature is useful and what the person should do next. A reminder that helps someone act is more valuable than a stream of updates they learn to ignore.
Phone browsers can handle many useful tasks too. Ask the developer to show why a particular feature needs an installed app, and try the important journey on the phones your customers or team will use.
Plan for poor internet connections
If people will use the app on site, while travelling or in areas with poor reception, decide what must still work without a connection.
They may need to read information saved earlier, add notes or record photographs to send later. Plan what they see while waiting, how they know their work is saved and what happens if two people change the same record.
Installing an app does not automatically make every function work offline. The useful question is whether your team can complete the agreed job and get their work back to the right place.
Will a web app do the job more simply?
If customers only need occasional access, asking them to install something can be an extra hurdle. A browser link may be more convenient for checking an order, updating details or sending a request.
A business web app can also suit staff who spend much of their day at a computer. You may need both: an installed app for work on a phone and a browser-based screen for the office team.
The choice should follow the job and the people doing it. A more expensive or more complicated build is not automatically the better service.
Budget for the work after the first build
Agree which phones and versions you will support, who handles app distribution and who maintains the service behind it. Ask what happens when phone software changes or users report a problem.
For iPhone and Android, include testing on both in the proposal. If the team shares some code between the two, there is still work to check that the app behaves properly on each.
Make account ownership, access to the source files, running costs and ongoing support clear before launch. These are ordinary business questions, and a proposal should answer them clearly.
Our guide to business phone app costs takes a closer look at how the first release, offline work and ongoing support affect the work involved.
Start with the smallest useful release
Choose a complete journey you can put in front of real users. If the app handles service requests, the customer needs to send one, the team needs to receive it and the customer needs to see what happened.
Leave room to learn before adding every idea. Our guides to choosing first-release features and briefing an app developer can help you prepare.
smitsocial.media develops web and mobile apps for businesses in Kent. You can see our own products, Reveli, Pistio and Squario, or tell us about your idea. We are based in Maidstone and work with businesses across the county, including small teams planning their first app.


