Android apps for business

Everything on our mobile app development page applies to an Android app, from one shared set of code for iPhone and Android to developer accounts in your business’s name. This page covers what Android and Google Play ask on top of that: the account, testing on Android phones, tablet screens, Google’s quality limits, the rules that change each year, and the Data safety form.

In StatCounter’s count of page views on the websites that run its tracking code, Android phones made 48% of US mobile web page views in October 2026, and iPhones 52%. Android’s monthly share moved between about 37% and 48% over the 12 months to October 2026, so most businesses need their app in both stores.

If your customers are in Miami-Dade, Spanish store pages and what to plan for when the cell network goes down are on our page for an app developer in the Miami area.

Google Play has two kinds of developer account, personal and organization. Google’s Play Console Help describes the personal account as for a “student, hobbyist, or amateur developer”, and the organization account as for an organization or business. An app for financial products, a health app, an app approved to use Android’s VPN service and a government app must use an organization account.

An organization account needs a D‑U‑N‑S Number, the business number our app development page explains. Google says applying for one through Dun & Bradstreet “is a completely free process”, and warns that some outside services try to charge high fees for it.

Google charges a one-time US$25 registration fee for the account. Personal accounts have a testing rule of their own: under Google’s requirements for new personal accounts, one created after November 13, 2023 must run a closed test with at least 12 testers, opted in for at least 14 days in a row, before the app can go public.

We open the account as an organization in your business’s name, with you as its owner and us as users you can remove.

The toile, our name for the working test version you try before the full build, reaches Android phones through Google Play itself. An internal test goes to up to 100 testers, and Google says a new build reaches them within minutes. It can start before the store listing is finished, so you and your staff install the real app from Google Play on your own phones early on.

When a build is uploaded, Google Play also makes a pre-launch report if its device lab has room. Google installs the app on Android devices in its test lab and taps, types and swipes through it for several minutes, then reports stability, compatibility, performance and accessibility problems. It doesn’t replace testing on your own phones, and we read it before each release.

Android phones run many versions of Android at once. In StatCounter’s figures for October 2026, Android 16 and 17 together made about half of US page views from Android phones and tablets, and Android 13 or newer about 82% (our arithmetic on its figures). Each older version the app supports reaches more people and adds phones to test, so the oldest one is agreed at the fitting and written down.

Since August 31, 2026, Google Play’s target API rule says new apps and updates must target Android 16 (API level 36, Android’s number for that version) or higher. Google’s notes on Android 16 say that for those apps, a lock to portrait or to a fixed shape no longer applies on large screens: those at least 600 dp across their shorter side, where dp is Android’s unit for screen size. On a screen that size, such as a tablet, the app fills the whole window whichever way the device is turned. Games are left out, and so are phone-sized screens.

Google lists what tends to break in an app designed for a phone held upright: stretched layouts, and animations and parts of the screen pushed out of view. Turning the device also rebuilds the screen more often, which can lose what the user was doing if the app doesn’t keep it. Apps can opt out for now, but Google says the opt-out is temporary and won’t apply once apps target API level 37.

Google Play keeps grading an app after launch. Android vitals, Google’s quality figures for each app, include limits on crashes and freezes: a crash rate of 1.09% on average across devices, or 8% on any one phone model, and a freeze rate of 0.47% on average, or 8% on one phone model. Google checks them every day, using a 28-day average.

Google’s word for a freeze is an ANR, “Application Not Responding”: the app stops answering for too long, and Android shows a box that lets the user force it to close.

Above any of these limits, Google says, “Play may reduce the visibility of your title”, and it may show users a warning on your store listing. We can’t promise where an app shows up on Google Play. What we do:

Google let developers ask for an extension of the August 31, 2026 target rule to November 1, 2026. That date has passed, so an update sent now has to target Android 16 or higher. An app already on Google Play that targets Android 14 or older isn’t offered to new users whose phones run a newer Android than it targets. An app kept permanently private to one organization’s own users is outside the rule.

From February 1, 2027, says Google’s page on 16 KB memory pages, an update that doesn’t support them on 64-bit devices can’t be released on Google Play. An app written only in Java or Kotlin, the kits it uses included, already supports them. An app with native code, its own or inside a kit (ready-made code from another company, such as for payments or analytics), has to be rebuilt and checked before that date.

Google is also bringing in Android developer verification, which checks who the developer behind an app is. Google says Google Play registers 99% of apps for it automatically. It began on September 30, 2026 in four countries, Brazil, Indonesia, Singapore and Thailand, and Google says it goes worldwide in 2027. It matters most if you plan to put the app on staff phones without Google Play, so the developer identity is settled before then.

Android vitals adds memory limits as well: Google says apps over its memory thresholds may see their store visibility affected from February 2027. So the upkeep plan, with who makes each update and by when, is written before launch.

Every app on Google Play needs a completed Data safety form, closed and open test versions included, and a link to a privacy policy, even if it collects no data at all. The answers have to cover data handled by the outside kits inside the app as well. Google says the developer alone is responsible for complete and accurate answers, and that it may take action when the app does something its answers don’t say.

So we draft the answers from a written list of what the app collects and where each piece goes, and you check them as the account holder before they reach Google.

Google Play uses two keys. With Play App Signing, Google keeps the app signing key, which signs the app your customers install. Your business keeps the upload key, which signs each new build before it goes to Google, and Google can reset it if it’s lost or stolen. That upload key is among what you hold at the end.

An Android-only app fits when everyone who’ll use it carries an Android phone, such as staff on phones the business hands out. If it stays private to your own staff, the yearly target rule above doesn’t apply to it either.

Ask every Android app developer you talk to. Our own answers follow each question.

Wico Business Solutions is at 3909 NE 170th St, North Miami Beach, FL 33160. To talk about an Android app, call or text (786) 396-4065, use the contact form or email info@wicobusinesssolutions.com. We reply by email, phone or text, in English or Spanish. If it’s work we do, we set a time for the fitting, and we’ll tell you there if a website or an iPhone-only app would serve you better. A price and a finish date follow that call, and work begins once you’ve agreed to both.