Clarify Riverpod's Focus in Tagline

[stephane-archer]

The current tagline, "Riverpod: A Reactive Caching and Data-binding Framework," feels professional but doesn't convey Riverpod's primary use case: state management. While Riverpod is versatile, most users see it first as a state management tool.

Proposed alternatives:

• "Riverpod: Reliable State Management and Beyond"
• "Riverpod: Smarter State Management for Modern Apps"
• "Riverpod: The All-in-One State Management Solution"

These taglines emphasize state management while hinting at its broader capabilities.
Any thoughts on this?

[rrousselGit]

This is very much intended. I want to dissociate Riverpod from the keyword "State management".

"State management" in the ecosystem is often read as "Observable class + Builder widget", with lots of imperative logic.
Claiming Riverpod's main goal is "State-management" misleads users into trying to use it like any other packages from that category. It therefore causes users to misuse Riverpod and not use it to its full potential.

I don't find the tagline perfect, but I clearly want something more tailored to Riverpod than what you proposed.

[rrousselGit]

Riverpod has two core goals:

• Make it dead easy to deal with any async logic. To the point where I had (and still am) considering making shipping a custom HTTP client in Riverpod.
• Enabling writing code in a widget-like way thanks to ref.watch() for simplicity and composition

Those are fairly specific goals, and "State-management" doesn't communicate either of those.

[stephane-archer]

@rrousselGit in that case, I think you should emphasize why Riverpod is not like any other "State management" and demonstrate those two points.
From an outsider, coming from Provider, I don't understand yet what "A Reactive Caching and Data-binding Framework" actually means. the current tagline is quite intimidating and opaque for new commer

[rrousselGit]

The rest of the page is supposed to do that. And pages like https://riverpod.dev/docs/introduction/why_riverpod

It's not something that can be explained in a one-liner

[rrousselGit]

I agree that we can probably do better, so I'll leave this open.

[stephane-archer]

@rrousselGit

• Riverpod: Effortless Async Logic and Seamless Composition
• Riverpod: Simplifying Async and Reactive Programming
• Riverpod: Async Made Simple, Composition Made Elegant

are some taglines that would emphasize your two core goals and feel more accessible to outsiders in my opinion.

I hope my feedback helps you make it more accessible to others

[rrousselGit]

• https://bsky.app/profile/remirousselet.bsky.social/post/3lcvgbuiuts22
• https://www.linkedin.com/posts/r%C3%A9mi-rousselet_what-do-you-think-would-be-a-good-tagline-activity-7271963903276863489-ymOJ?utm_source=share&utm_medium=member_desktop
• https://x.com/remi_rousselet/status/1866198107702133012

We'll see what people suggest

[stephane-archer]

@rrousselGit I think you have some great suggestions but if you have to ask for no reference to "state management" explicitly, It means something.
For most people, Riverpod is the Provider package on steroids. it's a state management tool with more to offer. It might sound too simplistic from your point of view but "a state management tool with more to offer" is a good tagline and most suggestions will probably go in that direction if you don't put constraints.

I hope you find a tagline that you love, but I suggest you listen to your users even if you think most of them don't grasp the entire scope of your package