-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wendy v1.0 #59
Comments
6 tasks
When will 1.0 be released? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Wendy began over 3 years ago. I created it to add offline support for an app that I was building at the time for an app I was building. Since then, the project has matured with improvements here and there as I add it to more and more production apps of mine.
Wendy has been very experimental for years. The more that I used it, the more that I learned about how to build offline apps.
The day has finally arrived. Wendy is ready to become stable. It's ready for it's next major upgrade.
Tasks planned for Wendy v1.0
This task also means No more
taskId
returned when you add a pending task to Wendy. To use Wendy, the developer should not need to be responsible for managing an ID returned from Wendy. Using Wendy's querying system, you should be able to find a pending task anytime in the future if you need it.This also means we probably need to add a cache to make Wendy faster. This is optional, but an idea of mine. Having an in-memory cache will improve speed but it may be so minimal it's not worth it.
Improved testing while using Wendy. The pending task API today is not very testable. Dependency injection is not good. This can be improved. Maybe we even remove pending tasks altogether and come up with a different way. ViewModel <--> Repository models are great ways to write code today. Leverage Repositories to do the work for Wendy.
Deploy Wendy to Maven Central. About time! No more JitPack as the place to get the production build.
Separate the features of Wendy that are useful to Android UI and features that are purely business logic. This allows projects that are not UI projects (like libraries) can successfully use this project.
Not as many defaults, be more flexible There are some default behaviors that Wendy performs. The power should be in the developers hands. For example, when you add a pending task to the queue in Wendy today, the queue runs immediately. This should be changed because the developer knows when they want the queue to run. Let them decide.
Be modern with coroutines
I'm excited. I am not sure when this will be complete so stay tuned. I am also making big, stable changes to my other library to help build offline capable apps, [Teller]levibostian/Teller-Android#74).
The text was updated successfully, but these errors were encountered: