## Tech - [PowerSync](https://www.powersync.com/) - Works with supabase - Host SQL locally - [[React Query]] offlineFirst - AsyncStorage how much support do we need for offline first?i was reading through reddit and saw people weren't the biggest fan of asyncstorage - apparently we need to update android max file storage size because right now its 6mb [https://stackoverflow.com/questions/32875726/how-large-is-asyncstorage-in-react-native](https://stackoverflow.com/questions/32875726/how-large-is-asyncstorage-in-react-native)[https://www.reddit.com/r/reactnative/comments/1djd7ws/when_to_use_asyncstorage_vs_react_native_sqlite/#:~:text=I'd%20recommend%20SQLite%20as,be%20between%20SQLite%20and%20MMKV](https://www.reddit.com/r/reactnative/comments/1djd7ws/when_to_use_asyncstorage_vs_react_native_sqlite/#:~:text=I'd%20recommend%20SQLite%20as,be%20between%20SQLite%20and%20MMKV) some other points they made: - slower load time - can work better with the SQL connection with supabase The only concern I have with this is with non-offline compatible processes like text generation and transcription - we can't just send an offline request and just give an optimistic update because we don't have the new values to update the ui with and when i was testing offline optimistic updates when using auto save with react query it didn't seem to throw errors or load for a long time, so i think it's sufficient enough. the only thing would be fixing that max file upload and making sure it's not an issue for other apps as well.an alternative would be something like powersync to host a local mini SQL on the client side for caching data, which we can then use as the persistent storage instead of whatever async storage is. it seems to have integration with supabase and tanstack query via [https://www.npmjs.com/package/@powersync/tanstack-react-query](https://www.npmjs.com/package/@powersync/tanstack-react-query) but it's in alpha and i don't think ti's necessary atm.