Skip to content

Building your first version

Should my first app be a web app or a mobile app?

Lumos · Updated

For a first version people can use through a link, start by checking whether a web app can do the main task. Choose a mobile app when the task depends on phone capabilities, distribution, or an experience that your web version can't provide reliably.

A web app can work in a phone's browser as well as on a computer. That makes it worth considering for forms, shared information, and tasks people move between devices to complete. You'll still need to design and test the small-screen experience.

Check the requirements that could decide it

Write down where the person will use the app and what the device needs to do. If the task needs background activity, offline access, notifications, or particular hardware, test that capability on the actual devices and browsers you intend to support.

Some web apps can be installed on a device and support offline or background behaviour. MDN's progressive web app guide explains these capabilities. They require implementation, and support varies with the platform and feature. An ordinary website doesn't gain them just by being called an app.

For the handbook's hypothetical feedback tool, a client opening a draft link and sending a response is a reasonable web task to try first. A product that relies on a phone feature throughout its main task needs a separate assessment.

You can revisit the choice after observing real use. Avoid building two interfaces before you've checked whether one completes the task.

In the Builders Handbook

Choose the main task helps you describe what the person needs to do before choosing screens. Build the first working flow includes phone and keyboard checks.