> The system uses the Leap Motion controller to track hand gestures. Implementations of the system include a version using 3D glasses, a free-standing glass projection (as seen in Iron Man) and the Oculus Rift headset for the full virtual reality experience. To top it all off, the team then printed the part in titanium using a 3D laser metal printer.
A prominent quote from the article with links to both LEAP and Oculus Rift. I'm not sure
I haven't really thought of marketing myself that way, but that is a great idea, Thanks.
I guess I've never thought about it because I'd imagined that it'd be such a niche skill that it would be difficult to build a consulting practice around it. People are always looking to build new things. But, they're maybe not as welcoming to talk about their failing projects.
Anyway, I have probably (inadvertently) turned around a good 12-15 projects that way. So, I definitely have results. But, the results aren't typically super pretty. That is, it gets people to the next step, to the next set of funding, to the horizon, at least. Some of these projects and companies that I've helped have been sold, and resold, because of these types of efforts, though.
As for adding a developer to the testing role - it is an interesting idea; I've never tried it. Typically, at this point people are scraping the bottom of what they have left to spend. So, it may be a hard sell. I could try it.
Hah, as I was reading your post I was thinking "they should hire this guy to fix it up". Triaging projects is definitely a valuable skill, and like any time/mission critical skill, likely to be highly paid if you can market as such.
I'm building a SaaS product right now and finding that there aren't very many sources for finding industry standards. Non-enterprise SaaS is quite new.
That said, I think the best thing to do is wait until you spot abuse, and create measures to prevent it. Work on your analytics and reporting systems rather than trying to contrive possible service abuses.
Hey thanks! Especially for the MVP, I think you're absolutely right about the abuse part. As for the login/recovery, have you had any experience with signup rates using Facebook/Twitter authentication? Reinventing the login flow seems like a bad idea to me at this point. For billing, I'm examining Recurly and Paypal Subscriptions (although I'm wary of Paypal).
I'm rolling my own signup (which is easy enough in Django), but I'd consider doing a Google login. Facebook & Twitter I wouldn't care to implement: My target audience wouldn't want to be mixing their social logins with my service.