"We need an app" can mean very different things. Sometimes it means a mobile app in the App Store. Often it means a web app that works on phones. Sometimes it means both, talking to the same back office.

The choice changes the cost, the timeline and how you update it later. So I ask a few questions before anyone draws a screen.

Start from who uses it, where they are, and what they hold in their hands.

Who uses it, and where

Office staff and managers, at a desk most of the day, need a web app. Big screens, tables, reports, exports. A store app adds nothing for them.

Customers who visit once or now and then usually need a website or web app too. Most people will not install an app to book one appointment.

Field staff, drivers, warehouse teams and technicians are where a mobile app earns its place. They work standing up, with one hand, often without signal.

When a web app is enough

  • People use it at a desk, or occasionally on a phone browser.
  • The work is mostly forms, tables, approvals and reports.
  • You want to update it any time without waiting for app store review.
  • Users are outside your company and won't install anything.

A well-built web app works on phones too. For many businesses, that is the whole answer.

When a mobile app is worth it

  • People scan barcodes or take photos many times a day.
  • It has to work without signal, then sync later. I wrote about that in a field app that keeps working without signal.
  • It needs the phone's camera, GPS or notifications in a reliable way.
  • The same people open it all day, every day.

When it is both

The most common setup I build is both: a mobile app for the people doing the work, and a web back office for the people managing it. Both read and write the same data.

The field records the stock count; the office sees it live and exports the report. Neither side has to type anything twice.

If that is your shape, plan the back office and the data first. The mobile app is the easier half once the data is right.

A note on "one app for everything"

It is tempting to build one app that does it all, on every device. Usually it ends up awkward everywhere. A phone screen built for a warehouse and a dashboard built for a manager want different things. Sharing the data is good. Sharing every screen rarely is.

# choosing
who are the users, by role ✓
where they are when they use it ✓
do they need the camera, scanner or GPS ✓
does it have to work offline ✓
how often each group opens it ✓
what the office needs to see afterwards ✓

Not sure which one you need

Tell me who uses it and what they do. Describe it on the scope page or get in touch, and I will suggest the smallest setup that does the job. See services for what I build on each side.