Start here.
Choose around the task and the people doing it. Compare opening a link with finding, installing and returning to an app. Check any essential phone features on the devices people use. Ask your supplier to explain the tradeoffs and continuing responsibilities, then try the proposed journey before committing to the full build.
- A service people use on a phone can be delivered through a browser or a downloadable app.
- An occasional customer and a colleague using the service every day may need different ways in.
- Ask for a demonstration of essential features on the intended devices rather than choosing from a list of assumed limitations.
What will someone actually do in it?
Imagine a business giving customers a way to review the details of a proposed job and send back a decision. This is a fictional planning example. A customer receives a message, opens the proposal, checks it and responds.
Describe that complete journey before choosing where to build it. Would the customer start from an email link, a search, a saved bookmark or an icon already on their phone? What would happen if they opened the message on a laptop instead?
A website can provide an interactive service, not just pages about the business. An app is also more than its store listing. Compare how each option would help this person finish the same job, including signing in, correcting a mistake and getting help.
How often would people come back?
For the occasional customer in our example, ask whether downloading something adds enough value to justify the extra steps. Show the proposed journey to someone who might use it. Watch what they do when asked to find the service again, rather than assuming they will remember where it is.
Now consider a colleague checking jobs and adding updates throughout the working day. A convenient place to return to may matter much more to them. Discuss that repeated task separately from the customer’s occasional approval.
Regular use is a reason to investigate a downloadable app, not proof that one is required. Ask what will bring people back, how they will know there is something to do and how the service fits the devices they already use. Do not treat a place in an app store as a plan for finding customers.
Does the job depend on a particular phone capability?
List the capabilities the actual work needs. Someone might need to take a photo, use the service with a poor connection or receive a timely alert. Describe the situation and consequence: “Our colleague needs to record the visit before leaving, even when reception is unreliable.”
Ask your supplier to demonstrate the essential behaviour on the phones and browsers you intend to support. Include what happens when a permission is declined, a connection disappears or the person returns after closing the service.
Avoid choosing from broad claims that websites cannot do something or that a downloadable app will automatically handle it. Device support, the design and the implementation all matter. Agree what must work, what limitations remain and what alternative is available when the preferred route fails.
Could a service opened from a link also have an icon?
Some browser-based services can also be added to a device and opened from an icon. MDN’s installation guidance explains that support and installation steps vary by browser and platform. This is an option to discuss, rather than a promise that every website behaves like every downloaded app.
Ask to see the way in as well as the finished screen. Can the intended person discover how to add it? What happens if they choose not to? Will the ordinary link still let them complete the task?
For our example business, a link for an occasional customer and a convenient return route for staff might meet different needs. Your supplier should explain which parts can be shared and which require additional work. Ask about the behaviour you need rather than paying for a label.
What comes with distributing an app through a store?
Ask who will manage the business’s store account, prepare submissions, respond to review questions and maintain future releases. Include those responsibilities in the project discussion before choosing store distribution.
For Apple’s App Store, the review guidelines call for more than a repackaged website. Putting an existing site inside a downloadable app does not guarantee acceptance. Ask the supplier how the proposed service meets the relevant current requirements and what preparation is included.
Discuss how people will get help with installation, access or an older version. If a launch date matters, ask how review, corrections and distribution fit the plan without treating approval as a date your supplier can guarantee. Requirements for each intended store need their own check.
What should you compare before choosing?
Ask for the realistic options against one agreed task. For each, list the first steps a user takes, essential capabilities, supported devices, remaining compromises and the work your team will keep doing after launch.
Separate what has been demonstrated from what still needs investigation. A short trial of a difficult phone feature may be more useful at this stage than a polished picture of the home screen. Use made-up information and agree a safe test with the supplier.
Choose the approach that fits the work you have evidence for now. Record why you chose it and what would justify reconsidering later, such as a new task or a clearly different pattern of use. That gives the first build a purpose without assuming every possible version belongs in it.
Bring one journey to the decision.
Ask your supplier to compare the realistic options against the same finished job. These notes make that comparison concrete.
- The way in
- How does the person first reach the service, and what do they need to do before starting?
- The reason to return
- How often will they use it, and what will bring them back?
- The essential capability
- What must work on their actual phone, browser or computer?
- The continuing work
- Who maintains each version, handles distribution and helps people who cannot get in?
Planning something with a similar workflow?
Discuss your project with usA couple of common questions.
Is a downloadable app always more expensive than a website?
Do not compare prices from the labels alone. Ask for estimates covering the same task, supported devices, testing, distribution and continuing maintenance. A complex browser-based service and a limited downloadable app can involve very different work; the actual scope needs explaining.
Can we start in a browser and add a downloadable app later?
Discuss that possibility before committing. Ask which work could be reused, which parts would need to be built or tested again, and what limitations the first approach would create. Treat a later version as a future decision with its own estimate, not an automatic upgrade already included.