Hakimi Sa’ari’s BlogDoes your business need a mobile app, or is a mobile-friendly website enough?
A mobile-friendly website is often enough for occasional tasks such as reading services or submitting an enquiry. Assess a PWA or a dedicated app when frequent use, offline work or particular device features make a difference.
Baca artikel ini dalam Bahasa MelayuText size
Start with what customers need to do
Most of your customers use a phone, so your business needs an app too? Not necessarily. A website that works well on a phone can already handle plenty of everyday tasks.
If customers only need to browse services, fill in a form or send an enquiry, first check whether a regular website is enough. They can open a link without installing anything.
Take a car wash. A customer chooses a package, fills in their details and sends a booking request. If they only use the service occasionally, asking them to install an app may add a step they do not need.
Staff may have different needs
Staff may have different needs. Suppose they record visits every day, take photos on location and update tasks. For work they repeat frequently, an application that is easy to reopen could be useful. But the technology still depends on the actual features required.
Where a PWA fits
Besides a regular website and an Android or iOS app, there is the PWA option: a Progressive Web App. It uses web technology and can support installation on compatible devices. The installation process and available features vary by browser and operating system.
One of my personal projects, Expense Tracker, uses the PWA approach. It has transaction records, receipt uploads and an expense dashboard in an interface designed for phones. It is a web application, not a native app-store release.
Check offline work and device features
A PWA does not automatically make every feature work offline. Offline data and workflows have to be built for that purpose. A feature that depends on an online API still needs a connection.
The same applies to cameras, notifications and background tasks. List the requirements first, then check support on the devices people will use. If particular hardware features or integrations are essential, a native or cross-platform app may be more appropriate to assess.
Allow for work after launch
Think about the work after launch too. Android and iOS support, device testing, distribution and updates are all part of the job. If you use app stores, their accounts and review processes need to be managed. With the web, hosting and browser support still need attention.
Write down one complete task before choosing
Before choosing an approach, write down one complete task a user needs to do on a phone. For example: open a job list, choose a customer, take a photo and submit a report. Then decide whether the task must work offline or needs a particular device feature.
That is more useful than starting with a requirement for both Android and iOS apps. A responsive website may be enough for a first version. A PWA may be worth trying first. Some projects do need a dedicated app from the beginning.
When asking for a quotation, specify the target devices and the most important features. Ask how people will access the app, how updates will be delivered and what needs looking after once it is live.
I'm Hakimi Sa’ari, a freelance developer from Selangor, Malaysia. If you are planning a website or app for your business, you can see my work at hakimisaari.site.