Seriously... that's a "radio voice" if I've ever heard one!

Super interesting. Looks like you think there are a wide-range of potential use cases (https://www.getstructure.io/use-cases) but will be curious to see who the early adopters are... thoughts about who jump in first?

There's a lot of interest in manufacturing and logistics (warehouses and trucking). I think that's because these industries are under served for technology in general, and IoT is great fit for their a bunch of their use-cases.

We're working with several early companies in the industrial space, especially logistics and manufacturing.

Seriously great summary (love seeing stuff like this rooted in real world experience/examples). Thanks for doing!

Predictions on how quickly adoption grows after 1.0?

I think it will be a pretty sizeable jump (100% growth?). I expect the next 0.8 release will make a lot of noise when they leave Handlebars behind and really ramp up the rendering engine side of things.

Yea, I need some jade or haml, as the current packages are brittle as f#%k.

Asset ordering for packages is another important issue I'd like to see rolled out for 1.0.

In terms of growth, who knows, right now it appears to be linear, but I feel a ramp up is coming.

Interesting, we haven't really run into big asset ordering issues, we tend to stick jquery plugins and libraries in /lib or /client/lib

Yea, I wouldn't call them big either, but they happen none-the-less. For package developers it can be vital. Sometimes A must be loaded for B. It's mainly a third party javascript issue. The compatibility folder sometimes does the trick, but by contrast the same utility doesn't exist for package developers. It's a larger dependancy management issue not tackled by the current packaging system.

Yeah, the current packaging system is more of a download installer and less of a dependency management system. That should get a lot better in 1.0. As for Jade, https://atmosphere.meteor.com/package/jade-handlebars is working towards this. It also appears that Meteor is (or was) thinking of integrating Jade support in Meteor directly: https://github.com/meteor/meteor/tree/jade

Two quick thoughts: 1. still fairly wordy on several slides (I know, it's REALLY hard to whittle down more) 2. you only hint at how you might make money: biz model should be very clear (you do a good job explaining how you'll spend $, but not make $)

Thanks for your thoughts! I'll work on improving those 2 things.

I'm a big fan of transparency. I'd explain the situation and let them know that you believe what you now own is valuable, but that you're happy to give them the first rights to (whether they hire you or not).

Could offer it as a deal sweetener if they do work with you, but also just offer to sell it at a reasonable price if not. Truth is today it's prob not much more valuable than what you paid for it, otherwise you wouldn't have been able to get at that price.

Totally agree. While getting our company off the ground, my co-founder and I regularly played basketball together a few nights a week. After a long day of the grind, it was a welcome change and I definitely think helped us in the midst of several difficult decisions/questions.

As icing on the cake, we also met what would become one of our first Angel investors while playing!

Really is a head scratcher: paying more money for worse coffee. Understand that convenience is a major factor, but kinda crazy it's enough to justify...

I think you need to get more detailed in your ask. Your answers are probably going to be significantly different if you're talking about white labeling a physical good (like Coffee or something) vs. software.

What are the core needs that a spreadsheet can't solve for small operations?

you'll see :)