Quadrant Chart

Quadrant Chart

This chart shows each technology’s satisfaction ratio over its total usage.

Additionally, technologies that have an interest ratio (percentage of non-users interested in learning it) over 50% are displayed as “on fire”.

AssessAvoidAdoptAnalyze82%RdRedux94%GqGraphQL46%RyRelay/Relay Modern93%ApApollo78%MxMobX0.02.0k4.0k6.0k8.0k10k12k0%10%20%30%40%50%60%70%80%90%100%Satisfaction %Users
Assess: Low usage, high satisfaction. Technologies worth keeping an eye on.
Adopt: High usage, high satisfaction. Safe technologies to adopt.
Avoid: Low usage, low satisfaction. Technologies probably best avoided currently.
Analyze: High usage, low satisfaction. Reassess these technologies if you're currently using them.


In the good old days, things were simple. Your data lived in your database, where the server could fetch it, plop it into a template, and send the whole thing down to the client.

But things are not so simple anymore. Today, apps need to know how to fetch data themselves in order to render their own templates and components. This has given rise to a whole range of data fetching and data management tools.

Redux is without a doubt the most widespread of these tools, and its 82% satisfaction rate is a testament to how well-regarded it has become.

But the whole space might soon get shaken up by the GraphQL shockwave. GraphQL users went from 5% to 20% in two years, and their client of choice seems to be Apollo. Add to this the fact that the latest version of Apollo makes using Redux optional, and it wouldn't be surprising if next year's results start to look very different…