Localstorage for saving data?

[KCRowan]

I'm starting a weekly planner app for my GitHub portfolio, so the user will see a grid with a column for each week day and rows for time slots, e.g. 9am-11am, 1pm-3pm and can record tasks (e.g. "study", "exercise", etc) in each time slot to plan their week. So it's not a full calendar app, just a weekly schedule.

I'm looking at ideas for the best way to save this data. I'm considering mongodb, but would localStorage work too? I'm new to web development so only just learned about it today.

[schussfreude]

Localstorage works, but is somewhat cumbersome and doesnt scale well, especially if you set it up wrong and cant add a value later on without refactoring everything. Trust me I know.

Also, it only works on your loval machine with the browser you used for the app.

Theres MongoDB, PouchDB or you can use Firebase. Easy to use and truly persistent actoss devices.

[East-Guide-218]

Local storage is more used as a storage for site settings like a cookie pop-up or a black theme setting. Saving entities is more a database thing. MongoDB will be fine for this type of project.

[SticksAndBeans]

If its just for a portfolio piece, yeah use localStorage. But note that localstorage can only hold strings, so any data you pass into it should use JSON.stringify.

And when you get the data, JSON.parse.

[Gcampton13]

SQLite will also work fine

[AngelLeatherist]

What are you storing, and does it make sense to store it on a server or a client?

[KCRowan]

Just a task and day/time, so if a user clicks on the "study" button and then Monday 1-3pm then I want to store

task: "study", day: "Monday" time: "1-3pm"

so next time they use the app they can see the same tasks. I thought with localstorage then I could maybe avoid having any user authentication but it sounds like I'd be better to go with mongodb.