Firefox 36 arrives with full HTTP/2 support and a new design for Android tablets
Mozilla today launched Firefox 36 for Windows, Mac, Linux, and Android. Major additions to the browser include full HTTP/2 support and a new tablet user interface on Android.
Context & Ripple Effects
Firefox 36 lands a month after Firefox 35 added Hello video chat, an Android download manager, and Mac MP4 playback, continuing Mozilla's rapid-release cadence of shipping a major version roughly every few weeks. This release closes the loop on HTTP/2, turning the new web protocol from partial to fully supported across Windows, Mac, Linux, and Android.
The second headline change — a purpose-built tablet interface for Android — extends the Android work from recent releases onto a form factor Mozilla had been treating as a scaled-up phone. Together they signal Mozilla competing on plumbing (protocol speed) and surface polish at once.
First-order effects
- Sites and servers that have deployed HTTP/2 can now serve Firefox users the protocol's full benefits rather than falling back, making Firefox a complete client for the upgraded web.
- Android tablet owners get a native-feeling Firefox UI instead of a stretched phone layout, directly addressing the weakest point of Mozilla's mobile presence.
Second-order effects
- The tablet redesign raises the bar for the Android work that follows — by Firefox 40's Windows 10 support and new Android navigation gestures later in the year, per-device fit had become a standing part of each release rather than a one-off.
- Full HTTP/2 support pressures laggard publishers and hosting providers: with Firefox now complete on the protocol, serving over the older standard increasingly means leaving measurable performance on the table for a major browser share.
Third-order effects
- If the pattern holds, Mozilla keeps trading breadth for currency — the same logic that later produced Firefox 48 dropping old OS X versions and Android Gingerbread begins here, with each release assuming newer protocols and devices and letting legacy support go.
- Protocol adoption becomes a browser-vendor responsibility: as with the rendering and autoplay defaults Mozilla shipped years later in Firefox 66, the browser itself turns web-standard upgrades into user-visible behavior, making vendors the enforcement mechanism for the web's infrastructure transitions.
The trend: Browser makers are absorbing the web's infrastructure upgrades — protocols, rendering, platform defaults — into their rapid-release cycles, so standards adoption now moves at the pace of version ships.