I wrote an article, The Changing Form of the Web Browser, for rehabstudio (my employer). It’s about the present and near-future of the web browser, in a market where the consumption of information and services is shifting. It’s quite a long piece, and necessarily broad for a non-technical audience, so there is perhaps a lack of nuance in its conclusions. Still, I’m quite proud of it, a lot of research and writing was involved.
There’s an extract below, but I suggest you read the whole thing in context if you can.
Rachel Andrew. Relly Annet-Baker. Naomi Atkinson. Alice Bartlett. Frances Berriman. Jina Bolton. Alice Boxhall. Tiffany B. Brown. Sara Chipps. Geri Coady. Anna Debenham. Hannah Donovan. Natalie Downe. Sylvia Eggers. Fantasai. Morena Fiore-Kirby. Zoe Mickley Gillenwater. Kristina Halvorson. Jessica Hische. Lara Callender Hogan. Molly Holzschlag. Denise Jacobs. Sally Jenkinson. Laura Kalbag. Erin Kissane. Johanna Kollmann. Gemma Leigh. Inayaili de León. Jenn Lukas. Divya Manian. Katie Marcus. Louise McComiskey. Karen McGrane. Rachel Nabors. Sarah Parmenter. Soledad Penadés. Yesenia Perez-Cruz. Leisa Reichelt. Stephanie Rieger. Natasha Rooney. Stephanie Sullivan Rewis. Linda Sandvik. Kristina Schneider. Marinda Sephton. Rachel Shillcock. Jenn Simmons. Sara Soueidan. Nicole Sullivan. Henny Swan. Kat Thompson. Lea Verou. Sara Wachter-Boettcher. Estelle Weyl. Denise Wilton.
Just some of the many women makers of the web who I’ve met, worked with, seen speaking, read, or followed their work. We’d all be poorer without their contributions.
The recent release of Firefox 31 brought an implementation of CSS Variables. Based on that, Daniel Imms wrote an interesting post, What CSS Variables Can Do That Preprocessors Can’t, where he investigates a few use cases for native variables over those provided by pre-processors like Sass and LESS (there’s a common argument that CSS variables are unnecesary as we already have them, and more flexibly, in pre-processors).
I remember reading about mutation observers a little while ago, but didn’t pay them too much attention as they didn’t have broad browser support and weren’t immediately useful to me. When I recently saw object observers land in Chrome (36) Beta, I realised that I should go back and learn about them. So I did.
It can’t have escaped your notice that iOS7 was recently released, and with it a new version of Safari. Among many additions and changes to its standards support comes (partial) implementation of the new Web Speech API. This API has two core features: speech recognition, which uses a web service to transcribe voice input; and speech synthesis, which uses system libraries to output an artificial voice. Safari for iOS7 brings support for the latter, so I’m going to briefly explain through how that works.
I recently had call to do a factory reset on my phone, and as I began the process of reinstalling all my apps again decided to try an experiment instead: to see if mobile web apps (or, sites) were up to the job of replacing native apps. With the forthcoming release of Firefox OS this is something I’ve been very curious about, but within days I was back to using native again. I’ll explain why, but lay out some of the more positive findings before I do. Note that I was using Chrome on Android for my experiment, but I think the findings should hold true for most browser and OS combos.