An abridged list of requirements to use React the way FB does for mobile web: - staff dedicated performance team - set hard perf targets that no CL can violate (enforced by CI) - have a separate "mbasic" version of the service and send users to it that can't handle heavy JShttps://twitter.com/mikeal/status/1159165205428879360 …
-
-
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 -
-
-
I hesitate to ask, but is this done with browser sniffing? *shudder*
-
Sometimes, but often (in the modern era) ML classifiers that look at things like device/vendor, RTT, network segment, etc. and train up on user choice to go to the other variant.
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.