This is a MapMyTimes opinion piece. It responds to Google's announcement on 19 November 2026 that Android developer verification will start rolling out worldwide in January 2027, which MapMyTimes reported here.
The idea behind the scheme is simple. Before an app can be installed on a certified Android phone, the developer behind it should be a known, verified party, whether the app comes from Google Play, another store or a website. Google says it wants to make it harder for bad actors to keep spreading harm under new names. That is a reasonable goal. But for a country such as India, where Android phones are in very wide use, the announcement leaves two questions unanswered: when, and on what terms for people who choose to install apps from outside the big stores.
What has Google actually promised?
Google has promised a global start in January 2027 and a gradual expansion after that. In a post on the Android Developers Blog, Matthew Forsythe, Director of Product Management for Android App Safety, wrote that the rollout will begin in partnership with seven app distributors: Google Play, Galaxy Store, Honor, Oppo, Xiaomi, Transsion and Vivo. Protections will then "gradually expand to all countries" and cover all installation sources "over several months". The first phase went live on 30 September 2026 for participating stores in Brazil, Indonesia, Singapore and Thailand.
Google also says millions of apps have been registered since verification opened to all developers in March 2026, that these apps represent over 99% of Android installs worldwide, and that registering an app takes less than ten minutes.
Why a clear India timeline matters
The post does not name India or give a country-by-country calendar. That gap matters more here than in most markets. Indian users install apps not only from Google Play but also from phone makers' own stores and from websites, and several of the partner brands named by Google sell phones in India. If the switch is flipped without warning, users may suddenly find a familiar app blocked or wrapped in warnings, and the developer may not know why.
A published date for India, announced months ahead, would let developers register in time, let phone makers prepare their stores, and let banks, telecom companies and government departments tell customers what to expect. Fraudsters also study rollouts, so a public calendar should come with public guidance on what a genuine warning screen looks like.
The strongest case against the plan
The fairest objection is about control. Android's openness has long meant that anyone could build an app and hand it to anyone else. Requiring identity checks for every developer, run through one company's console, concentrates a great deal of gatekeeping power in Google's hands. Independent developers, privacy-minded users and people who rely on open-source apps can reasonably ask what happens if their registration is rejected, delayed or revoked, and to whom they can appeal.
Google has made concessions. It launched limited distribution accounts in August for students and hobbyists, without registration fees or government ID checks, and has now raised their sharing limit from 20 to 50 authorised devices. It has published guides for open-source registries and other distributors. It also describes an "advanced flow" that lets experienced users install unregistered apps "when they choose to accept the risk", while keeping guardrails against scams. Those are real steps. But the advanced flow has not been explained in the announcement itself, and an escape hatch that is hard to find or changes without notice would quietly turn a safety measure into a lock-in.
What should happen next
This newspaper thinks verification can be a sensible defence against repeat offenders who push harmful apps through links and messages, as long as it comes with three commitments. First, Google should publish dates for India and other large markets well before enforcement, not after. Second, it should set out in plain language, and in Indian languages, how the advanced flow works, so that informed users keep a real choice. Third, there should be a clear, time-bound appeals process for developers whose registration is refused or suspended, with reasons given.
Indian regulators and consumer bodies also have a role. They can ask Google and its partner phone makers to explain how the rollout will reach Indian users and how complaints will be handled. MapMyTimes has explained what the change means for sideloading; the next step is for Google to answer the open questions before January, not during it.
Safety and openness do not have to be opposites. Google says the same thing. It now needs to prove it with dates, rules and a route of appeal that Indian users and developers can see in advance.




