GBCORP BLOG · IT SERVICES
Custom Android App: When Android First Is the Right Call
There are good reasons to build a custom Android app first: the market, the devices, the price of the hardware in staff hands. There is no good reason to build it in a way that makes iOS a second project later.
A custom Android app is the right first build when the users are on Android: many consumer markets, most field and warehouse staff on rugged or low-cost devices, kiosks and handhelds. GBCORP builds it from the same codebase that also produces the iOS and web versions, so Android first is a sequencing decision, not a platform lock-in.
When Android leads
| Case | Why | GBCORP approach |
|---|---|---|
| Consumer markets where Android dominates | Most users on Android phones | Ship Android first, iOS in the same release when ready |
| Staff and field apps | Rugged handhelds, scanners, low-cost devices | Android is the only sensible choice |
| Kiosks and fixed devices | Tablets in a shop, a clinic, a warehouse | Android in kiosk mode |
| Devices with special hardware | Barcode scanners, printers, payment terminals | Android integrations available |
Device variety
Android runs on thousands of screen sizes, versions and manufacturers. A custom Android app is tested on the devices the business will actually use, from the cheapest phone a customer may hold to the rugged handheld a warehouse buys, and on the operating-system versions still in the field. The design system adapts layouts; the engine handles the version differences.
Staff apps and hardware
Barcode and QR scanning through the camera or a built-in scanner, label printers, payment terminals, offline capture in basements and yards, and kiosk mode that locks the device to the app: these are the reasons staff apps are Android, and GBCORP scopes each as an item rather than a surprise.
Play Store rules
A privacy policy, accurate data-safety answers, account deletion, permissions justified, and, for staff apps, private distribution to the company’s own devices without a public listing. GBCORP prepares all of it with the listing so review passes first time more often than not.
Checklist before the scoping week
- The devices the app will run on, including the cheapest and the oldest.
- Whether it is public in the store or private to company devices.
- Hardware it must talk to: scanners, printers, terminals.
- Offline needs: where the signal is poor and what must be captured there.
- Whether iOS follows, and when.
- The one number the app should move.
The numbers to expect
Scoping in one week. First release in eight to twelve weeks at a fixed price. iOS and web from the same codebase when wanted, at a fraction of the first build. Releases every two weeks afterwards. Customised or more complex functionality is quoted separately before any work starts.
A worked example
A distribution company issues rugged Android handhelds to forty warehouse and delivery staff. The custom Android app has picking by aisle with the built-in scanner, loading checks, a delivery run with proof of delivery, and offline capture for cold rooms and basements, all synchronised when the signal returns. It is distributed privately to company devices, never to the public store. The first release ships in ten weeks; the web console for dispatch is part of it. A year later the company adds an iOS customer app from the same codebase, in three weeks, because the core was already built.
Kiosk mode and shared devices
A tablet at a reception desk, a self-service screen in a shop or a check-in device at a clinic runs the app in kiosk mode: locked to the app, no home screen, automatic sign-in for the device, reset between users. Several staff sharing one handheld sign in with a PIN so actions are attributed to the person. Both are configuration in a custom Android app, and both are reasons a business chooses Android for the devices it owns.
Testing across the fleet
A custom Android app is tested on the exact devices the business owns, at the operating-system versions actually installed, with the scanners, printers and terminals connected, and in the conditions staff meet: gloves, cold, poor light, no signal. Test builds go to a handful of staff before the fleet, and their first day decides the last changes. A staff app that passes its first real shift without a workaround is the one that gets adopted.
Offline first for field work
Field and warehouse apps must work where the signal does not: forms captured, photos queued, scans stored and everything synchronised when the connection returns, without duplicates or losses. This is scoped explicitly in a custom Android app, because an app that loses a morning’s picks in a cold room is an app nobody carries. Conflict rules, what wins when two people edit the same record offline, are agreed in the scoping week.
What the client owns
The code in a repository the client controls. The cloud project, the developer account, the signing keys and the device-management configuration in the client’s name. Documentation another team could use. No credentials retained after a hand-over unless a support contract requires them. A custom Android app built this way belongs to the business that paid for it, and the devices it runs on can be managed by the business’s own IT people from the first day.
Questions we hear first
Is a cross-platform app as good as native Android?
For business apps, users cannot tell; the app compiles to a native binary. Hardware integrations are done natively where needed.
Can we distribute to staff without the public store?
Yes, through managed distribution to company devices.
What about very old Android versions?
The scoping week sets the minimum version from the devices in use; the engine supports older versions where the business needs them.
How is it priced?
A fixed price per release after the scoping week; the priced starting point is on the GBCORP e-shop.
Where to start
The GBCORP mobile app development hub sets out the approach; the GBCORP Custom App Development product is the priced starting point. For the platform comparison, read cross platform app development explained.
GBCORP operates across 17 countries on 4 continents through six pillars: AI & IT, Innovation, Sustainability, Infrastructure, Business Lounge, and EV's & Solutions.
