Describe one complete journey
Imagine a first-time visitor who has a specific reason to arrive. What must they learn, enter, decide and receive? A booking journey may need availability, a short form and a confirmation. It does not automatically need a social feed or an account dashboard.
Write the beginning and the finish before listing screens. Include the moment when something goes wrong: an unavailable date, an interrupted connection or an unclear next step.
Compare access with repeat use
A website can make a task easy to reach through a shared link. A mobile app may be worth exploring when a recurring activity and device capabilities are central to the experience. Neither choice guarantees adoption.
Ask how people will discover the service, how often they expect to return and what they need on the device they already use. Test these assumptions with potential users instead of treating them as requirements.
Prototype the decision
Sketch the journey on a few pages and ask someone to talk through it. Notice where they hesitate. A clearer sequence may matter more than adding another feature.
Record what the prototype teaches you, including questions it cannot answer yet. A short discovery exercise creates a better development brief than a confident platform decision with no user evidence.
Your small, useful checklist
A good platform decision follows the task. Start with the route people need, then choose the technology that supports it. Explore Seventh’s app portfolio for product context. For further reading, consult W3C’s introduction to web accessibility.