I'm a Software Engineer based in Dublin. I love crafting software and experimenting with languages and technologies. I'm a #DevOps advocate and continuous improvement pursuer.
It's not clear from your post if you've launched it already or not.
You have already recognized a few issues.
If you think the database structure is bad it's probably because you're evaluating it in terms of the way you think your webapp is going to evolve. I wouldn't stress too much about it but rather I would prioritise understanding if your user-base is gaining value from your app as well as validating if your assumptions are correct. Sometimes you find that your users are going to need something different from what you had already imagined and that probably means a database structure you hadn't thought of.
Regarding insecure APIs I would prioritise the privacy and security of your users. So if you acknowledge that insecure API might harm your users I'd definitely prioritise addressing that.
It's not clear from your post if you've launched it already or not.
You have already recognized a few issues.
If you think the database structure is bad it's probably because you're evaluating it in terms of the way you think your webapp is going to evolve. I wouldn't stress too much about it but rather I would prioritise understanding if your user-base is gaining value from your app as well as validating if your assumptions are correct. Sometimes you find that your users are going to need something different from what you had already imagined and that probably means a database structure you hadn't thought of.
Regarding insecure APIs I would prioritise the privacy and security of your users. So if you acknowledge that insecure API might harm your users I'd definitely prioritise addressing that.
I indeed meant both ways -- I have old one I don't want to maintain anymore, and I want to create a new one.
However, there will be a user system, so privacy and security come first.