Back

Can't get your todo demo app to work (Flutter)

  • 0
  • Flutter
  • Web
Timmer
3 Oct, 2024, 18:01

Hi. New to AppWrite, looking to replace Firebase in app.

Got past the "appwrite login" bug where you add the --endpoint flag and got it to work.

Next: Trying to get your Todo app to work - https://github.com/appwrite/demo-todo-with-flutter

I was unable to get it to work, here is what I ran into. When/if you can resolve these issues (or help me if I screened up) i'll restart my Appwrite eval.

Step 3 says "appwrite deploy collections". When you try that, the CLI says use 'appwrite push' instead which is fine but I'm not sure what the next steps are from there and also it seems like this step is somehow out of order because at this point I don't have any Appwrite code/folder on my computer - that doesn't happen until the following step as described in the README.

Later on in the readme, under "run locally" it says "Make lib/constant.dart using lib/constants.dart.example as a template." It wasn't clear to me what needs to get done here. Do I need to create a DB in the web portal first? Create a collection first?

Bottom line: If you could give me explicit steps for a noob to get the demo todo app to work on flutter, I should be off to the races and think it would help other people too if you can update the README accordingly to indicate precise steps to get it to work on the CLI and also what (if any) steps need to happen in your web console.

Thanks Tim PS - In case you track use cases: Flutter PWA offline-first web app, ideally safari compatible, where you can control what is cached (forced saved) locally on the device. I will be coming from Firebase which is soooo close but you can't launch a firebase based web app offline on safari (you can on chrome) and on all browsers you can't force save/cached items on the device - in other words, you have no control over what is cached from firebase on the device and what is not.

TL;DR
Developers are having issues getting the demo todo app to work in Flutter with AppWrite. The steps in the README are confusing and out of order. Explicit instructions are needed, including what needs to be done in the web console. The desire is to create an offline-first web app that works on Safari and allows control over cached items. Solution: Update the README with precise steps to deploy the app using the CLI and web console. Clearly outline the process of creating a DB and collection before running the demo todo app.
Reply

Reply to this thread by joining our Discord

Reply on Discord

Need support?

Join our Discord

Get community support by joining our Discord server.

Join Discord

Get premium support

Join Appwrite Pro and get email support from our team.

Learn more