After grad school, I've spent a year making a music web app with 3 friends (I was fortunate to have family was funding me). I'm now doing the opposite of you as I've just signed my first job post graduation. But Here's my 2 cent anyway:
I'm just a young graduate, but so far what I consider the 2 most important things in starting a business are to surround yourself with the right people, and be able to manage them.
About your project, you can do a market study to buy time. If it's a service, then maybe you don't need much more than a landing page for now. Maybe you can fake the product you're selling if it's a desktop app, and only show videos on your landing page (I think that's what dropbox initially did). this allows you to study the market before/during coding and/or keep your job at the same time.
As a coder, the most useful thing I've had in this team is a UI/UX designer. Because without him, I'd lose hours trying to find the right spacing/sizing/centring for all my divs. More over, always make sure that you understand a wireframe before coding. And most importantly, make sure you have a wireframe before coding. Because maintaining your html/react/sass will quickly be time consuming if you change your UI often. Especially if the app's responsive.
Don't worry about the stack, use what you know. It looks like you're in a rush to make money since you're quitting your job. Don't learn the latest JS/Python Foo if you're already efficient in Bar. If you already know react and redux, structure your code such that you can reuse as much code as possible when porting to ios/android using react native.
Funny anecdote of how we lost many days trying to figure out why our bounce rate was so huge. We realised that users thought that our buttons were textboxes and wouldn't click on them. Once we realised that, we simplified the landing page so a user HAD to know that these textbox looking objects were buttons because the only thing to do on the page was click on them. Subconsciously, the users now knew what a button looked like on the app. So yes, sometimes you will waste days on things because you're not looking at the right place (in our case we imaged all source of problems possible, but not that users didn't know what a button on our website looked like). Try as much as possible to stay open minded, because things will be obvious to you but not your users. Working on projects alone can make this hard to remember.
I guess what i'm trying to communicate is the obvious: don't lose any time unnecessary time. Always plan ahead. Don't under estimate the amount of work there is to do. Be able to delegate the right task to the right people at the right time while supervising that everything goes on smoothly. Remember the product is designed for users that have never used it.
I'm just a young graduate, but so far what I consider the 2 most important things in starting a business are to surround yourself with the right people, and be able to manage them.
About your project, you can do a market study to buy time. If it's a service, then maybe you don't need much more than a landing page for now. Maybe you can fake the product you're selling if it's a desktop app, and only show videos on your landing page (I think that's what dropbox initially did). this allows you to study the market before/during coding and/or keep your job at the same time.
As a coder, the most useful thing I've had in this team is a UI/UX designer. Because without him, I'd lose hours trying to find the right spacing/sizing/centring for all my divs. More over, always make sure that you understand a wireframe before coding. And most importantly, make sure you have a wireframe before coding. Because maintaining your html/react/sass will quickly be time consuming if you change your UI often. Especially if the app's responsive.
Don't worry about the stack, use what you know. It looks like you're in a rush to make money since you're quitting your job. Don't learn the latest JS/Python Foo if you're already efficient in Bar. If you already know react and redux, structure your code such that you can reuse as much code as possible when porting to ios/android using react native.
Funny anecdote of how we lost many days trying to figure out why our bounce rate was so huge. We realised that users thought that our buttons were textboxes and wouldn't click on them. Once we realised that, we simplified the landing page so a user HAD to know that these textbox looking objects were buttons because the only thing to do on the page was click on them. Subconsciously, the users now knew what a button looked like on the app. So yes, sometimes you will waste days on things because you're not looking at the right place (in our case we imaged all source of problems possible, but not that users didn't know what a button on our website looked like). Try as much as possible to stay open minded, because things will be obvious to you but not your users. Working on projects alone can make this hard to remember.
I guess what i'm trying to communicate is the obvious: don't lose any time unnecessary time. Always plan ahead. Don't under estimate the amount of work there is to do. Be able to delegate the right task to the right people at the right time while supervising that everything goes on smoothly. Remember the product is designed for users that have never used it.