search

kamilgadek / to_do_list_kamilg

1 stars 0 forks source link

GENERAL: Where to store tasks #23

Closed mszakacz closed 2 months ago

mszakacz commented 2 months ago

@kamilgadek Let's use this issue to discuss where we wanna store out data. Options: 1) Firebase 2) Device storage 3) Other DB + API (free API)

Based on the selection we will design a architecture.

Give me your opinion on every option, try to think about benefits and disadvantages of each approach.

mszakacz commented 2 months ago

@kamilgadek any update on this?

kamilgadek commented 2 months ago

Firebase is a great option if we need cross-device syncing, real-time collaboration, or authentication features (e.g., multi-device access). It is more scalable and can grow with our app, but it might be overkill and costly for a very simple to-do app.

Local Storage (Device Storage) is the simplest and fastest to implement for basic offline-first to-do app where users don’t need to access data across devices or share it with others.

API + DB is flexible and gives me control, but it requires backend management. This is a good option if we need more customization and have the capacity to manage a backend, or if we want to experiment with free services like Supabase.

For a simple to-do app, I would recommend starting with local storage (using something like Hive or SQLite) since it covers most basic needs (offline, simple data handling). If we decide to add more advanced features later (like syncing across devices or real-time collaboration), we could migrate to Firebase or build your own backend with an API.

mszakacz commented 2 months ago

@kamilgadek Nice research. For this app let's go with Local Storage.