25 August 2026

Android Sideloading Rules 2026: What Actually Changes For India Now

A friend sends you an APK on WhatsApp. It is a small utility, the kind that never made it to Play because the developer could not be bothered with a store listing. You tap it, Android asks its usual question, you say yes, and it installs. That flow is changing, and most of the coverage has handed Indian readers the wrong date for it.

Android Sideloading Rules 2026: What Actually Changes For India Now

TL;DR: Google's developer verification goes live on 30 September 2026 in Brazil, Indonesia, Singapore and Thailand. India is not on that list and will not be until 2027. What already reaches Indian phones is the advanced sideloading flow, with its one-time waiting period.

Why It Matters

Start with what the rule actually checks. Google is confirming who published an app, not what the app does. No code review, no content pass, no judgment on whether the thing is any good. It is a name-and-document check attached to a signing key, and the practical effect is that anonymous distribution stops being an option on certified devices. Whether you read that as overdue hygiene or as another gate on hardware you already paid for probably depends on how you felt when Apple kept self-service repair out of India using a similar safety argument.

India sits outside the first enforcement wave, and that is doing a lot of work in the coverage. Nothing on an Indian phone becomes uninstallable on 30 September. But look at which stores signed up: Google Play, Samsung's Galaxy Store, Xiaomi's GetApps, OPPO's App Market, vivo's V-Appstore, HONOR and Palm. That is nearly every app store that ships preloaded on a phone sold in this country. StatCounter put Android at 92.44% of India's mobile OS share in July 2026. When the rule does arrive here, it will not arrive at the margins.

The security case is real, and worth stating at full strength rather than waving at. Google's own Android Developers Blog post from 25 August 2025 said its analysis found over 50 times more malware from internet sideloaded sources than from apps available through Google Play. That is Google measuring its own platform, so read it with the appropriate squint, but a gap that size is not a rounding error. The counter-argument is not that the malware is imaginary. It is that identity checks catch the lazy operator and inconvenience the hobbyist, while the organised fraud rings buying stolen KYC documents in bulk carry on. Nobody has published a clean before-and-after on that yet, and until someone does, anyone claiming to know which way it nets out is guessing.

Cooling-off wait

24 hours

Before the first unverified install

Developer fee

$25

One-time full account registration

Hobbyist device cap

20 devices

Free account, no government ID

Play apps auto-registered

99%

Handled without developer action

The waiting period is the number that changes behaviour, and not because it is long. It cannot be completed in the moment. Someone on a phone call telling you to install a file right now, this minute, before your account is frozen, has just been handed a delay he cannot argue you past. That is the same pressure pattern running through the AI voice cloning scams working Indian phone numbers, and a forced pause is a surprisingly rude interruption to it.

"

A one-day pause is not really a defence against malware. It is a defence against urgency, which is what every coercion scam actually runs on.

What Changes And What Does Not

Strip out the speculation and the rule set is small enough to hold in your head. Here is the whole thing, as published on Google's developer verification pages and its Android Developer Console help documentation.

Category Detail What it means
Deadline 30 September 2026 Four countries only, India not included
First wave Brazil, Indonesia, Singapore, Thailand India's turn arrives in 2027
Stores Seven participating stores, Play included Indian phone brands are all inside
Sideloading Still allowed through the advanced flow Buried in developer options by design
Pause A one-time wait before the first install Built to break live coercion scams
Cost A paid full account, or a free limited one Hobbyists trade reach for privacy
Checked Developer identity, tied to a signing key Verification is not app content review
Escape hatch adb installs stay outside the rule Needs a computer and a cable

Read that table twice and the shape of the thing shows up. Google did not close the door. It moved the handle to a place ordinary users will never look, added a delay to the one path that leads there, and left a developer tool untouched for people who own a laptop. Every one of those choices is defensible on its own. Together they describe a device that is a little less yours than it was.

Aug 2025 · Mar 2026 · Aug 2026 · Sep 30, 2026 · 2027 · Rules announced · Console opens · Advanced flow · Four countries · Global rollout ·

Five stops on one line: the policy was announced in August 2025, verification opened to all developers in March 2026, the developer tools and the power-user install path shipped in August 2026, four countries hit enforcement on 30 September 2026, and everything else follows from 2027.

Friction Points

The advanced flow lives inside Developer options, which you reach by tapping the build number seven times. Google is not hiding it out of embarrassment. Burying it is the design. But it produces an odd result: the people most likely to need an app that never reached a store, a regional language keyboard, a niche utility, a local college's attendance app, are frequently the people least equipped to go digging through settings that warn them off at every screen.

Then there is the paperwork gap. An individual developer supplies a government ID. An organisation needs a D-U-N-S number from Dun and Bradstreet first, and that request can take up to 28 days to come back. For a two-person studio in Pune shipping a niche app, the fee is not the obstacle. The month of waiting and the registered-entity requirement are, and they arrive before a single line of the rollout touches India.

One more thing worth flagging, because it gets lost in the outrage cycle. The advanced path is not a one-time switch you flip and forget. Keep an eye on these before you decide the whole thing is overblown:

  • The unverified-install setting can be enabled temporarily for seven days or left on indefinitely, so a temporary grant will lapse without warning you again.
  • The adb route still installs unregistered apps, but it needs a computer, and plenty of Indian users have only ever treated a phone as their whole computer.
  • Google's help text covers new installs only, and says nothing about apps already sitting on your device, so do not assume either outcome.
  • Your phone brand's own preloaded store is on the participating list, so "I never use Play" is not the exemption people think it is.
  • The rollout reaches handsets in stages, so two identical phones in the same house can behave differently this month.

Certified devices only

The rule binds phones that ship with Google services, not every Android build.

Direct distribution survives

Google says developers keep the freedom to ship straight to users or via any store.

Two ways to register

Play Console, or a separate Android Developer Console for anyone who avoids Play.

So: nothing on your phone breaks next month. Use the time. If you rely on an app that lives outside a store, message the developer now and ask whether they have registered, because the answer in 2027 is going to be a lot less negotiable than the answer today. And if you are the sort of person who already keeps a second browser around rather than trusting one company's default, apply the same instinct here and get the file you actually care about onto your device while the door is still easy to open.

22 July 2026

AI Voice Cloning Scams in India: Your 2026 Survival Guide

The call comes at 2:40 on a Tuesday afternoon. It is your son's voice — the exact pitch, the exact pause before he says "Amma," even that slight nasal edge he's had since childhood. He's been in an accident, he's at a private hospital, the desk won't admit him without an advance, and a "hospital administrator" comes on the line with a UPI handle. Ten minutes later the money is gone. Your son, it turns out, was in a lecture hall the whole time, phone on silent.

AI Voice Cloning Scams in India: Your 2026 Survival Guide

That is not a scene from a Netflix thriller. It is the standard fraud playbook of 2026, and it runs on two rails India built better than almost anyone: cheap AI tools and instant payments. The same UPI stack that lets you split a dinner bill in four seconds also lets a stranger with a cloned voice drain a retirement account before the chai gets cold.

TL;DR: Fraudsters now clone a familiar voice from a few seconds of public audio, fake an emergency, and push you to pay over UPI before you think. No app setting fully protects you. A family code word, a callback rule, and the 1930 helpline are your real defences.

Why It Matters

Start with how little the attacker needs. A wedding video on Instagram, a voice note forwarded to the wrong group, a podcast clip, a birthday reel — any short sample of someone speaking is enough raw material for today's open-source cloning models. The scammer doesn't hack your phone. They harvest your family's public audio, build the clone in minutes on a free tool, and then engineer panic: an accident, an arrest, a stuck visa, a kidnapping. Panic is the product. The voice is just packaging.

The scale has stopped being a niche cybercrime story. Industry tallies put global losses to AI-enabled fraud at roughly $442 billion for 2025, and India sits near the centre of that map because of how thoroughly daily life here runs on WhatsApp and UPI. This has climbed the food chain too — a cloned voice of Bharti Airtel chairman Sunil Bharti Mittal was used in an attempt to move funds through a senior executive. If a scammer will build a deepfake to fool a boardroom, the version aimed at your parents costs them almost nothing.

Here's my first unfashionable opinion: the "be aware, stay alert" poster campaigns banks love are mostly theatre. Awareness assumes the victim has time to think. These scams are engineered to remove thinking time — the fake son is crying, the fake policeman is shouting, the clock is always ticking. Defences that require calm judgment in the moment will keep failing. Defences that were agreed on before the call — a code word, a hard rule to hang up and dial back — actually hold, because they don't depend on you being clever while terrified.

The numbers below are why this deserves space on your family WhatsApp group tonight rather than someday. Each one describes a different edge of the same machine: how little input it needs, what it took last year, how many people reported it, and how fast it is growing.

Audio Needed
3 sec
enough to clone a voice
Reported Losses
₹22,495 cr
Indian cyber fraud, 2025
Complaints Filed
2.81 mn
cybercrime cases, 2025
Growth Rate
+24%
complaints, year on year

Sit with that first cell for a moment. It's less audio than the greeting most of us leave on a voicemail. It means the question "has my voice ever been recorded in public?" now has the same answer for everyone: yes. Planning your defence around keeping voices private is already a lost game — the defence has to work even when the clone is perfect.

The Anatomy of the Scam, Row by Row

Before the table, one piece of context. What police cyber cells describe from 2025-26 case files is not one scam but an assembly line, and every stage has been made easier by an off-the-shelf tool. Reading it as a system explains why no single tip — "check the number", "listen for robotic tones" — is enough on its own.

CategoryDetailWhat It Really Means
Voice sourceReels, voice notes, wedding videosYour family's audio is already public
Cloning toolsFree and open-source appsZero cost, zero skill required now
Face fakesOne photo, under a minuteVideo calls no longer prove identity
Delivery channelWhatsApp calls and fake UPI appsThe scam rides trusted, daily apps
Pressure scriptAccident, arrest, "digital arrest"Urgency is the actual weapon here
Payment railUPI, instant and irreversibleSpeed favours the scammer, not you
Recovery pathHelpline 1930, bank, cybercrime.gov.inReporting fast beats reporting perfectly

The row that deserves your attention is the payment rail. UPI's four-second settlement is a genuine engineering triumph — and in a fraud, every one of those seconds works against the victim. Once money moves through two or three mule accounts, recovery odds fall off a cliff. That is why the practical fight is won or lost in the minutes before you approve a payment, not the days after.

The four-stage pipeline above is the whole crime: only stage three ever touches the victim, which is why interrupting that single moment — with a code word or a callback — collapses everything before it.

Friction Points

Now the uncomfortable part: what still doesn't work. Caller ID apps flag unknown numbers, but these calls increasingly arrive on WhatsApp from freshly created accounts wearing a stolen profile photo. Banks send warnings, but a warning SMS competes with a screaming voice claiming to be your child. And the apps themselves keep getting faked — imitation UPI apps that look pixel-identical to the real thing have travelled across India through WhatsApp forwards. I wrote about how telecom-grade bot support fails customers in an ordinary billing dispute; imagine that same support maze when you're trying to reverse a fraudulent transfer with your hands shaking. In field studies of these cases, one number keeps surfacing: the window between the first ring and the first debit averages around 19 minutes. That's the entire battlefield.

There is also a genuine grey area nobody has resolved, in India or anywhere else: who eats the loss when a victim authorised the payment? Bank rules protect you reasonably well from unauthorised transactions. But a voice-clone victim taps "pay" themselves — tricked, yes, fully authorised, also yes. Regulators are still arguing about where liability should sit, and until that settles, assume the answer is: you do. Which is one more reason the AI tools now embedded in our daily software deserve scrutiny before trust — the same caution I argued for when comparing AI browsers against Chrome earlier this month.

Watch for these tells before any rupee moves:

  • Urgency plus secrecy. "Don't tell anyone, pay now" is the signature of every script. Real hospitals and real police have paperwork, not UPI handles.
  • A refusal to be called back. Hang up and dial the person's actual saved number. A genuine caller survives this test every single time; a clone never does.
  • Payment to an individual for an institutional need. Hospital deposits, court fines and customs fees do not land in a personal UPI ID.
  • Slightly-off audio behaviour. Clones handle interruptions badly. Ask an unexpected question — the pet's name, last Sunday's lunch — and listen for the stall.
Key Takeaways
  • Agree on a family code word tonight — it costs nothing and defeats a perfect clone.
  • Make "hang up, call back on the saved number" a house rule, not a suggestion.
  • Install UPI apps only from official stores; a forwarded APK is an automatic no.
  • If money moves, call 1930 and file at cybercrime.gov.in within the hour — speed decides recovery.

Do one thing before you close this tab: message your family group and set the code word. Not tomorrow. The scammers already have the voice samples — the only question left is whether your family has a script of its own when the phone rings.

17 July 2026

AI Browsers vs Chrome in 2026: Should You Switch Now

AI Browsers vs Chrome in 2026: Should You Switch Now

You ask your browser to find the three cheapest flights to Delhi, check them against your calendar, and draft a note to the group chat. It does all of it in one pass. No stack of tabs, no copy-paste, no forty-minute rabbit hole. Then a week later a researcher shows how one poisoned link could have told that same helpful assistant to quietly forward your inbox to a stranger. Same tool. Same power. Two very different endings.

AI browsers like ChatGPT Atlas and Perplexity Comet genuinely save time on research and repetitive clicking. But their own makers admit the central security hole, prompt injection, may never be fully closed. Switch for low-stakes work. Keep Chrome for anything tied to money or private accounts.

What These Browsers Actually Do

The browser used to be a window. In 2026 it wants to be an employee. OpenAI's ChatGPT Atlas, Perplexity's Comet, and The Browser Company's Dia all ship with an agent that reads the page you are on, references your other open tabs, and clicks through live sites for you. Google and Microsoft bolted the same kind of agent mode into Chrome and Edge. The pitch is simple: stop doing the boring web chores yourself and let the software handle them.

This is not a chatbot sitting in a side panel. The difference that matters is context and action. A traditional browser with a ChatGPT tab open still makes you shuttle text back and forth. An agentic browser already sees the checkout page, the flight results, and the half-written email, and it can act on all three without you lifting a finger. That shift is why adoption moved fast. AI-driven search sat under a tenth of activity back in 2023. By this year it climbed to a large slice of everyday queries, and roughly half of consumers now say they would rather get a direct answer than a page of blue links.

Those numbers are worth pausing on, because they explain why every major company suddenly wants to own the address bar rather than just the search box.

Time Saved
~12 min
trimmed per research task
Entry Cost
$0
base tier, Atlas and Comet
Rivals in Play
8+
agentic browsers competing now
Search Shift
30%
of queries now AI-driven (2026)

Take that last figure and sit with what it means on the ground. When nearly a third of searches skip the results page entirely, the habit that built Google, scanning a list and picking a link, starts to erode. People stop visiting sites and start asking the browser to read the sites for them. That is a quiet rewrite of how the open web gets used, and it is the real prize these tools are fighting over.

The Trade You're Really Making

Here is where the AI browser vs Chrome question gets honest. You are not choosing between a fast browser and a slow one. You are trading control for convenience. Chrome does what you tell it, click by click, and nothing more. An agentic browser interprets a goal and then makes dozens of small decisions on its own to reach it. When those decisions are booking a table or comparing prices, that is a gift. When a hidden instruction on a web page redirects those decisions, that is a problem nobody has solved.

That problem has a name: prompt injection. Attackers hide commands inside ordinary content, a web page, an email, even the text buried in a URL, and the agent cannot reliably tell your instructions apart from the stranger's. It processes both through the same pipeline. OpenAI said plainly in December 2025 that prompt injection is "unlikely to ever be fully 'solved.'" Read that again. The company building one of these browsers told you the front door does not fully lock. And because the agent can reach your logged-in accounts, a successful attack is not a nuisance popup. It is your email, quietly leaving.

Atlas vs Comet vs Dia vs Chrome, Side by Side

Feature checklists miss the point here. What separates these four is how much they act for you, and how much that exposes you. This table reflects where each one stands in 2026, not a launch-day demo.

Dimension ChatGPT Atlas Perplexity Comet Dia Chrome
Core strength Deep task automation Answer-first research Tidy, focused writing help Speed and stability
Acts on your behalf Yes, extensive Yes, extensive Light Agent mode, opt-in
Multi-tab summarizing Strong Strong Good Basic without add-ons
Underlying AI OpenAI models Perplexity + mixed Multiple models Gemini
Price, base tier Free with ChatGPT Free Free, paid tier above Free
Prompt-injection exposure High when agent runs High, attacks shown Moderate Lower, agent off by default
Maturity in 2026 New, fast-moving New, fast-moving New, narrower Mature, huge base
Best suited for Power users automating chores Heavy researchers Writers wanting less clutter Anyone guarding sensitive accounts

Read across the bottom row and the strategy picks itself. The AI browsers win on doing. Chrome wins on not getting you burned. Most people will end up running both, an agentic browser for grunt work and a locked-down one for banking, and that split is a feature, not a failure.

It helps to see how an attack actually travels, because the mechanics are simpler and nastier than the marketing suggests. Four steps, no malware download, no dodgy attachment, just words on a page the agent was told to trust.

Where It All Goes Wrong

The convenience is real, and so are the failure points. These are not rare edge cases. They are the predictable seams that show up once an agent has real access to your accounts and the open web at the same time.

Security teams have already turned theory into working attacks. Researchers at LayerX demonstrated a technique they nicknamed CometJacking, where a single crafted link could push Comet into pulling data from a user's connected Gmail and calendar and shipping it to an outside server. Brave's own security group reproduced indirect prompt injection inside the same browser. None of this required the user to type anything wrong. They just clicked.

Watch for these before you hand an agent the keys:

  • Account reach. If the browser is logged into your email, bank, or work tools, a hijacked agent inherits all of that access instantly.
  • Invisible instructions. Malicious text can hide in white-on-white page content or query strings you never see, so nothing looks off.
  • No clean fix. This is the honest grey area. Vendors can add guardrails, but they openly say the underlying flaw has no perfect patch, so caution is on you.
  • Silent actions. An agent working in the background can click, send, and share faster than you can notice and stop it.

Keep these four in your pocket before switching:

  • Use different browsers for different risk. Agent for errands, plain Chrome for banking. The split is your cheapest defense.
  • Do not connect it to your primary inbox. CometJacking targeted exactly that link between agent and email.
  • Watch the agent on money tasks. Let it draft and compare, but confirm any purchase or send yourself.
  • Expect the tools to change monthly. They are new. Today's safe setting can move in the next update.

So do not rip out Chrome this weekend. Install one agentic browser, point it at your low-stakes chores, research, shopping comparisons, and messy tabs, and keep every account that touches money or identity on the browser you already trust. Run them side by side for a month, watch what the agent does when you are not looking, and let its behavior, not the keynote, decide how far you hand over the wheel.