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
A further (key) subtelty: most metaplatforms are happy to optimise for the short-term. They tend to build direct pass-throughs to underlying native systems in order to quickly gain market share (see also: Cordova, Electron, etc.). These incidentally tie developers to OSes.
-
-
That is, they become instantly FOMO-free for the low, low cost of selling platform optionality that doesn't materialize in practice.
-
The web has taken a different path. We fully abstract (to the greatest extent possible) underlying OSes and platforms. It's why we *do* standards at all.
End of conversation
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.