 I'm Wojtek, I'm a senior social engineer, I don't know like this, particle, I know if you guys know what we do, we manufacture internet connected modules for Internet of Things, which look like this, which can have Wi-Fi or 3G modem basically, and they are like Arduino but in built-in Wi-Fi or 3G. I know how many of you guys played around with Arduino, but it's basically small computer that can control stuff like LEDs, servos, anything basically that is like mechanical or physical. And the thing about like those devices that we actually do, they always try to connect to our cloud, they try to be connected to one specific place, which basically helps us, helps our customers to control those devices and do a lot of interesting features, which by using those four functions when writing a software for this device and flashing this onto this device, users can use our API to call a function on a device, so you can use API to turn on the LED on the device. They can expose variables from the device to the API, so you can use API to check the current temperature on a sensor that is connected to the device, and you can also publish and subscribe to events so like device can talk to each other, you can subscribe to events the devices publish, so a lot of communication between those devices and those devices and your cloud. Just the connectivity part, that's just basically the model modules and the old cloud backend on it, so basically just a platform for this. Another cool thing about the thing that those devices are always or at least most of the time connected to the internet, you can update the code over the air. You don't actually have to be physically near the device to update it, so this is something that you start your project with, this is a prototype, but then you scale, you actually manufacture products, you build intelligent thermostat, you sell it to your users, and then you actually want to update the software while it's already in your user's hands, so you can do it very easily. And also you can manage fleet of devices like hundreds, thousands or millions of devices quite easily and react and analyze the data that comes from your users and adjust and use it to actually develop better software. So basically to handle those two problems we created two Ember apps. First is built, which is our Web IDE, maybe not this much, and yeah, we try to keep it as simple as possible, this is the entry-level IDE, we also have Particle Dev, which is more advanced, but this was supposed to be like Arduino and it has like a couple of features. You can have multiple apps available wherever you are and thanks to this, you can basically have any code and flash compile it while in a browser and if the code compiles, which it did, you can basically flash it to a device. It also helps you to manage all the devices. Yeah, list of your devices, you can add them, you can change the default firmware version you want to use on a device and a lot of interesting things with devices. So if you have a device selected, you can just click flash. The thing is the device is in my office, so you won't see the result. But yeah, if flash has been so successful, so the device is updated and I'm not even there. So it already changed the code and also to help users build products faster and make it easier, the IDE also has libraries. So this is just a brain, it doesn't do anything by itself, but when you connect a temperature sensor, when you connect like LCD screen, like any button, something, you need to write some code to actually support it. You have to write some code and basically what we try to do is port as many libraries as possible and have them in this one place. So basically using this, you can just include example code and write your software that connects to these sensors and whatever external. And yeah, if anyone wonders, this is Ace editor, I'm going to talk about the back stuff in a bit. But yeah, the whole app is an number, it's 1.0. We're going to update it as soon as possible. First we have to remove the legacy rails back end because we have one common API which is backed by node and we want all our tools to use it and so all the features that are currently here are available in our other tools or whatever tools anyone can build on top of our API. So yeah, that's the one Ember app that we did. And the second thing that we wanted to handle is fleets of devices and how to manage a product in a company because that's the thing. We sell those to hubbists but we also sell them to companies. We sell them to companies that make internet connected coffee machines. So then basically when they buy them, the customers, they are our customers but they have their own customers. So how do we help them manage their customers? So this is why we created Dashboard which is a separate app which is more recent actually. And what it allows us to do basically it's when as an organization you can create products and those products can have different levels of access. Like just part of your people in your organization can modify them. You can basically see all the devices, see if they're online, what's the last time they were actually online, which is sometimes useful when some device hasn't been online for a long, long time and you can basically maybe check up on this. And also it allows users, well, organizations to manage their firmware versions. So if you want to update new codes on all the devices, you can basically say hey this is the latest version I want all the devices to get and then when the devices wake up or are available to update, they will actually get the latest version and update themselves. It has a lot of checks like if the coffee machine is in the middle of brewing coffee, it's not going to be like you know what, I'm going to update myself right now and just spew coffee all to the table. It is actually it's going to ask the device like hey are you ready to receive an update? Yes I am, then go ahead. So this way you can basically manage what is the software that is supposed to run on your devices and it also allows you to roll back, which is very useful if latest firmware version that has been distributed to all the devices has a bug. Like I know if anyone of you has a Nest thermostat but latest version bricked it. So I hadn't had a thermostat for like two weeks because they had to send a replacement because they weren't able to fix it remotely. So yeah, you can basically hear a button and say yeah I'm just going to roll back and all the devices will come back to the previous state. And you can also basically watch the events from the devices, so whatever what they do, you can seal of it. I forgot that we have a third Ember app. I should get it too but this is a Wi-Fi module. We also have 3G module which we give a SIM card with. So basically in this case we wrote the whole panel that shows what's the current data usage, what's the cap, how to increase it and stuff like enabling and disabling SIMs. But yeah that's our second Ember app. And yeah like I said the stack we mostly use Ember. We did I think two React apps which were more of a experimental thing and not to be... Basically there were a statement about not becoming an Ember shop. Basically just saying like okay maybe we should have a bit of distribution. But the most important apps of our stack are using Ember. Like I said they are backed by Node.js and Express. Most of our like 90, 95% of our stack are backend is basically Node.js and Express. And it's all backed by MongoDB which basically connects very easily with this. This way. And yeah of course we're also hiring. So if anyone thinks that internet connected devices are cool and writing IDEs is cool and when I'm saying IDEs I don't mean Eclipse. I mean cool Ember IDEs. Let me know. I'm gonna hang out a bit so you can ask me anything. And yeah thank you. Do you have any questions? 19 bucks for this one which is called the Photon which is the Wi-Fi kit. The 3G kit starts at 39 and I think 49 for the 3G version. And the thing is like you can just go to our website and just buy it. Like you don't need to sign any NDA, CLA's, whatever A's. Basically you can just buy it and tinker with it and if you decide it okay this is like whatever I did is cool and I want to sell it and go to Kickstarter with it. We can basically use the same thing but in a smaller package which you also sell and you can also order it on the website and basically ship your product with the same code and without doing any changes. It needs a power source. In this case it can be powered by a from a USB. It also has a separate pin that can be used to charge. The 2G and 2G version has a battery that you can power from. You can also use like a solar panel which like in case of the 2G and 2G version it's designed to basically be in a remote locations like I know maybe it's in the forest or something. So it's really low power thing. In case of the Wi-Fi one well we expect like if you're in a Wi-Fi range you have some plug somewhere so yeah it doesn't really. It works in a battery but is it designed to be plugged into like actual power source. The thing is our firmware is open source and we already have and with recent huge overhaul of the firmware is basically our own stack can work on anything you want. Like if it's it can work over ZigBee. I don't think there's implementation for ZigBee or is it? Maybe someone is working on it. There's definitely a separate version that uses Bluetooth low energy. There are someone that plays around with Laura and this kind of thing but the thing is it's definitely it definitely can work. It's designed to work on everything we partnered with Telefonica so we are we are basically MVNO and we sell their data but the thing is the same you're getting you don't actually have to do anything with Telefonica. You only talk to our APIs and our panel and the current plan that we offer works in more than 100 countries so yeah we also sell data for this. If you want you can also use a SIM card like your SIM card with the device but what you should check first is your agreement with your operator because there's like 99% chance that there's a one clause which says this SIM cannot be used for M2M communication which is the machine to machine usage which basically scratches most of the SIMs to actually be usable for even playing around because it's basically breaking the agreement with the operator. That's the thing like if you want to use it they shouldn't like if you do not put stress on their network they're probably going to be fine they want one notice but yeah if you would if you have a bug that basically streams data or like streams debug logs over the air yeah it's possible they gonna see that now that's that's not a cell phone. It's not someone watching YouTube it's it's like you know something that malicious device basically that's the weird part they do less actually but it's more of it's more of this is where is the money so they actually want to say yeah yeah basically I'm not sure that's that's interesting question because because that's yeah yeah well they yes you can expect it yeah but that's the thing it's not it's not about the actual data which is sent it's the device that does it so it's like if they basically treat this as a not certified device like we did not test this device we didn't know what it's gonna do probably we got it's gonna make our network unstable if it's make our network unstable then other customers will get angry so this is why we are not allowing you that's the official version the unofficial version is well just come and talk to our sales rep and then you're gonna see there's a thing like usually if you're one person and have like five devices it should be fine but if you don't want to like have any troubles you can just you know give us the three bucks a month and have a sin that's gonna work in hundred countries without roaming coasts and like just have something that works