| I have a similar experience.. The thing is that although many of us can work on one or other part of a complete product, it is pretty hard to focus on everything at the same time and build an entire product alone! For me, I have identified my problem not as fear of failure but perfectionism. So I start questioning all little things and things move very slow. I am currently building a SaaS app, and I've built others before but none made me any money so far. But lately I've been tuning my strategy to make things work faster, and have been seeing some success on it. Some of my main points are: * start with something very simple that has the minimum functionality, like drawing a chart if the app is to draw charts, etc. * since I'm working full time on this, decide to implement a feature per day (until you have enough features for now). * THIS ONE IS REALLY IMPORTANT: never leave an inconsistent and non-working application between two commits. Make sure that the version on your repo is always fully working even if it lacks features (it may not be between two commits, I hope you get the idea..). * ANOTHER IMPORTANT ONE: when you have a stable app, do a release to your server, even if you have it mounted on a personal url. It will give you the feeling of being moving forward.. * When you have something usable enough for other users, invite them to use it. Non-technical people feel flatered if you invite them personally to test your application.
- Use a repo such as github (or gitlab for private projects). Commiting the code to those repositories will give you the feeling of moving forward every day. And if your local copy does not work anymore, you can always reset to the latest working commit.. I've been working on this project for much more time than I ever wanted (5+ years) and the points above have been what I learned from it. |