Developing prototype custom IoT solutions usually means a breadboard, jumper wires, sensors, peripherals (such as a realtime clock and storage), a microcontroller, and a lot of custom program code. Deployment into the hands of users is another additional project in itself. What if you could simplify and speed-up the whole prototype and deployment process using one simple, compact and cheap device?

What if prototyping and deploying custom IoT solutions could be as simple as following these steps:

* Pick up to 3 standard I2C IoT sensors from 100's of choices from different makers. Mix-and-match whatever you need.

* Plug them in.

* Power on.

* Start logging IoT data. Data-local by default, but stream anywhere if desired.

* Fits in your pocket! Low cost.

Why did I build it? I was frustrated and tired of reinventing the wheel and building a rats-nest-of-jumper-wires prototype breadboard every time I wanted to have an IoT device to log some data (specifically, data that was then wholly under my control). And when it came time to putting it into the hands of users -- say, on a limited basis of tens of users -- deployment was a nightmare (a rats-nest breadboard doesn't neatly and snugly fit in anyone's pocket!). After a lot of experimentation, what I came up with manages to fit a lot of electronics (RTC for highly accurate timestamps, MicroSD for local storage, powerful MCU, display and control joystick for setup and operation of the device) and pre-programmed functionality into a protective clamshell enclosure the size of a pocket-friendly Altoids tin.

The exact same device (in terms of functionality, capabilities and firmware) is available in two form factors: 1) a pocket-sized fold-closed clamshell device the size of an Altoids tin that opens when needed to expose the sensors to the environment, and 2) a pocket device that does the same and conveniently mates with and pairs with (via Bluetooth) your smartphone. The only tangible difference is in the plastic enclosure, which I feel is not a key feature and changes functionality not one jot. I'm of the mind that choosing between the two is a rather inconsequential decision, other than personal preference and convenience. But the feedback I've gotten from experienced engineers and product designers is that this choice alone -- two form factors, two different pieces of plastic -- has already, and utterly, doomed the device. My instinct is to let the IoT community and market decide? Comments?

Demo video (~5min): https://youtu.be/DrpaWU58Om0

Fact sheet: https://tinyurl.com/IoThingyFactSheet

The Personal (Pocket) IoT Manifesto: https://tinyurl.com/PocketIoTManifesto

Find out more & follow project: https://iothingy.io/

Coming to Youtube are additional videos for specific features of the device, just search for "IoThingy".