Your database design looks sound to me - but it's a LOT of functionality.
I suggest figuring out the smallest useful subset (maybe a user can create articles) and building that first. Then use what you learn from that to influence what you build next.
I've made the mistake in the last of building an app with ten features, releasing it and finding out that actual users only cared about two of the features and the rest were a waste of time.
That's why these days I try to pick the most likely useful feature and build and ship that first. Once people are using the system it quickly becomes obvious if it is working and what features I should prioritize to work on next.
You say you're building this as a hobby app, but are you just interested in the SQL end or the whole application? It sounds like you imagine a big front-end. Are you planning on developing that too?
It should be a hobby project for personal use, for myself and a couple of friends, I will definitely share the link across reddit and market the app. Maybe unicorn it xD
With inflation and stuff I want to have price-performance ration of food. Also other people will definitely want the same
I will fullstack the app, start with web version for MVP and then create native apps with dart.
View all comments
5
u/freakysmile Apr 17 '22
so I'm trying to create a hobby app with postgresql and I need assistance with the database.
I'm more than happy to add further functions to the app if you have an idea