I thought that would be the case but in people I've spoken to it's not been a driver.
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
-
-
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
-
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.
- 10 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.