When a business needs a mobile app

Start with where and how often it is used

A customer checking an order once a month and a worker scanning products all day have different needs. Describe where people use the product, how often they return and what they must accomplish in one session. Installing an app should offer a practical benefit rather than merely another icon on a phone.

Test the mobile web journey first

A catalogue, inquiry form, booking flow or customer account can work well in a browser. Test on real devices: controls, data entry, file uploads and returning to an unfinished action. If the underlying process is confusing, moving the same screens into an app will preserve that confusion. Fix the journey first.

Describe device features precisely

Camera use, location, notifications and offline work each need their own scenarios and target-device checks. Avoid grouping them under a vague mobile capabilities requirement. Define what happens when permission is denied, connectivity disappears or the app returns from the background. Validate the chosen format’s capabilities and limitations in a prototype before full development.

Keep the product’s data consistent

The website and app need a shared understanding of users, orders, bookings and payment status. Design the backend and access rules early. Our experience includes iOS and Android clients for Set-Ka and an iOS client for Pitomesto. Their value comes from making the product’s actual workflows accessible on a phone.

Plan beyond the first version

A mobile product needs testing on selected operating-system versions and devices, followed by updates and support. Agree who prepares publication materials, handles feedback and checks new builds. Plan for older app versions to remain in use. Customers do not all install an update as soon as it is released.

How to prepare the decision

List the main actions, target devices and connectivity conditions. Mark which workflows already work well in a browser and which require investigation. Use that information to compare a mobile website, an enhanced web client and a native app by implementation scope. Base the choice on demonstrated constraints and practical user value.