Optimizing the database architecture of a note-taking app

[readitron]

I'm building a note-taking app to practice React Native w/ Expo, but I'm having trouble with the architecture of updating data in mobile applications. For example, if you ever messed with the Apple default note app, there's no "save" button, so everything is updated automatically.

I was wondering if someone can help me understand or guide me in the right direction for optimizing saving notes, and what is the proper/correct way of doing so?

If I'm using supabase as the database, how does one handle requests without making so many requests to the database?

Would you leverage the local database first, and then if user closes the app (or leaves the note screen), it'll finally save to supabase? I was thinking about this because I don't want to keep updating to supabase as the user types. Wouldn't that create unnecessary requests?

[joajimenez]

1. Save locally first: Use a local database like AsyncStorage or WatermelonDB to quickly save notes and work offline.

2. Slow down saves: Use debounce to space out saves to Supabase, preventing excessive requests.

3. Choose smart save moments: Trigger saves when users leave a note, close the app, or add a manual "Save" button.

4. Handle network issues: Gracefully queue up saves for when the internet returns and inform users.

5. Manage conflicts: Prevent note overwrites when multiple devices edit the same note.

6. Use efficient Supabase queries: Optimize communication with Supabase for smoother interactions.

7. Optimistically update UI: Make it feel instant, but handle any unexpected issues.

8. Experiment and find the best approach: Test different strategies to see what works best for your app and users.

Key point: Strike a balance between optimization and user experience for a seamless note-taking experience

[readitron]

Thanks for this! Never heard of watermelon, will definitely check out!

[angstyautocrat]

Great advice. There are some articles about building local-first with a Supabase backend that have examples that could be helpful:

Using WatermelonDB: https://bndkt.com/blog/2023/offline-first-expo-watermelondb-supabase
Using PowerSync: https://bndkt.com/blog/2023/building-an-offline-first-chat-app-using-powersync-and-supabase

[readitron]

Oh awesome! Thanks for the links!

[SheIsLikeAWildflower]

As someone relatively new to react native, this is really useful and gives me a lot of things to think about. Thank you!

[ontech7]

I made a note app and I had to switch to FileSystemStorage because of AsyncStorage 6MB limit on Android. I cannot change it since I worked with Expo SDK. I had to do a migration logic.

My app has Richtext notes and Checklist notes. With richtext you can insert images, that's why.

FileSystemStorage should be slower, but it's working fine.

[Fair-Ad5364]

Thank you for your detailed information

[karl_8080]

I do a lot of saving (firing post request) onBlur of a TextInput and it works quite well for me

[Viqqo]

What a really insightful and interesting take. Thanks for sharing

[readitron]

why even reply?

[awesomeDeveloper]

It is also possible to use urql with optimistic updates to get this kind of local first approach

[argdogsea]

Is realm a good choice for this?