Skip to content

← Writing

engineering

The Huawei Ban: Platform Risk in Your Pocket

· Jerwin Arnado

Archive note: this is a backdated post, written years later while rebuilding this site. It’s dated to the moment it covers, but the hindsight is real.

On May 16, the US government added Huawei to its export entity list, and within days Google announced it would suspend the company’s access to Android services. Not the open-source core — Huawei can still build AOSP — but the parts people actually feel: Play Store, Gmail, YouTube, Maps, the update pipeline, the whole Google Mobile Services layer.

For Washington and Beijing, this is a trade-war chess move. For the Philippines, it’s personal: Huawei is one of the most popular phone brands in the country. The group chats this week are full of one question — “Magka-update pa ba ang phone ko?” — and the answer, honestly, is “probably, for now,” which is not the kind of answer a ₱25,000 purchase is supposed to have.

What actually happened, minus the panic

Sorting the facts from the stampede (some local sellers reportedly saw panic reselling within days):

  • Existing phones keep working. Google confirmed current devices retain Play Store and services. The cliff is for future devices and, murkier, future Android version updates.
  • Android-the-OS isn’t Google’s to revoke — it’s open source. What’s revocable is the proprietary service layer on top, which is where a decade of app ecosystem actually lives. An Android phone without GMS boots fine and feels broken.
  • The reprieves and 90-day licenses now being issued can extend timelines, but the structural fact is delivered: a US policy decision can reach into a Chinese-made phone in a Filipino pocket and change what it does.

The lesson I keep turning over

I write software for a living, and this is the largest possible demonstration of a thing we usually discuss at API scale: dependency risk. Huawei built a world-class hardware business on top of a service layer it didn’t control, governed by a jurisdiction it doesn’t operate under. The dependency was invisible exactly as long as it was reliable — like every dependency.

The same shape, at every scale I work with:

  1. The platform you build on is a counterparty, not a fact of nature. Google services, an app store, a hosting provider, a payments API — each one is someone else’s policy surface. Most days that’s fine. The Huawei lesson is that “most days” is load-bearing.
  2. Switching costs are the real lock-in. Huawei reportedly has a fallback OS in development, and it will discover what every migration discovers: the code is the easy part. The ecosystem — apps, habits, developer attention — is the moat, and it isn’t theirs.
  3. Geopolitics is now part of the threat model. That sounds absurd for a web dev in the provinces, until you remember the SDKs, clouds, and services in any modern stack cross at least three jurisdictions before breakfast.

For the PH buyer, practically

Existing Huawei phone: keep it, it works, don’t panic-sell at a loss to someone who read the headline slower than you. Buying new this month: the honest answer is that you’re pricing in a geopolitical variable nobody can forecast, and the discount would have to reflect that.

And for those of us building things: audit which “Google layer” your own product has — the dependency so reliable you forgot it was a decision. Everyone has one. Huawei just found theirs.