That, and ability to send push notifications by default, are major drivers amongst the most...um...*growth oriented* players.
-
-
Replying to @slightlylate @robinberjon and
So what is the Chrome team's plan to get those apps back into the browser, as they are on desktop? I strongly suspect, though obviously without the data you have, that they'd make a bigger effect on % of time in browser than most things currently happening under the Fugu banner.
1 reply 0 retweets 0 likes -
Replying to @gsnedders @robinberjon and
"in the browser" may not literally mean "in the browser" -- nobody wants to type a URL on a mobile phone -- hence PWAs. Fugu fills out the general PWA approach for more classes of app. It's all of a piece.
1 reply 0 retweets 0 likes -
Replying to @slightlylate @robinberjon and
PWAs etc. are still "in the browser" for most practical purposes. My problem with what's happening with Fugu, as I said in (much later) tweets in the original thread, is that so many of the classes of apps are unlikely to account for more than a very small % of user time.
1 reply 0 retweets 0 likes -
Replying to @gsnedders @slightlylate and
If you're framing the web crisis as "users spend a small % in browsers" then surely you need to chase after the largest apps which users spend the majority of their time in?
2 replies 0 retweets 0 likes -
Replying to @gsnedders @slightlylate and
I don't think that's a great way to frame this.
2 replies 0 retweets 0 likes -
Replying to @tobie @gsnedders and
Ignoring the whataboutism, there are important questions we should tease out and address head-on: the role of FOMO in developer decision-making and how adjacency-theory explains suppressed use
2 replies 0 retweets 0 likes -
Replying to @slightlylate @tobie and
First, and I can't say this often enough, many Fugu capability requests come *directly* from top app developers.
1 reply 0 retweets 0 likes -
Replying to @slightlylate @tobie and
Pushing past the tactical, developers *frequently* express concern to us that they'll "miss out" on capabilities if they build for the web (vs. native). This is a key driver of short-term decision making in our experience. Folks don't want to be caught flat-footed vs. competition
1 reply 0 retweets 0 likes -
Replying to @slightlylate @tobie and
Historically, you could trust the web *not* to expand it's capability footprint. In the comparative lens, this means it's a dead language. You'll never expect it to keep up and deliver what you need to enable the new experiences you will want to deliver. FOMO suppresses interest
1 reply 0 retweets 0 likes
How do you work against this? A steady string of safe-but-capable expansions that meet clearly-articulated developer needs. And the "steady" part matters. If we pull up the drawbridge at any point and say "no more!", everyone will understand the web can't support them.
-
-
Replying to @slightlylate @tobie and
Now, of course, this is exactly what some vendors have done. Little surprise, then, that tools like Electron have gotten traction in their proverbial backyards.
1 reply 0 retweets 0 likes -
Replying to @slightlylate @tobie and
Every metaplatfrom naturally expands to provide capabilities developers need and that is available on *most* hardware and *most* OSes -- or that metaplatform dies.
2 replies 0 retweets 0 likes - 8 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.