Android app development

Designing for device variety

• Screen sizes

  Small phones to tablets and foldables; layouts must adapt.

• Performance range

  Budget phones need careful attention to speed and memory.

• OS versions

  Decide the oldest Android version you will support.

• Manufacturer differences

  Some behaviour can differ between manufacturers, so test on more than one brand.

Choosing devices to test on

You cannot test on every Android device, so choose a representative set based on who your users are. If the app is for your staff, test the devices you issue. For customers, use analytics from your website or existing app to see which manufacturers, screen sizes and Android versions are common, and include at least one lower-cost device. Cloud device-testing services can extend coverage for automated tests.

Decide the minimum Android version supported with that data, not by guesswork.

From build to Google Play

1. 01

   Developer account

   Play Console account created and verified in your organisation's name.

   Output: Publishing access

2. 02

   Internal testing

   Builds shared quickly with your team.

   Output: Early checks

3. 03

   Closed or open testing

   Wider groups of testers before release.

   Output: Feedback

4. 04

   Production

   Listing, privacy declarations and release.

   Output: Live on Play

5. 05

   Staged rollout

   Release to a percentage of users first.

   Output: Safe launch

Google Play requirements to plan for

Android quality checks

Distribution outside Google Play

Many consumer Android apps are distributed through Google Play. Internal business apps can sometimes be distributed privately through device management systems, which suits company-owned devices. Private apps restricted to one organisation are also treated differently in some Play requirements. Choose the route with whoever manages your devices.

Staged rollouts and monitoring

Google Play lets you release an update to a percentage of users first. Watching crash rates, reviews and backend errors during that period catches problems that testing missed, before they reach everyone. If something goes wrong, the rollout can be halted while a fix is prepared. Combining staged rollouts with crash reporting is a practical way to protect users on such a varied range of devices.

Agree in advance what crash rate or error level would pause a rollout.

Accessible Android apps

Support system text sizes, screen readers and sufficient touch target sizes. Test key tasks with Android's built-in accessibility tools on real devices, not only in emulators.

Keeping the app current

Plan at least one update a year to meet Google Play's target API requirements and absorb Android changes. Testing on the latest Android version before it reaches most users avoids surprises.

Tablets and other form factors

If your users work on tablets, for example in shops, warehouses or clinics, design layouts that use the extra space rather than stretching a phone screen. Rugged or business devices may also have hardware buttons or scanners worth supporting. Decide early which form factors you will support, because each adds design and testing work.

The store listing

Screenshots, a clear description and accurate privacy declarations help people decide to install, and must be updated as the app changes.