Over 2000 backers. Welcome, everyone, to blink(1)!
Thank you to everyone who has backed us so far. It's incredibly cool to find others who also think the blink(1) idea is a neat one. Here's what we've been up to since the last update.
Sketching in Hardware 12
Stay tuned for links to the Sketching talks.
Thanks to all the backers who participated in the "blink(1) use" survey. (over 60% filled out the survey!) We broke the survey up into bins, based on how many blink(1)s you wanted, so we could see how those who ordered 40 blink(1)s differed from those who ordered two.
The general trend is that the majority of people who got a single blink(1) will be using blink(1) at home on a laptop. There was a slight preference of Mac OS X over Windows. For those purchasing many blink(1)s, Linux servers were a strong showing.
If you'd like to see the survey summaries yourself, here they are in PDF format:
- Group A (40+ blink(1)s per backer) survey summary
- Group B (5+ blink(1)s per backer) survey summary
- Group C (1-2 blink(1)s per backer) survey summary
More Enclosure Work & Customization Options
We moved to a slightly different USB plug that is easier to use in automated assembly (see the difference below) and reworked the outline of the circuit board to make it a little smaller. This means we've had to make a few changes to the enclosure to match.
For those of you who want different light output pattern than what the stock enclosure provides, we will be providing alternate enclosures on Shapeways and Thingiverse. If you've worked with BlinkMs, you know the LEDs we use can be painfully bright. We've been tuning the enclosure so the light from blink(1) isn't blinding but a soothing glow. But we also want to give the option of experiencing the fun of raw LED light. So we've made the case top removable for your own experiments. For instance, here's two blink(1) prototypes, one with a 3d-printed prototype enclosure, another topless but a glue gun stick used as a light pipe. LEDs are fun!
SDKs & APIs for blink(1)
There have been a few questions as to how you'll be able to control blink(1). We will be offering a variety of ways to talk to blink(1), from the very low-level to non-programmer apps.
First up, APIs we currently have:
- Raw USB HID SetFeature & GetFeature reports – Many programs allow sending arbitrary data to USB HID devices via "feature reports". blink(1)'s use of these reports are documented so you can do this low-level communication.
- C library – compiles on Mac OS X, Windows, Ubuntu/Debian Linux, Beaglebone/Angstrom Linux, Raspberry Pi Linux, DD-WRT Linux, and just about any other POSIX system with libusb/hidapi. This library should work with Objective-C, C++, and Visual C++ too.
- Command-line tool – Pre-compiled executable works on all systems supported by the C library.
- Java library – for Mac OS X and Windows officially, can work on any system with Java & libusb/hidapi.
- Processing library – Same requirements as Java library.
- REST local web service – Anything that can talk HTTP can control blink(1).
- Python API – the backers have spoken! We'll have a Python API too. This will likely be a wrapper of our C library instead of using PyHID, for maximum cross-platformness.
- OSC UDP receiver – Send Open Sound Control UDP messages to control blink(1).
With the command-line tool and the REST web service, just about any alert system on your system can use blink(1).
Our next update will talk about how to connect web services to blink(1). We should have something pretty cool to announce regarding that.