Where the Phone Beats the Desk
An app is not simply a smaller version of your website. These are the sectors where being in someone’s hand, in a particular place, with a camera and a battery and no guarantee of signal, changes what you can build.
Eight Sectors, Eight Different Sets of Problems
What the App Has to Do, and What Gets in the Way
Each one below covers the same three things: the job, the physical constraint that only appears on a phone, and the integration that comes up every single time.
Retail & Ecommerce
Browsing, search, a saved basket, order history and reorder in two taps. The real prize is not a second storefront — it is loyalty, push notifications you have permission to send, and a card already on file so a repeat purchase takes seconds.
The mobile constraint
Image weight and cold start. A catalogue app that takes four seconds to show the first product on a mid-range phone loses the sale before the page paints. Everything is lazy-loaded, cached and sized for the device, and the last screen a customer saw is restored on reopen.
The integration that always comes up
The commerce platform or ERP that owns stock and pricing. It is rarely built for a phone, so we put a caching layer in front of it rather than letting the app make a dozen calls to render one screen.
Health & Fitness
Logging, plans, progress over time, and reminders that get opened instead of dismissed. Often a companion watch app, because on the wrist is the only place some of this data can realistically be captured.
The mobile constraint
Battery over a full day of sensor use, and permissions that a person has every right to refuse. Health and activity data sits behind explicit consent on both platforms, and the app has to remain useful for someone who says no — which is a design decision, not an error state.
The integration that always comes up
The platform health stores and wearable data sources, plus whatever your practitioners already use for records. Health data also attracts extra scrutiny in store review and stricter rules on what may be collected, so the declarations are drafted in week one rather than the week of submission.
Field Service & Trades
Today’s jobs, the site history, parts used, photos before and after, a signature at the end, and an invoice triggered from the van rather than from a laptop three days later.
The mobile constraint
Offline is the default, not a fallback. Plant rooms, basements and rural roads have no signal, so the job list, the forms and the photos all have to work with the aeroplane symbol showing and sync cleanly when the engineer drives back into coverage. That means a local database, a queue, and a settled answer to what happens when two people edited the same job.
The integration that always comes up
The job management or scheduling system, and behind it the accounting package. Both usually expect a polite web client rather than fifty handsets syncing at 5pm, so the sync design matters more than the screens.
Logistics & Delivery
Route for the day, scan on pickup, scan on drop, proof of delivery with a photo and a signature, and a live position that the customer and the office can both see.
The mobile constraint
Gloves, cold, sunlight and a warehouse handset with a hardware scan trigger. Tap targets have to be large enough for a gloved thumb, contrast high enough to read in direct sun, and the scan flow fast enough that nobody reverts to a clipboard. Background location has to survive the whole shift without flattening the battery or being killed by an aggressive power saver.
The integration that always comes up
The transport management or warehouse system, plus carrier and tracking APIs. Barcode symbologies are never quite what the documentation claims, so we test against real labels from your own operation before writing the parsing.
Hospitality & Food
Menu, order ahead, table or collection, a loyalty balance that is visible without hunting, and offers that land at the hour people are actually deciding where to eat.
The mobile constraint
One-handed use while standing in a queue, often on venue wifi that is barely working. The whole order flow has to be reachable with a thumb on the lower half of the screen, and a dropped connection mid-payment must never leave a customer unsure whether they have been charged.
The integration that always comes up
The till or point-of-sale system, which decides whether an order actually reaches the kitchen. Multi-site businesses then need per-branch menus, opening hours and stock, which is more work than it sounds and is best designed in from the start.
Education & Training
Lessons in short pieces, progress that is visible, assessments, certificates, and a nudge that brings someone back on day three when the enthusiasm has worn off.
The mobile constraint
Learning happens on a commute, so content has to be downloadable and playable with no connection, and progress recorded locally then reconciled later. Video is the other trap: it dominates app size and mobile data, so quality is adapted to the network and downloads are managed rather than left to fill the phone.
The integration that always comes up
The learning management system or course platform that already holds enrolments and results. If courses are sold inside the app, store billing rules apply to that purchase, and the rules differ from selling the same course on your website — a difference worth understanding before pricing anything.
Events & Ticketing
Tickets in the wallet, the schedule, a map of the venue, alerts when something moves, and a scan on the gate that takes well under a second per person.
The mobile constraint
Thousands of phones on the same cell tower at the same moment. Tickets must render from local storage with no network at all, screen brightness has to lift automatically for the scanner, and the door app has to validate offline and reconcile afterwards so the queue never stops moving. Everything spikes into one hour and then goes quiet.
The integration that always comes up
The ticketing platform, plus the phone wallet passes people genuinely prefer to an app login on the night. Getting a pass into the wallet is often more valuable than getting the app opened.
Finance
Balances, transactions, transfers, statements and alerts, with biometric sign-in and a session that ends when it should rather than when the user remembers.
The mobile constraint
Security has to be visible without becoming friction. Face or fingerprint unlock with a sensible fallback, sensitive screens hidden from the app switcher, tokens held in the keychain or keystore rather than anywhere convenient, and screenshots and copy behaviour thought about deliberately. Onboarding with identity checks is where most users drop out, so it is designed and instrumented as carefully as the money screens.
The integration that always comes up
Your core banking or ledger provider and an identity verification service. Both bring rules about what may be cached on the device and for how long, which shapes the offline story far more than any design decision does.
Four Questions That Matter More Than Your Sector
By the end of a first call these usually predict the shape of a project better than the industry does.
Where are they standing?
A sofa, a van, a shop floor, a loading bay. It decides screen density, tap target size, contrast and whether one-handed use is a requirement or a nicety.
What happens with no signal?
Read-only caching is cheap. Editing offline and merging later is a project of its own. Knowing which you need is the single biggest fork in a mobile estimate.
How often does it open?
Several times a day justifies an icon on the home screen. Once a quarter usually justifies a good mobile website instead, and we will say so.
Whose system does it depend on?
The integration nobody owns is where timelines slip. If there is no test environment, we schedule that work early rather than discovering it in the last sprint.
Sectors Where We Would Talk You Out of an App
Not every business needs one, and a badly justified app is worse than no app because it also needs feeding for years.
If this is you, the first call will be short and it will still be free. We would rather lose the project than build something that gets deleted.
Questions About Sector Fit
Do you need experience in our industry to build our app?
Less than you would think, and we would rather be honest about it. You know your sector far better than we ever will, and our job is to ask the questions that surface the rules living in your head. What does transfer between projects is the mobile part: how an app behaves with no signal, how a scanner integration goes wrong, what a store reviewer objects to, how to keep an app alive on a handset that is used for a full shift. That is the expertise you are buying.
Our staff use company handsets. Does that change the build?
It simplifies it considerably. When you own the devices you know the exact models and OS versions, which shrinks the test matrix and removes most of the guesswork about what will be fast enough. It also opens up internal distribution, so the app can go straight to your devices without a public store listing and without waiting on review for every update. The trade-off is that your device management system now becomes part of the project.
Would a mobile web page do the same job more cheaply?
Sometimes, and we will say so. If the job is reading information, filling in an occasional form or checking something once a month, a good mobile website is cheaper and needs no install. An app earns its cost when you need the camera, Bluetooth, background location, reliable push notifications, real offline use, or an icon that someone taps several times a day out of habit. If none of those apply to you, the honest advice is to spend the money elsewhere.
We are not on this list. Does that matter?
No. These are the sectors where the mobile constraints are sharpest and most worth writing about, not a list of who we will work with. The useful question is never which industry you are in, it is where the person is standing when they open the app and what has to keep working when the signal goes. Answer those two on a call and the sector mostly stops mattering.
Tell Us Where Your Users Are Standing
Describe the job the app has to do and the conditions it has to do it in. You get a scope, a timeline and a cost range back within two business days.