re: Vine, I'm really sad about it for the inside-baseball reasons. 1.) growth and native are hard to square; see: http://startupljackson.com/post/83244692828/html-first …
-
-
Replying to @slightlylate
3.) we didn't get there in time to help them. The web platform hasn't evolved fast enough to them out.
1 reply 0 retweets 5 likes -
Replying to @slightlylate
(my team is working on that; you should be able to make a web page in Chrome that "does Vine" in early 2017)
1 reply 1 retweet 7 likes -
Replying to @slightlylate
4.) the history of Twitter was bootstrapping on _existing_ distribution mechanisms; scrappy communication. Vine forgot that.
1 reply 0 retweets 3 likes -
Replying to @slightlylate
5.) while we're contemplating Apple, spare a thought for WebRTC and Media Session APIs in Safari (no, they aren't there, why do you ask?)
3 replies 1 retweet 6 likes -
Replying to @slightlylate
6.) the biggest story never told about browsers so far has been the impact of the auto-playing video debate. Impacts what's possibly here.
1 reply 0 retweets 4 likes -
Replying to @slightlylate
We finally reversed course (at the same time Apple did):https://blog.chromium.org/2016/08/chrome-53-beta-shadow-dom.html …
2 replies 0 retweets 4 likes
7.) 2017 is going to be a good year for media on the web. Too bad Vine was early and we were late. The next Vine will have it easier.
-
-
Replying to @slightlylate
...if only the folks building it get the memo. /fin
0 replies 0 retweets 3 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.