> I'm planning to release at least one app or website per month in 2019
If this exercise is strictly to learn and expand your skillset, great!
But if you're actually trying to build something of value, no need to put an artificial time limit of a month. #1 might be decent business. Spend the time required to properly validate if there's demand for the project and build it for real, don't half ass it.
I've done a startup before, built in 2 weeks. It crashed 4 times a day, customer service response was about 4 days early on. People are willing to wait when it's an important enough problem.
But it's very hard to tell which will succeed and which wouldn't. I've been building "properly" the last 3 years and nothing came out of it.
The artificial time limit is there to force myself to focus on what really matters, prevent scope creep. E.g. the big problem with #1 is that people wanted scheduling, but I'm not entirely sure it's necessary so early on. It might just work as a matchmaking site.
If this exercise is strictly to learn and expand your skillset, great!
But if you're actually trying to build something of value, no need to put an artificial time limit of a month. #1 might be decent business. Spend the time required to properly validate if there's demand for the project and build it for real, don't half ass it.