Ask HN: Is it practical to start a 1-person Micro ISV these days?
[1] http://sidekiq.org/products/pro [2] http://www.perfecttableplan.com/
[1] http://sidekiq.org/products/pro [2] http://www.perfecttableplan.com/
I spent 15 years working at various startups and earned little more than a typical dev salary in the end. Today I'm making several times my previous salary so the business has been a big success for me.
As for visibility, I'm happy owning my own little niche of Ruby background jobs. I don't advertise or market much, just provide the best product I can, support it every day and developer word of mouth does the rest.
Edit: fix grammar
http://micheleincalifornia.blogspot.com/2015/10/bicycles-on-...
This list is not just software vendors. Some are webcomic artists. I was interested in any really tiny web operation actually making enough money to support the people running it.
I suspect the lack of response is partly due to low visibility and/or a desire to lie low. Small shops that don't want to grow into big corporations do not necessarily want excessive attention and also may not be well known enough (as a Micro ISV specifically) for other people to confidently say "Yup, this qualifies." A small shop doesn't need tons of traffic and money to support the few people working on it and may view excessive exposure as a bug, not a feature.
In the last couple of weeks I've been finally building my product as a web application mainly because of these factors: currently I have more experience on web development that desktop development; I use a lot of SVGs and tables and they are easier to do on HTML; I have my source code in Python and C and it is a pain to distribute Python; cross-platform desktop development tools are not great nowadays (Qt is the only serious option and it sucks); I would have to distribute lots of libraries with my application.
The way I see things now is, if you really want to test the market for something and you can use a web app, do it. It is easier for you to control the updates, iterate faster to improve your idea, and have better discoverability. It is less painful for a prospective client to click on your URL than thinking on downloading and installing your application. The funnel for web applications is smaller than for desktop apps [1], and that is really important when you want to test your application.
Later in the game, after you have a stable idea and enough loyal clients, you can always move to the desktop or mobile if that's the case. This is what is happening with all major SaaS nowadays, they start on the web and eventually go to the desktop when they reach some maturity (Evernote, Slack, etc...)
[1] http://www.kalzumeus.com/2009/09/05/desktop-aps-versus-web-a...
I empathize with what you are going through.
> The way I see things now is, if you really want to test the market for something and you can use a web app, do it. It is easier for you to control the updates, iterate faster to improve your idea, and have better discoverability. It is less painful for a prospective client to click on your URL than thinking on downloading and installing your application. The funnel for web applications is smaller than for desktop apps [1], and that is really important when you want to test your application.
Perhaps you are right. I do wonder, though, if there is a place for a desktop offering. Balsamiq Mockups [1] started as a desktop app, if I remember correctly. The plus to an installed app (especially if it is a single executable along the lines of Go, Rust, Swift, etc.) is the customer data can stay with the customer, performance can be quite good without the need to scale the backend, operations can be simpler, among others. (Many of the downsides are already addressed in patio11's article you referenced.)
Absolutely right. This is also my experience.
http://www.joelonsoftware.com/articles/Micro-ISV.html
http://www.microisv.com/ (defunct)
http://www.singlefounder.com/the-day-the-microisv-movement-d...
I think those of us looking to start something really want certainty that whatever thing we're thinking of building will be successful. I think it can be, but it takes more grunt work selecting the right thing to build.
To answer your question, yes. Go do it then come back and tell us how it go. And good luck.
The vast majority of successful 1-person businesses are run by non-technical people and are more content-driven then software driven.
I don't think so. I've launched a few 1-person SaaS companies in the past, and some were popular (but not profitable). I've settled on earning a salary and investing as much of that salary as possible.
I still get the urge to build stuff, and I still do, but I now look at it as a hobby.