Web & Mobile · 04 Nov 2026
A request for “an app” often starts with a business problem: customers cannot find information, staff repeat the same capture work, or orders disappear between teams. Choosing a platform before understanding that problem can turn a simple improvement into a costly product to maintain.
Separate discovery from transactions
A public website is a useful starting point when people need to discover your business, compare services and make contact. A web application becomes relevant when they need to sign in, submit information, track progress or complete repeatable tasks. A mobile application deserves consideration when the task relies on device capabilities, offline work or frequent use that justifies installation.
These are starting questions, not hard boundaries. Browsers also offer device features, and a well-built responsive website can support sophisticated workflows. Validate the specific features on the devices your customers actually use before committing.
Test one complete journey
For an illustrative service-booking journey, sketch how someone finds a service, understands the price or quotation process, submits a request and receives confirmation. Include the staff member who must respond. A polished booking screen is not enough if the request lands in an unattended inbox.
- What does the customer need to achieve in a single visit?
- Which steps require an account, and why?
- What happens on a slow connection or after a failed submission?
- Who owns enquiries, updates and ongoing support?
Make accessibility part of the brief
The W3C’s Web Content Accessibility Guidelines apply across web content, including mobile experiences. Turn accessibility into concrete review tasks: readable contrast, labelled inputs, keyboard navigation, meaningful error messages and layouts that work when text is enlarged. A phone-width screenshot alone does not demonstrate that a service is usable.
Agree what success looks like
Before development, choose a small number of outcomes you can observe: completed enquiries, successful bookings or reduced duplicate capture. Establish the current position so improvements have something to be compared against. Include maintenance, hosting, content ownership and testing in the budget.
A useful first step: write the most important user task in one sentence, then prototype its full journey before choosing the platform. Imaginative Tech’s web and mobile development work can begin with that conversation.
Topics: Digital strategy, User experience
Sign in to comment or rate this insight.
Back to insights