Scribd CTO: “We Are Scrapping Flash And Betting The Company On HTML5″ (Exclusive Screenshots)
Adobe's much-beleaguered Flash is about to take another hit and online documents are finally going to join the Web on a more equal footing. Today, most documents (PDFs, Word docs …
Context & Ripple Effects
Scribd’s move lands as Adobe is already adapting its own publishing work: the Wired iPad app was rebuilt to meet Apple’s Flash-free requirements. By shifting document rendering to HTML5, Scribd makes web-native delivery—not a browser plug-in—the core of its reading experience.
First-order effects
- Scribd must replace its Flash document viewer with HTML5-based rendering, changing the technology underpinning its document platform.
- Adobe loses Scribd as a prominent document-platform use case for Flash while it continues to support iPad publishing under Flash-free requirements.
Second-order effects
- Document publishers using Scribd gain a distribution path aligned with browsers that do not support Flash, raising the value of HTML5-compatible document tools.
- Adobe’s publishing products face pressure to interoperate with web standards as customers prioritize delivery across Flash-free environments.
Third-order effects
- If other document platforms make the same architectural choice, document viewing shifts from proprietary plug-ins toward browser-native formats and rendering stacks.
- The competitive boundary moves from owning the viewer runtime to delivering reliable web-based reading experiences across devices.
The trend: Digital reading services are moving document delivery from plug-in-dependent viewers toward HTML5-based browser experiences.