What if everything was powered by “The Web”, but you never saw a browser?
This is a big question. As an industry would we be happy with the user hardly ever seeing a web browser anymore? Or is that the one thing that is sacrosanct?
I think my original classifications: Notifications, Physical, Embedded and Integrated, were not a million miles off where I think the platform is headed.
</q>
It's a long argument / technical exploration of what a web-served world not mediated by browsers, but through notifications, native apps, embedded systems, etc., would look like. More Web-as-data-back-end than Web-as-content-delivery, in one view that occurs to me.
That said: the article wanders, doesn't start with or come to a point, and is difficult to follow. It's more a thinking-out-loud exploration than clear draft IMO.
> That said: the article wanders, doesn't start with or come to a point, and is difficult to follow. It's more a thinking-out-loud exploration than clear draft IMO.
I would say that is true, there are a lot of different threads that I am trying to pull together at the moment.
Quick off-the-cuff bits (like this comment), or things I've been thinking about for a long time, can just spill out. It's the ideas I'm still putting together which I've got to struggle with most, often with extensive notes, outlines, and graphs to organise them.
It's a joy for me to see other writers who've clearly distilled their argument. Rare, too. It takes talent, clarity of thought, and organisation.
The school of writing advice that this is just words and you've got to keep them flowing strikes me as quite flawed.
<q>
What if everything was powered by “The Web”, but you never saw a browser?
This is a big question. As an industry would we be happy with the user hardly ever seeing a web browser anymore? Or is that the one thing that is sacrosanct?
I think my original classifications: Notifications, Physical, Embedded and Integrated, were not a million miles off where I think the platform is headed.
</q>
It's a long argument / technical exploration of what a web-served world not mediated by browsers, but through notifications, native apps, embedded systems, etc., would look like. More Web-as-data-back-end than Web-as-content-delivery, in one view that occurs to me.
That said: the article wanders, doesn't start with or come to a point, and is difficult to follow. It's more a thinking-out-loud exploration than clear draft IMO.