GBCORP BLOG · IT SERVICES
Android Application Development: Every Phone, One Build
Android is most of the world's phones, from the newest flagship to a five-year-old budget model on a slow connection. Android application development has to work on all of them, and ship iOS from the same release.
Android application development produces an app that runs across thousands of device models and several operating-system versions, passes Google Play’s policies, and reaches the customers who carry Android, which in most markets is most of them. GBCORP builds Android apps from a single codebase that produces iOS and the web from the same release, so a business gets every platform for one build, and runs its own apps on the Play Store, which is the only guarantee that a policy change will be handled in time.
What Android demands
| Demand | What it means | How GBCORP handles it |
|---|---|---|
| Devices | Screen sizes from small to foldable; memory from 2 GB up | Layouts tested on real budget and flagship devices |
| Versions | Several operating-system versions in use at once | Support back to the versions customers actually run |
| Connections | Slow and intermittent networks | Cached content, retries, offline queues |
| Play policies | Data safety form, account deletion, target version, permissions | Handled in the engine; own apps live |
| Payments | Play Billing for digital goods; the business’s gateway for physical goods and services | Engine routes by product type |
| Sign-in | Google, phone, e-mail; Apple’s when iOS ships too | Engine |
One codebase, Android and iOS together
Screens are written once and rendered with each platform’s conventions. Backend, logic and console are shared. A release is tested on both platforms and submitted to both stores the same day. A business that needs Android first ships Android first and adds iOS when it wants, from the same release, for the cost of testing.
Play Store policies that reject apps
Missing or wrong data-safety declarations. No account deletion in the app. Targeting an old operating-system version. Permissions the app does not need. Generated content without moderation. Digital goods sold outside Play Billing. GBCORP’s engine handles each, and its own apps pass review on every release, including the policy deadlines that catch abandoned apps.
Testing on real devices
Every release is tested on real Android devices across budget and flagship models, screen sizes and versions, on slow connections, with notifications, payments and sign-in exercised. A test build reaches the client’s phones every two weeks through the Play Store’s own test track. Crashes and slow screens are measured in production after launch.
Checklist before commissioning an Android app
- The process the app runs, in ten lines.
- The devices and versions your customers actually use, from your analytics or a survey.
- Whether it sells digital goods, physical goods or services.
- Play developer account in the business’s name, or authority for GBCORP to open it.
- Whether iOS and web are needed now or later.
- The number the app should move.
The numbers to expect
Scoping in one week. A first release in eight to twelve weeks at a fixed price, submitted to the Play Store and, if wanted, the App Store the same day. A configured white-label app within days. Releases every two weeks. Support at a known monthly figure. Customised or more complex functionality is quoted separately before any work starts.
A worked example
A regional delivery company’s customers are almost entirely on Android, many on budget devices with intermittent connections. GBCORP configured the delivery engine under the company’s brand, tested on the five device models its analytics showed most, and shipped to the Play Store in a fortnight with the ordering flow cached for slow networks and an offline queue for the driver app. iOS followed a month later from the same release, for the office staff and the minority of customers who asked. The company paid for one build.
The driver and staff apps
Android is the usual choice for staff devices, and staff apps have their own demands: rugged use, long shifts on battery, offline queues that sync when the signal returns, and device management so a lost phone can be wiped. GBCORP’s field and driver apps are built for that, with photos, signatures, routes and job status working without a connection and reconciling when one appears.
Distribution beyond the Play Store
Staff apps can be distributed privately through the Play Store’s managed channel or as a signed package installed by device management, without a public listing. Customer apps go to the public store. Both come from the same codebase and release, and both are signed with keys held in the business’s own account.
Multilingual and multi-market
The app ships in the languages the business serves, with right-to-left layouts as a setting, and the Play Store listing is localised per market. Currency, tax and payment provider are configured per market, and the listing shows the business as publisher in each.
After launch
A support plan with monitoring, patches, operating-system and Play policy updates, hours for small changes and response times by severity. Crash-free sessions and slow screens are measured in production and reported. Policy deadlines are tracked so an app is never removed for missing one.
Ownership terms
Code in a repository the business controls, documented with every release. Play developer account, signing keys, cloud project, domain and payment account in the business’s name. Data exportable at any time. No commission on sales, and no credentials retained after a hand-over unless a support contract requires them.
Questions we hear first
Native or cross-platform?
One codebase rendered with native components; users and the review team cannot tell, and the business pays for one build.
Can we ship Android only?
Yes. iOS and web are produced from the same release when the business wants them.
What about old devices?
The engine supports the versions customers run, tested on real budget devices, with cached content for slow connections.
Who owns the Play Store listing?
The business: the developer account is in its name and it appears as publisher.
Where to start
The GBCORP Custom App Development product is the priced starting point; the GBCORP mobile app development hub sets out the method. For the custom route on Android, read the custom Android app explained.
GBCORP operates across 17 countries on 4 continents through six pillars: AI & IT, Innovation, Sustainability, Infrastructure, Premium Business, and EV's & Solutions.
