The MVP for Gleebeam is done and deployed at https://gleebeam.com. It includes:
I feel it's just as important to mention the things I left out of the MVP:
Integrate payments only if you have a sizeable audience of people eager to start using your product immediately after launch.
It will likely be a waste of time initially as you probably want to first validate your app's prototype and learn about the few users who will want to use it initially without having them pay to make full use of the product.
This was my first time integrating Stripe in an app so I wanted to do it to learn the API. It took quite a bit of time to handle all free/paid tier upgrade/downgrade scenarios.
Don't build too much specific functionality before you know what users expect from the product.
The part of Gleebeam that was most difficult to build was the notification editor. Now having spent more time thinking about it, I'm pretty sure the app doesn't need an editor with so much flexibility - it only adds to the set-up overhead users experience when they start to use the app.
Lots of technical stuff.
I am a self-taught developer and am constantly learning incredible amounts of things. Some noteworthy examples for what I learned with this project: Firebase Cloud Functions, Firestore Database (I had previously used their Real-time Database solution), Firebase Hosting, tests with Jest, multi-page apps with Vue CLI, Stripe API, and the list could go on.
Learning this is not essential for making Gleebeam a sustainable business but I just really enjoy expanding my tech skills with my projects and would never willingly stop doing this just to save time. That said, I don't think I reinvent the wheel too often - the goal is just to push my current limits and not to learn how EVERYTHING works.