This mirrors the "richness only when the user can handle it" approach Google Search employs. JS is a privilege -- not a right or requirement -- in high performing teams
-
-
Show this thread
-
In these sorts of services, having multiple versions to reach all users with the best experience is *just the cost of doing business*. If your team can't afford this, focus on lowest-tier device/network. Scaling up is effort, but scaling down *simply doesn't work*
Show this thread -
In darker moments I wonder how much of computing's future has been lost to native because naive managers and engineers thought "responsive" meant they could stuff their desktop JS into mobile sausage casings.
Show this thread
End of conversation
New conversation -
-
-
Same applies to lit-element, built in Google and for Google needs
- 9 more replies
New conversation -
-
-
And at some point, give up and switch to inferno...
-
I thought the newest mobile web version was real React, but they *did* hire
@trueadm (good get!)
End of conversation
New conversation -
-
-
It's worth noting that Facebook web experience on mobile is absolutely, absolutely terrible. Slow, buggy and ugly. Even on high-end devices. Keep this in mind when using their tools :P
- 3 more replies
New conversation -
-
-
I get the point (I think) but I'm not sure this applies outside developed economies. Personally haven't seen a phone that truly struggles with React. Maybe it's the apps I write, basically just forms and lists, but then isn't that most apps.
Thanks. 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.