Firefox 35 launches with simplified Hello video chat, Android download manager support, and MP4 playback on Mac
Emil Protalinski / VentureBeat :
Context & Ripple Effects
Firefox 35 lands in Mozilla's rapid six-week release train, following the same ship-everything-at-once pattern that carried into the next cycle with Firefox 36's full HTTP/2 support. This release is mostly about closing capability gaps rather than adding headline features: native MP4 playback finally reaches Mac users, and Android downloads route through the OS-level download manager instead of an in-browser one.
The other notable move is Hello, Mozilla's WebRTC video-chat service built into the browser itself, getting a simplified interface — an early sign of where Mozilla was willing to invest versus prune.
First-order effects
- Mac users get MP4 playback directly in Firefox 35, removing a codec gap that had pushed them toward other browsers or plugin-based workarounds.
- Android users gain a unified download experience through the system download manager, so files fetched in Firefox land in the same place as app downloads.
Second-order effects
- Shipping media codecs natively erodes the last practical reasons to keep plugin-based playback installed, pressuring the plugin ecosystem Firefox itself would later cut off in Firefox 48's removal of old OS X versions and Android Gingerbread support.
- Hello's simplification signals Mozilla testing whether browser-native communications can hold users against standalone chat apps — a bet whose payoff depended on usage Firefox has never disclosed publicly.
Third-order effects
- The release fits the structural pattern across this coverage: each version trades breadth of legacy support for depth of modern web standards, a consolidation path that ends with Firefox shedding old platforms entirely rather than maintaining parity everywhere.
- If browser-native communications keep getting simplified rather than expanded, the likely endpoint is Mozilla folding Hello back or spinning it out — the maintenance cost of a second messaging surface inside a browser competing on rendering and JavaScript performance, as later releases like Firefox 58 show.
The trend: Browsers are absorbing media and communications capabilities as native features while progressively abandoning legacy platform support, with codec parity becoming table stakes rather than differentiators.