Birmingham mobile app briefs divide into customer products and staff tools
Search demand across the West Midlands is dominated by people looking for app developers, but the enquiries behind those searches are two different purchases. One group wants something the public will install: a booking product, a membership card, a marketplace. The other wants a tool for people already on the payroll, running a delivery round, walking a warehouse aisle, inspecting a site or collecting a signature at a customer's door. The second group is larger here than in most cities, because the regional economy is built on logistics, manufacturing, construction and field service.
The distinction matters because almost every decision downstream depends on it. A consumer product lives or dies on acquisition and retention. A staff tool lives or dies on whether it survives a ten hour shift in a van with poor signal and gloves on. Suppliers who treat both as the same job produce a mobile app that demonstrates beautifully and fails in the field.
The device estate shapes the build more than the design does
Before any studio quotes, write down what your people actually carry. Company issued handsets on a refresh cycle, personal phones under a bring your own device policy, rugged terminals with integrated scanners, tablets mounted in cabs, or some mixture that changed last time procurement got a better deal. Note the oldest model still in service and the oldest operating system version you have to keep alive.
That list drives cost. Supporting recent hardware is straightforward; supporting a seven year old handset that will not be replaced this financial year is a testing burden that has to be paid for. Scanner hardware brings its own complication, because an integrated barcode reader is reached through a manufacturer interface rather than the camera, and a supplier who has never worked with that hardware will underestimate it confidently.
Offline behaviour is a requirement, not an edge case
Signal drops in steel framed buildings, in basements, in yards and along stretches of road between depots. If the mobile app stops being useful when the connection does, your staff will go back to paper and the project quietly fails. Offline capability is not a checkbox, though; it is a set of decisions somebody has to make explicitly.
Decide what can be created while disconnected and what cannot. Decide how long cached data stays valid. Decide what happens when two people change the same record and the device reconnects, because silent overwriting loses work and blocking everything frustrates users. Ask each candidate supplier to describe their conflict resolution approach in plain language. If the answer is only that the mobile app syncs automatically, they have not thought about it.
Getting the software onto staff devices without a public listing
An internal tool usually should not sit on a public store at all. Enterprise distribution through a device management platform lets you push updates, wipe a lost handset, lock the app to a single screen for warehouse use and avoid a review process designed for consumer products. It also means your staff never see an install prompt asking them to sign in with a personal account.
The practical question is who administers that platform. If your organisation already runs one for email and security, the mobile app should be delivered into it, and your supplier needs to know how to package builds accordingly. If you do not have one, adding it is a separate purchase with its own licensing, and it belongs in the business case rather than appearing as a surprise in week nine.
Permissions, battery and the complaints you will hear first
Location tracking, camera access and background activity are the three things that generate resistance from staff and questions from their representatives. Decide early what you genuinely need. Continuous background location has a real battery cost and a real trust cost, and in many operational cases a location captured at the moment of a scan or a job completion answers the same business question without either.
Write the justification for every permission before the build starts, and make sure the wording shown on the device matches it. Battery behaviour deserves a test of its own: a full shift on a single charge, with the screen on as often as it will really be, on the oldest handset in the estate. This is the sort of test that never appears in a quote unless you ask for it.
Judging suppliers on the work you can install
Ask for products you can put on a phone yourself rather than a reel of animations. Look at how often each one has been updated, whether it still supports the current operating systems, and what the public reviews complain about. A team with a long record of small releases is telling you something a case study cannot.
Ask also who would be assigned and whether that person has worked with the kind of hardware you use. Regional suppliers here are often small, which is an advantage for attention and a risk for continuity, so agree what happens if the lead developer leaves mid project and insist the code lives in a repository you own from the first commit.
Comparing mobile app companies in Birmingham
Brief three or four suppliers with the same written document, including the device list, the offline expectations and the distribution method, then compare their exclusions rather than their totals. Where a supplier has assumed you will supply the backend interfaces, check whether you can, because an internal system that cannot be reached from outside the building will hold the whole schedule.
Work that reaches beyond the handset is usually shared between specialists, so the service interfaces might come from bespoke software teams in the city and the public facing layer from local web development firms. The full supplier list across the country is in the mobile app development directory, and neighbouring pools such as Nottingham or Leeds are worth adding when your requirement is specialised. Once the document is ready, send it to several verified suppliers at once so the responses can be compared line against line.