Microsoft, Adobe, and rich versus reach
With the alpha release of Apollo, all the pieces are on the table and developers can start to experiment with the platforms from Adobe and Microsoft, arguably the two biggest players in the RIA-technology space (as opposed to RIA-solutions themselves).
Context & Ripple Effects
Adobe's Apollo alpha moves the rich-internet-application contest from slideware to code: developers finally have something to install, and the immediate analyst framing — Michael Gartenberg asking whether this is Apollo versus WPF — shows the release being read on day one as a two-platform race rather than a tools drop. Adobe and Microsoft are positioned as the two biggest players in RIA technology itself, distinct from the RIA solutions built on top.
Microsoft arrives with the opposite asset mix: WPF rides the Windows installed base, and the company closed its TellMe acquisition the same day, signaling how much client-side surface it is accumulating at once. That is the tension in the headline's 'rich versus reach' — Adobe's runtime promises richer experiences, Microsoft's stack reaches every Windows desktop already.
First-order effects
- Developers get their first hands-on window into Apollo, letting them judge the rich-versus-reach trade-off directly against Microsoft's WPF tooling instead of against paper specifications.
- The alpha reframes Gartenberg-style commentary around an explicit Apollo-vs-WPF axis, forcing early adopters to pick a primary platform commitment rather than dabble in both.
Second-order effects
- Adobe has to win developers on richness and cross-platform promise alone, because Microsoft's reach advantage — a runtime tied to the Windows base — means Adobe cannot compete on distribution.
- Agencies and independent software vendors building RIA solutions face a fork: whichever runtime accumulates components and reference apps during this experimentation phase becomes the default they staff and retrain for.
Third-order effects
- If the pattern holds, the meaningful application layer migrates to vendor-controlled runtimes sitting between operating system and browser, making runtime owners rather than browser makers the gatekeepers for desktop-class web apps.
- A market with room for many web frameworks consolidates into a small set of platform vendors, pushing smaller toolkit builders into niche integrations on top of Adobe's and Microsoft's stacks.
The trend: Application development is shifting toward vendor-controlled runtimes competing to own the desktop-to-web boundary, with Adobe's Apollo and Microsoft's WPF as the opening contenders.