To recap mobile, browsers now supporting Web Components V1: Android WebView, Microsoft Edge for Android, Baidu Browser, Samsung Internet, UC, Opera, Firefox, Safari, and Chrome. If that's not damned-near 100% of your mobile users, you're many sigma out of the norm.
-
-
Show this thread
-
...also, recall that "Android WebView" covers many halfling browsers like the Facebook in-app-whatever-that-thing-is. Also, Apple's WebViews support WC too. Point is, lack of native support is a rounding error.
Show this thread
End of conversation
New conversation -
-
-
still feels like building on sand to me, all the while there's a simple boolean enable/disable Javascript option. But that's viewing them as an approach to adding new elements, not as a way to make webapps...
-
Why does it feel like building on sand any more (or less) than the now-pervasive use of JS frameworks?
- 5 more replies
New conversation -
-
-
Are you saying that developers who are (rightfully) concerned about desktop support are the "past" and developers who live in a mobile only world are the "future"?
- 3 more replies
New conversation -
-
-
hi. I use Edge. -
I do too (for some fraction of the time I'm on Windows, which is some fraction of the time). But Edge for Android supports them and when I'm on desktop using Edge the polyfills work great and aren't super heavy because my desktop devices have 10x the CPU of my mobile devices.
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.