Appwrite backend for flutterflow

anyone here uses appwrite with flutterflow. From my understanding you'd need to use the web sdk or api. Should simply use api calls in flutterflow or the appwrite pubdev https://pub.dev/packages/appwrite to connect the two. What's your experience?

Flutterflow does have a template https://app.flutterflow.io/marketplace/item/maPenbTJa9L1K2hzjaYt but these are way too many end points to connect manually. There has to be a more streamlined way to connect. them. Is there another resource you can point me to or advise

FlutterFlow is flutter...so you can try using the flutter sdk https://pub.dev/packages/appwrite Make sure to use the right version of the SDK with your version of Appwrite.

That said, when I tried FlutterFlow, it was difficult to get the SDK working because re-using the Appwrite Client wasn't possible. so, i manually made the API calls. See https://medium.com/@stnguyen90/connecting-flutterflow-to-appwrite-56abdbcbbd92

these are way too many end points to connect manually

How many do you need? and wouldn't it be copy and paste?

btw, have you voted on Appwrite in the integration wishlist? https://community.flutterflow.io/integration-wishlist

I did vote appwrite today coincidentally. I have your article in my notion actually. Not sure if it was me still couldn't quite get it to work...api integration

I used an instance but now use the cloud version of appwrite

What was the problem?

Apart from getting the integrations to work, mine are multiple. I may post this in the general channel as well for more perspectives but still respond directly here. I'm about to release a events and services platform in the caribbean https://karibevents.com/ which is being built with flutterflow. However with firebase doing away with dynamic linking which we heavily rely on for event promoter and service provider profile pages, and our country service and event listing pages will be dynamically generated so we wouldn't have to build one per country and just dynamically generate the listing data for each.

I'm working solo, it's my platform - i'm strongly thinking of redoing the backend but with appwrite to avoid any future migration pains. Now i'm tasked with learning it with flutterflow as I want to use it for other projects in the pipeline as well.

I saw on a blog post and github page you guys have a dynamic linking solution coming up. Is it ready?

Is there an ETA because I need it like now because I'm planning to launch next week. If we keep using firebase dynamic links, can that be migrated too with your recently released 1 click migration tool for firebase

I'm a bit confused because as of right now not sure what design changes i'd have to make to accomodate how dynamic linking would work in appwrite.

Are you guys building out a fcm alternative as well for notifications? Can I use firebase and still use fcm via cloudfunctions or webhooks.

Does the relationships feature appwrite has work similarly to a document reference in firebase? For authentication can I send a verification email to ensure the addresses are real like I can with firebase.

I've seen the cloud pricing which seems attractive considering reads and writes on firebase, but the feature upgrades aren't quite clear.

Can I have a bit of advice here as to the best way forward.

one advantage of firebase is it's caching abilities, does appwrite have anything similar and can I use appwrite on flutterflow and still deploy for web and mobile (android, IOS) simultaneously like I would with firebase

Also how does chat work with appwrite...do I need third parties for it as it's really cheap in firebase

someone said that " thanks to this latest release you can have exactly the same behaviour as firebase dynamic links thanks to Appwrite functions" - is there documentation or a tutorial on how to do that.

and is that the same thing as the https://github.com/appwrite/dynamic-links

Forgive my ignorance on something. I may have been obverving appwrite for a bit but haven't built any live projects in it yet

I don't want to ask too many questions, however what are the pros of using appwrite cloud rather than self hosting and instance - which i've tried before actually. Do I also get email support?

That's the example

The main benefit is that you don't need to manage anything, handle any potential outage, etc

Email support is currently not available until appwrite Cloud gets out of beta, and only in the paid plan (currently it's 100% free)

not to be impatient or anything, you didn't answer any of my prior questions though

There's not any ETA since it's there

You can't migrate for now those links directly from firebase mainly due to firebase limitations

I've read that subcollections can be put in appwrite as nested documents or another collection connected using the Collections API. if you have many subcollections in a document or the potential to which is better?

Also does the new relationships feature make connecting related collection even easier - thereby enabling the subcollection functionlity - like you would with sql tables

Just don't store things like no-SQL, instead do things like SQL

In my opinion it's easier, but it's just an opinion 😅

I think the best was is having separate collections

And then connecting them manually or through relationships

I see. when would nested documents be best for then?

What do you mean by nested documents?