Lack of documentation and working example code on pub is an issue

Nobody has claimed this yet.

I was intrigued by the prospect of a repo library. However, looking through pub pages and the Github repo I found the lack of a few examples, and documentation to be very limiting. It's not that developers can't spend time reading and grokking your code, but who has time to dig that deep when trying to decide if a library is worth using. I suspect your library gets passed over because of this lack of information. Also, if it doesn't already, the library should be able to handle gathering data from two sources easily. Anything above your library shouldn't need to know if the data came from a cache or an API call. The repo should handle this. I think your library would be much more popular if you documented it with good documentation and provided multiple code samples so devs can see how to use it and how it would be helpful without taking the time to dig into the details of how it works. I hope this helps and gives you a little motivation to continue developing this and other Flutter libraries.

Review the pub page and GitHub repository first to identify the library's current usage and data-source behavior. Define which documentation, working examples, and cache/API abstraction are actually needed, then consider the issue complete when newcomers can understand the library's value and follow examples without reading its implementation.

Written by the indexing model from the issue text.