Been thinking about the performance concerns around React apps. I acknowledge there are a lot of poor-performing React apps out there. But wonder: Are the challenges technical or organizational?https://twitter.com/slightlylate/status/1015279791371476992 …
-
Show this thread
-
For projects that resulted in apps w/ performance issues, was performance prioritized? Were there stated goals around performance? Was developer experience prioritized above user experience? Regardless of tools, performance doesn't happen by accident.
1 reply 0 retweets 0 likesShow this thread -
The same goes for accessibility: React doesn't make it harder than any competing tools to implement accessible experiences. But accessibility only ends up being done well when it's a priority and teams building apps are accountable for hitting specific goals.
1 reply 0 retweets 1 likeShow this thread -
If we had a time machine and replaced React in some of these projects with Vue, or Preact, or whatever... would the results be much different? Is React the reason some apps are slow? Or are teams deprioritizing performance and just happen to use React because it's popular?
4 replies 0 retweets 3 likesShow this thread -
It'd be fascinating to get in to some organizations and be a part of post mortems to figure out where things went wrong: before the first line of code was written? Or after the teams decided to build their apps around React?
1 reply 0 retweets 0 likesShow this thread -
We're still pretty happy with our decision to use React. Could we use less JavaScript? Sure. Does the app meet our business and user's needs? I think so. Is our PWA fast? Faster than what it replaced. So I'm still unconvinced that React is entirely to blame here.
2 replies 0 retweets 1 likeShow this thread -
Replying to @davidbrunelle
What automation do you have in place to prevent regressions and measure median and 95th% user experience? Or is "faster" annecdotal and historical?
1 reply 0 retweets 0 likes -
Replying to @slightlylate
Still working on automation that will fail builds if there are performance regressions. But "faster" in this case is based off of data collected and analyzed with
@newrelic. To be fair: we had a low bar to measure improvement against.2 replies 0 retweets 0 likes -
Replying to @davidbrunelle @newrelic
So "no" and "low bar". Better than most, but can we agree that teams that pick up these sharp implements must do so with care and support that's largely missing?
3 replies 0 retweets 0 likes -
Performance was one of the MAJOR selling points I used to get us on React. I re-wrote one of our heaviest Knockout modules in React. Render time and memory usage both improved massively. 1/3 memory, and 1/4 time to render, iirc.
1 reply 0 retweets 0 likes
Adam, you target desktop in relatively controlled environments. That's not today's big challenge.
-
-
Absolutely not true. We have desktop oriented modules (billing, claims management, etc). And we have modules designed explicitly for mobile / tablets (those are more domain specific and harder to describe). In either case, React *improved* perf by every measure.
1 reply 0 retweets 0 likes -
This begs more questions than it answers.
1 reply 0 retweets 1 like - 3 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.