lohanidamodar
commented
2 years ago @hey-nicolasklein As long as the package you choose supports remote REST APIs, Appwrite should work with them. Personally I've not tried any of them to let you know the best approach. From what I see the package you linked seems to be most flexible and configurable. If you find the best approach, we would love for your contributions an article, demo project whatever you would like. Let us know if we can help in any other way.
Silfalion
Sun3
🔖 Feature description
Hey, I'm currently developing an app that has to be offline first. I know that the Firebase offline functionality is a planned feature for appwrite as a whole. But what are some solutions that could be used right now? The discussion over on the appwrite repo is more focused on appwrite as a service providing such functionality. But which options could be recommended for flutter?
In my research I found some possible solutions. From using the local Shared Preference Storage, to persisting blocs with Bloc Hydrated, to complete solutions like this package over on pub.
Do you have any advice on which way to go? What would be a good architecture wrapping the appwrite sdk to implement offline storage?
🎤 Pitch
I guess my pitch is to implement offline functionality in the flutter appwrite sdk someday. Probably, when appwrite as a whole implements such a feature. But in the meantime here could be a place to promote solutions which work with appwrite until there is an official support.
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?