There's NO WAY I get all that in to a 60-minute talk.
You might be surprised– I'm always amazed how little time my demos take onstage.
How much time (if any) should I spend on the IoT as a whole?
I agree with @jon Jon– people seem to have heard of IoT by now, but it's so buzzwordy that they don't stop and think about the practical effects. So I'd say skip the estimated X billion devices statistic, the up-and-to-the-right graph, and focus on some use cases for what connected everything really means.
E.g. what if every item in the USPS system was broadcasting its whereabouts during its entire path to delivery? What would be the effect, if we knew exactly the moisture content of the soil at every point in a field, and the projected rainfall on each of those points, and could control watering accordingly?
Of course, this goes straight into:
What's important to show in the intro demos (which modules, which features, etc...)? What's going to have the highest "Wow!" factor?
Which is tough to bring together, because (imo) the really cool use cases of an internet of everything are the subtle, useful ones that don't really look like much on a stage.
Though perhaps you can find a happy medium– I've also put some thought into "where is IoT useful in the setting of a conference presentation?" Maybe there is some way you can be tied into the environment of the conference itself and demonstrate the effect of IoT that way.
Which again transitions beautifully– nicely structured question flow!
What's a great project idea to tie it all together with? I want something that is either ridiculously useful, or perhaps something that could be interactive with the audience.
One fun, easy way to get audience interaction is to tie in Twitter. At Solid this May, I hooked up some Hue lights to sentiment analysis on @technicalhumans tweets and had the audience give me live feedback that way.
I've also considered doing some sort of conference installation piece along the lines of Mark Weiser's dangling string example, where the motion of the string is based on tweets tagging the conference hashtag. You're welcome to use my ideas, btw.
I feel like there has to be more that can be done in a conference setting, but most of the interesting applications aren't onstage. What do people care about when they're sitting in the audience? Is there some way you could tie in sensors from elsewhere in the venue? Let me know if you figure this one out.
How do a put a bow on the whole thing? I want people to walk out wanting to go order a Tesselfor themselves. What's the most compelling thing about Tessel in your opinion?
In my experience, by far the most compelling feature of Tessel is how easy it is to get started. I usually show this and then go through the code for a demo. People love the
npm install, especially for the modules since it's printed on the hardware.
Good luck, and reach out if you need anything!