pleasedo
-
-
Replying to @jalbertbowdenii @rem
Co-incident to our efforts on Web Components, another team inside of Chrome was developing "Chrome Apps"; I argued against them at the time.
1 reply 1 retweet 7 likes -
...but argument that a more capable platform was needed wasn't wrong. Question was "how". Many platform folks (incl me) busy w/ WC/ES6.
1 reply 0 retweets 4 likes -
In 2012 I moved to London for personal reasons and had to stop co-leading the Web Components/ES6 efforts because time-zones wouldn't work.
1 reply 1 retweet 4 likes -
Chrome Apps v1 and v2 happened between 2010 and 2013. Meanwhile, AppCache had been deployed broadly and was not received well.
1 reply 0 retweets 4 likes -
So developer choices were: - standard thing that wasn't "first class" and didn't work well - proprietary thing w/ limited reach
1 reply 0 retweets 4 likes -
The major difference between them wasn't the proprietary/open split, tho, it was "on the web" vs. "app store model".
1 reply 1 retweet 6 likes -
This seems counter-intuitive, but the difference is a chasm; not small. Defines all other choices in the solution space.
1 reply 0 retweets 6 likes -
So lets say you're me circa 2012: you want a way to address the first-class-apps problem but aren't in a position to do so organisationally
1 reply 0 retweets 5 likes -
...what to do? Well, in my case was lucky: the effort that didn't involve new UI (the hard part) was to fix the offline story; needed doing.
1 reply 0 retweets 4 likes
Jake had been making the case that AppCache was broken and others agreed. Andrew Betts hosted a meeting to discuss:https://labs.ft.com/2012/08/fixing-app-cache/?mhq5j=e1 …
-
-
We worked to build a solution that would "stick" with folks at Mozilla and elsewhere. Promises ("Futures") became part of the effort.
1 reply 0 retweets 4 likes -
Fast forward to late 2013: Service Workers moving forward in Chrome and future of Chrome Apps hazy. I write a "micro-manifest manifesto" doc
1 reply 0 retweets 4 likes - 22 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.