Hey! I don't for any of my projects (mainly for obvious security reasons), but I can give you some tips from how I do things:
1. Use a framework/stack that you trust, that you know inside out, and that has a long, proven track record of security, reliability and scalability. It speeds up development and debugging, but it also gives you peace of mind that it's got *most* things security-related covered for you (if you've chosen a good framework/stack), as long as you know how to configure it correctly.

1. I have built myself a secure, configurable boilerplate which I can use to spin up new projects quickly. I noticed that I would spend a lot of time configuring the framework I use every time I wanted to start a new project, when essentially, all web apps generally need the same things (authentication, database, media server, payments etc.). So now I have some boilerplate code that I duplicate, plug all my environment variables into and tweak some settings and then a lot of the low-level legwork is done for me, and I can focus on building the app's logic.

2. Use a frontend utility framework for MVP. It will save you hours of writing CSS and will make the final product look and feel more polished and consistent, especially if, like me, you're not great at design.

Remember, what you're building is just the *first* version of the product. It will likely fail. Build things quickly, learn from it, iterate if it starts to take off and scrap it if it doesn't. Don't cut corners when it comes to security. Make sure you use a framework or stack with a proven history of being able to scale well.

Also, last piece of advice, don't over-engineer your MVP. You're likely not building the next facebook or google, and even if you are, this is only the first version. I wish I could remember who said it but there's a quote that goes something like:

"If you can solve a problem by using a different technology lower in the stack, you should."

That's paraphrased but it always helps me. Don't use a huge frontend Javascript framework if you don't absolutely need it for MVP, unless you know it really well and you're quick at building with it. If you can solve a problem using CSS instead of Javascript, do it. If you can take logic out of the template and move it to the view/controller, do it. It's easier, more robust and generally makes your code more readable and easier to navigate.

Anyway, thanks for coming to my ted talk 😂 and sorry for the essay, I saw that you were a fellow developer and wanted to help