"Will our internal Android apps stop working once September arrives?" Answering this question requires reviewing the countries of use, app distribution channels, and device management methods. This is not an announcement that all apps in Japan will shut down simultaneously in September 2026.
Correction on September 17, 2026: In line with the official scope of application, we revised statements from the earlier version claiming a "full mandate in September 2026," that "all apps are affected," and that "apps will uniformly stop working even via MDM." We also removed unverified application turnaround times and mentions of migration packages offered by our company.
This article provides an analysis based on Google's official documentation verified on the same date. We have not conducted operational verification on actual Android devices, distribution consoles, or MDM environments.
Checking the scope beginning on September 30
According to Android's official guidance, protections will begin on September 30, 2026, across target app stores in Brazil, Indonesia, Singapore, and Thailand. Target devices are certified devices running Android 7 or later. Global rollout is scheduled for 2027 and beyond.
The initial target app stores listed in the official guide are Google Play, HONOR App Market, OPPO App Market, Galaxy Store, Palm Store, V-Appstore, and GetApps. As target regions and channels will expand in the future, please re-verify the requirements whenever you change your deployment or distribution approach.
For enterprise apps, rather than looking solely at development bases or headquarters locations, the priority is to examine the countries where actual users are located and how apps are distributed. Even for Japanese companies, apps used by local subsidiaries in target countries must be reviewed individually.
This diagram is an analytical summary created by GH Media based on official guidance to aid decision-making. It does not reflect results tested on physical devices. Rather than judging based purely on dates, please use it to verify distribution conditions.
Categorizing internal apps by "from where and to which devices"
Applicability cannot be determined simply by labels like "internal-use" or "we use MDM." The official FAQ explains that apps distributed from an enterprise store to managed devices do not need to complete verification requirements. However, it recommends registering them anyway in case you distribute through alternative channels or to unmanaged devices.
| Distribution and usage scenario | What to check first |
|---|---|
| Distribution from an enterprise store to managed devices | Whether those devices and distribution meet the FAQ exception criteria |
| Distributing APKs from company websites or file shares | Region of use, device certification status, upcoming rollout phases, registration status |
| Using both Google Play and distribution outside Google Play | Registration status of packages and signing keys handled under the same developer account |
| Installation via ADB during development and testing | Separating development-time checks from distribution verification for general users |
The FAQ states that installations for development and testing using ADB will continue to be supported. Do not assume that general user distribution will proceed without issue based solely on the fact that an app ran over ADB.
Nor is this a system where distribution outside the Play Store is uniformly prohibited. The official guide outlines multiple pathways, including distributing registered apps and additional steps users take to install unregistered apps. When designing regular enterprise distribution, verify which actions will be required of your target users.
Separating account verification from app registration
Taking action involves more than just verifying identity or organizations. The official guide also explains the registration process that links developer accounts to app package names and signing keys.
- When using Google Play: Start by checking the existing Play Console. Review target registration statuses, including the handling of keys and apps also distributed outside Google Play.
- When distributing exclusively outside Google Play: Check the guidance in the Android Developer Console.
This article does not provide a uniform timeframe for application and registration processes. This is because timelines vary depending on account status, requested documents, and review progress. Please plan based on the notices actually displayed and the targets requiring action.
Inventories to prepare as an app manager
Before deciding on refactoring or changing distribution methods, gathering the following information on an app-by-app basis will make reviews with development partners and system administrators run much smoother.
- User location countries and devices: Android version, certification status, and whether devices are company-managed or personal.
- Distribution channels: Play, enterprise stores, internal websites, file distribution, etc. Whether the same channel is used for updates.
- Managing entity: The entity managing the account, responsible personnel, package names, and the entity managing signing keys.
- Registration status and missing items: Details confirmed on the console, additional procedures required, and unconfirmed criteria.
- Distribution testing plan: Differentiating fresh installs from updates on test devices, and verifying across the actual channels used.
This is an approach to verification organized by the editorial team, not a procedure that guarantees operation across all environments. When documenting results, be sure to record the device, region, distribution method, and verification date.
Rebuilding apps or migrating to PWAs involves a separate evaluation incorporating feature usage, offline requirements, device management, and maintenance considerations. It is critical not to conclude that a full-scale app migration is required solely because of this policy change.
If you are unable to fully sort out your company's distribution conditions, please outline your app's purpose, target countries, distribution methods, and managing entity, and contact us through the inquiry form.
