/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

← → days · ↑ ↓ browse · Enter similar · o open

Flash, HTML5, and Mobile Apps

About a year ago, I wrote a post about Apple's “blind spot” for Flash.  I took more heat for that post than anything else I've written here other than political posts.  It opened my eyes to the fact that Flash vs HTML5 is one of the most politically heated topics in the tech business.

A VC Fred

Context & Ripple Effects

This post is Fred Wilson returning to an argument he made roughly a year earlier — that Apple had a Flash "blind spot" — a take he says drew more reader hostility than anything else on his blog short of politics. His updated framing is that Flash vs HTML5 is less a technical dispute than a political one, among the most charged topics in the business.

The timing matters: it lands mid-stretch of Apple self-sufficiency moves logged in early February 2010 — engineers publicly correcting reporting on the in-house A4 chip, ad-industry recruits putting Apple head-to-head with Google in UK mobile advertising, and AT&T finally permitting VoIP apps over 3G. TechCrunch carried the same Flash-vs-HTML5 framing the same week, showing how far the question traveled.

First-order effects

  • Publishers and developers running Flash-based content face an immediate fork on Apple's mobile devices — port to HTML5 or ship native apps — because the platform simply won't render Flash.
  • Adobe loses default-runtime status wherever iPhone OS spreads: every Flash-dependent site becomes, in effect, broken inventory on the fastest-growing computing category.

Second-order effects

  • Google gains a differentiation lever: backing Flash on Android lets it position itself as the open alternative precisely where Apple blocks, turning plugin support into a platform-war weapon rather than a compatibility checkbox.
  • Apple's parallel February 2010 push into mobile advertising means the fight is not just about formats — whoever controls the content runtime controls the ad slots, directly colliding with Google's core business.

Third-order effects

  • If device makers can veto web technologies at the platform level, the open web fragments into per-platform sanctioned stacks, and HTML5 adoption accelerates fastest where a gatekeeper forces it.
  • Standards governance becomes strategic: the real contest shifts from whether HTML5 displaces Flash to who steers its video, advertising, and app-like capabilities — a structural fight between platform owners and the open-web coalition.

The trend: Mobile platform gatekeepers are replacing browser plugins with native apps and HTML5 as the sanctioned content layer, converting web standards into instruments of platform competition.