Ask HN: hardware startups, where to begin?
Every once in a while I get an idea for a cool little gadget paired with a web service. I'm pretty good at web services but have no idea how to approach the task of building a hardware prototype on the cheap... Any blogs/sites you guys can recommend?
13 comments
[ 4.4 ms ] story [ 42.2 ms ] threadPrototype, make it efficient, make it cheap (fewer components), make the spec, find someone who can do a test-market batch, and if it catches...SCALE.
Any ideas where to start investigating.
There are many platforms that might be appropriate. Why not start by writing code for an iPod Touch and then see how it goes from there? You will probably refine your ideas during prototyping, so starting with a flexible (if expensive) platform that is easier to program can be helpful.
Another example of a small device that could be interesting is the "IM-ME", which sells for about $15 retail, and is pink! see http://hackaday.com/2010/01/06/update-more-pink-wireless-ter... and http://hackaday.com/2009/11/30/pink-wireless-terminal-of-won...
HW startups have bit more front-loading, couple grand to produce an MVP, 10-20 grand for a small production run.
http://radar.oreilly.com/2010/07/the-manufacturing-future.ht...
Can you constrain the problem? Can you assume the cat is inside your house and you want to know which room it's in? Or is this lowjack for lost pets that wander away from their homes?
Getting a fix on the pet's position is probably the most challenging part. Transmitting information from pet to the web is easier.
You may want to look at the snif tag as an example of pet activity monitoring. It is like fitbit for dogs (or cats). http://www.sniftag.com/
I've built a few gadgets that collect data, analyze it, and then send it to a data store on the web. Think carefully about your needs for each of those 3 steps, as well as your readiness to get into low-level technical details. And then tell us more about what you're trying to do.
In the mean time, here is some general advice:
In my experience, the connection to the web is the most challenging part of the project, and the one that has the most impact on the total cost of parts. Most of the microcontroller kits that appeal to casual developers (such as me) do not include ethernet or wifi connectivity. They assume you will be connecting via USB to a PC. Adding wifi or ethernet to an arduino significantly increases the cost and complexity. For stationary (non-mobile, non-battery-powered) gadgets that need to communicate with the web, I can recommend using a wifi router as a development platform. Many of these can run the OpenWRT version of linux, and collect information from a USB port. Here is a good description of working with linux and USB peripherals on a wifi router: http://mightyohm.com/blog/2008/10/building-a-wifi-radio-part... As to cost, the router used in this blog post costs about $30 (http://www.newegg.com/Product/Product.aspx?Item=N82E16833320...).
Another thing to consider is the analysis step. Some devices will have no need for fancy data analysis, but for gadgets that need to work with data in complex ways (learning/compressing/transforming) you may run out of processing power and/or memory on some of the microcontroller platforms. Again, a wifi router is quite capable here - as long as you stick to fixed-point operations.
Once you have an idea of a suitable hardware platform, then it's off to the races. There are many great places to see examples of hardware projects, as mentioned by fragmede. And you may want to consider working with a hackerspace (NYCresistor, noisebridge, etc) - I've found that having an oscilloscope is very helpful for troubleshooting my gadget project.