Appwrite doesn't have explicit API versioning.so how can i use Backward Compatibility
#How to use Backward Compatibility
livid carbon
Appwrite doesn't have explicit API versioning.so how can i use Backward Compatib...
The Appwrite SDKs are backwards compatible for 1 version.
So, apps that were using the 1.5 SDK when Appwrite Cloud upgraded to 1.6 still worked.
harsh mirage
The Appwrite SDKs are backwards compatible for 1 version.
So, apps that were us...
in database schema
I’m building a pre-launch Flutter app using Appwrite as the backend and Hive for local storage. I’m adding postIdStr (String) and postIdRel (Relationship, onDelete: cascade) to my Post collection. I’d like to avoid model classes and use Hive with raw maps for flexibility.
What’s the best way to handle adding a new field (e.g., status) in Appwrite so my Flutter app adapts without a Play Store update? I’m considering a cloud function to fetch data and a UI spec, syncing to Hive dynamically. Is this a good approach, or do you recommend something else with Appwrite’s features?