3 ms·
There's a big difference going from a demoable app to production-ready software. So much so, that it's exceptionally rare for a single individual to do both.
by grinich 13y ago
There's a big difference going from a demoable app to production-ready software.
So much so, that it's exceptionally rare for a single individual to do both.
The worst managers don't see this, and mistake a well-made prototype for a finished app.
But as Elon Musk has said, "The first step is to establish that something is possible; then probability will occur."
:)
- seltzered_ 13y agoThis. it's really hard to ship, it's even harder to ensure all the marketing/support/commerce stuff you really don't want to do as an interaction developer is also running. Personal case examples: 1) Recently announced a plugin mentioned by some top designers - basically brings some new interaction ideas to graphic design tools. It's taken about 4-ish months of evenings to make a functioning prototype. Then another couple months to design the website/do user interviews/etc. Despite the flattering mentions, I still freak out a bit that not enough people will buy it when I launch. 2) Made a desktop app that had more of an 'interaction-first' approach, and inspired by folks behind Balsamiq. After 2 years of doing code, hiring a coworker, etc. It was 80% done, customers couldn't wait for me to ship, but some just-hired manager didn't get it and canned the project, along with my employment. Just downloaded what the old stuff they still ship, it has 2012 copyright info. Also, it hasn't been encouraging when going to conferences like microconf, where the focus and advice leaned towards "find that b2b niche and make a saas app, you're gonna regret otherwise"