Going from proof-of-concept to prototype, aka my single 1988 Ford Bronco II, offers up some challenges. Rather than using Seeed Grove to prototype temperature using a simple generic temperature and humidity sensor (the DHT11, if anyone is asking), I need…
So while I was figuring out how to get my application approved for the Microsoft Store, I decided to move forward with actually writing some code. Eventually I want to read the temperature in the Bronco, but before I get there I wanted to just test out reading temperature at all.
Being rejected is difficult. When I submitted my Universal Windows Platform (UWP) application to the Microsoft Store, I had no reason to think it would not pass with flying colors. I followed their checklist. I checked all the appropriate boxes, dotted all the t's and crossed all the i's.
Getting code from computer to device is a little bit different from just developing an application all on the same machine. Here's how the pieces fit together to get code from an IDE to a device!
What's a piece of hardware without the operating system to run it? When buying a new desktop computer, the decision often comes down to a few choices: Mac, PC, or Linux. With IoT, it's a little bit different.
Choosing hardware to prototype with in the realm of IoT can be overwhelming. There are so many choices for so many use cases! How does one choose?
Over the course of the next few months, I am planning on taking my 1988 Ford Bronco II and making it a little more smart and a little more connected, thanks to the power of the Internet of Things. I plan on using this cruddy old truck to experiment and learn about IoT