The use case is limited, a project has it's own backend, why need to add a new sub-system for tiny data storage?
To add something new, that needs to persist, will not require going to a backend team and begging for a new API from them.
A common difficulty is the simplest scenario, where do I store this frontend user preference? How do I store this that prevents nagging multiple times across devices?
Backend teams will argue this is a frontend piece of data, and they provide APIs and backend storage that is agnostic of a specific frontend.
This feels like a valuable addition.