 Okay, good morning everyone. It's very good to be here. It's my first time in India. It really makes me happy to see so many people who care about JavaScript. If you look at the first JavaScript conference, it had a really short schedule. It was Brenda and I. What is JavaScript anyway? Launched in a quick wrap-up. So, back in progress, right? I think that's a really, really good thing. I'm from Sweden. So basically, where I travel, it's going to be nicer and warmer. If you can't hear me, I'm really funny. So I do run the Mozilla Hacks blog. The point with the Mozilla Hacks blog is that it's our developer-basic blog at Mozilla. We want to make sure that people can learn things about the open web. It's not only about Mozilla technologies or things that we do. It's for everyone who's part of the developer. We're trying to cover, now, JS, mobile performance, et cetera, et cetera, as much as we can. Also, tweets, usually actually see good things nowadays, I would say. I'm partial about Facebook live in the open web and Firefox web. When I go to a conference, I can usually talk about technologies and details and such. Then after the talk, a lot of people come up to you asking about Mozilla in itself. What Mozilla actually is and how do you make money and all of that. So basically, Mozilla is a non-profit. And the reason for Mozilla for existing is to keep the web open. We don't want just one player to own it all. We don't want one company to have control over the technology or how you do things. We want everyone to be a part of it and everyone to be able to take a part of it. And that's what we do on the money part. We make money through different donations and partnerships with search providers and such, over the time, in stockholders and something like that. So basically, we do the things that we believe are good for the web, not to make money or not to have a creative report. Do you look back a few years ago, it was only an explorer, and then Firefox came out to try and make things better. And I think the web browser climate right now is excellent because we have such good competition right now. And especially if you look at JavaScript, the JavaScript performance over just the last few years has improved so, so much. And I'm really happy about that. And some people think that, oh, for instance, with Google Chrome, that Google Chrome is getting a lot of user, that must be really bad for you. Like, no, this is perfect. We want to have diversity. We don't want to have 100% of the remarks with Firefox. That wouldn't be a good thing either. We want to make sure that it's balanced. So right now, we're in a really good place. Integrity on the web, their data. It's a problem with people sharing. It's just about knowing that the things that you share aren't going to be available to a lot of people. So, you know, just keep that in mind. We also try to stay up on what's happening on the web right now for how to make sure that we actually adapt to the things that people need right now to be slightly more serious as well. I think we have bias because I live in Western Europe. But if you look in North America and Europe in particular, that people have too much money and people are all for tube support. With the New York Times, people having subscriptions for New York Times. The average number of devices that are used to access the New York Times are six. People have six different devices to access it. That's not, it's fun, right? But it's beyond reason. And I think it's about the mindset where we are right now. Like, you know, you buy things you don't need with money. We don't have it because people don't like it. And I think that's a good summary. Where we're trying to go there is in order to make sure that everyone can take part of the web and also contribute to the web. And we'll tie it to what I'll be talking about Firefox OS. We bring up Firefox OS. It started a few years ago. And if you look in the mobile sector, with Apple and with Google, that they have over mobile. And we will look at Firefox. We offer Firefox and it's something completely open to use to some different platforms. And basically, more or less, we can't. We can't offer Firefox on iOS because we're not allowed to. We can't offer it in Android, which we do like. We can't offer it on Windows Chrome. So we're looking into different options. How can we make this better? And we came to the conclusion that we need to build a mobile operating system based on our technology. So it's only Asian, Thai, CSF, and JavaScript. And it's also made me sure that people wonder about Firefox OS phones, like, okay, you can pair a Firefox OS phone to an iPhone or Nexus 4 or something like that. And the way it is right now is not the same thing. That's not our initial target. We want to make sure that it's more about making it affordable in as many parts as possible of the world, so we're looking at South America or looking to Eastern Europe. And over time, I definitely hope we're going to come here and have something available in India and Africa and so on. And I think it's also about a lot of people that are going to come online the next few years. Like, there's an evaluation that's two million more people that are going to come online in the next few years. That's two million. That's a lot of people. And most of them are going to do it through mobile. And if you look at Africa, there's more people that actually have mobile phones than have access to electricity. So they have a charging pole for a charger phone than anything. So how can we offer a smartphone experience for them? You know, they might not even have one today or they might have a feature phone, like this old Nokia where one button is bigger than the actual display. You can rub your face to see what you're actually typing. It's a lot that you have two lines. So how can we get the most smartphone experience for more or less the same price? So that's where we're aiming, initially, with Firefox West. In emerging markets, you bring smartphones to them with open technologies. Over time, I think it's going to change as well. I think we're going to see Firefox West on a number of different devices. I think, you know, the next year or something like that, you're going to see different hardware partners that we have, like LG and so on and so forth, having more expensive phones. So I think we're going to have a wider range of devices as well. But initially, we're going to make sure that everyone can be a part of it, instead of just trying to compete with existing ecosystems. Months ago, in the beginning of July, the first part also was released, which was really a special moment for me because I've been around since it started a couple of years ago. And it's something unique to actually go into a store and see the device in people's hands and actually start using it. And they were selling for 69 euros, with 10 Firefox phones for one iPhone or something like that. So I think we're aiming in the right direction. If you look at other countries like Poland, it's even cheaper with a subscription. Talking about different hardware partners, we have a few, like with LG, Sony, VT, Alcatel and such. And one partnership that was announced a couple of months ago was with Foxconn. And Foxconn is a company that built the first iPad, for instance. And they were talking about bringing Firefox OS to a wider range of devices. So we're not only talking about mobile phones anymore, we're talking about potentially tablets. We're talking about having Firefox OS on TVs and such. And that's what I think makes it interesting. You can imagine just building something that you already know, the use of technologies, where you can ship it to any kind of device, any kind of resolution. And that's really promising, I think. And we'll see what you're going to release and update on what they want to invest in when they want to release first. I think for me, it's about the potential like where can we go, how far can we take this? And talking about the history, I wrote a short, actually long blog post on how we sort of all went down. How Firefox OS started, what happened during the last two years. If you're interested in seeing how it actually came about, that would be a fairly good read. With mobile phones, people want to have apps. That's already been established. For me, I'm more of a URL kind of person. I went out with a browser, tested the URL, and I'm done. I do everything on the web. But people want to have apps. So we're looking into how can we still use open technology like HTML5, but package it as apps. So we started working with something called Open Web Apps. And the idea with Open Web Apps is basically just reusing what you already know, what you already can. You don't have to learn a new programming language. You don't have to use a specific IDE or something like that. If you built for the web Firefox OS, it's just another platform that it would just work on. You might not trust me like I'm just trying to sell you something here. But I think the point here is basically we need to use what we can. We don't need to reinvent the wheel over and over and over again. I think we need to get away from things like this, like with QR codes. Or like a two-page instruction how to use it or you can type in a URL. And I think we want to get back to that kind of simplicity. We want to get back to making the web more powerful. So building Open Web Apps, it's quite easy. It's just once in design. Your, for instance, will work out a box on Firefox OS. Then, and it will be optional, if you want to package it as an app and have the app experience, you can add a manifest file. And a manifest file is basically just a JSON file described in your app. So it outlines different icons for different solutions and such. Who built it. And you can also have different localizations if you support more than one language. And that's it. Then you're good to go. Now you've created an app. So it's really, really easy to get going. You have two different ways of building apps. We have packaged apps and hosted apps. And hosted apps means that you can have it in your own website. You can have this file and be installable, but you will still run the content from your own website. So you will control all the updates, the content, et cetera, and then no one else will, you know, tell you when to do it or when you can release it. It's all up to you. And then if you want to make sure that you have offline support, you can use, for instance, AppCache in HTML file to make sure that it works offline as well. With packaged apps, it means that you can have all the files in your app and just zip them up in one file. Then you install that zip file on the device, which means you install all the files directly on the phone and then they will run locally there. The difference when it comes to security with packaged apps versus hosted apps is that with packaged apps you can have it in the Firefox marketplace and reading the code and you can make sure that it's secure and then you'll be able to access more hard work and more APIs on the device. So that might be one option depending on what you need to do on the device and what kind of needs you have for your app. Back in 2007, when the first iPhone came out and they said, well, whatever things get made of web, just build a web app so it's gonna work. And then about one year later they kind of gave up on that and they went with Objective-C and the App Store and all that. Just documents for people building for iPhones back then. They couldn't access contacts, they couldn't access anything on the device and we just ran great pages. And I think the path they could have taken instead which is the path we're trying to take now is to offer more access to the hardware to offer more access to the phone. So we started a project called Web API starting to build up all of these APIs to make sure that you do more things directly on the web no other dependencies on the actual device. And it's also making sure that, you know, run everywhere that's not really true with Java still make sure that you don't have to adapt for any kind of platform or device but just write it once access API and it's gonna work we're gonna take care of it and if you look at other players in the IT sector they come up with new ideas one thing that's really important for us is standardization. So with the APIs which we don't want to build something just for ourselves we want to make sure that as many as possible support the APIs we want to make sure that other web browsers other platforms also support the same things so you can build something and it will work everywhere. And a few of the APIs have already been standardized and a lot of the other ones are in the works. If you look at the security you have a few different levels one level was it's just normal web content something you render within a hosted app so if it's being run from your own web server it's still on the same security so you can access more APIs you can access contacts for instance or doing cross domain XML and we also have a page on the wiki about the web APIs as you can see in the column with all the colors there it shows which API it is so ID means that it's supporting a Firefox desktop A means that it's supporting Firefox on Android and B in the right hand which is the old code name for the Gecko which was a Firefox a couple of years ago if it's supporting Firefox OS so then you can see with the API it's supported across all the platforms with blue for instance it means that it's certified so right now we can access that for security reasons so it gives you a good indication what you can use across the board of the only work on one or maybe two platforms and talking about building web apps in your manifest file you can also have a permissions part and in the permissions part you list what kind of certain APIs you want to access so if you want to access the contacts you just say ok my app is going to access the contacts this is what I'm going to use it for and you also specify what kind of access you want like is it read-grade is it read-only so the user knows and same thing with alarms and we also have on MDN you can see what kind of permission you need to specify and how you specify so it outlines all kinds of access so the regular APIs you can access from your web page and there's a good number of evidence with the ones with W3C are the ones that already been standardized so I'm just going to go through a few of them to give you a feel of what it looks like to code it and we're also trying to make sure that when you access the APIs it's as easy as possible to write the code try to have any super complicated names and with five people in the board I actually understand so it should be as intuitive as possible to work with it with the API you can access the battery on the device you have a few properties you can check the level of the device how much power it actually has right now you can check whether it's charging or not you can also check the charging time which means how long time it's going to take until my phone is fully charged it doesn't only work with phones it works on laptops as well and you also have discharging time like how long time it's going to take until it went to the text was happening so basically we had a charging change so you can see if someone is actually connecting the device to an AC adapter or if they're unplugging the device and the basic part here of sports is that sure you can build a dashboard showing how much better it is left but also be depending on what you're doing with your app how much power deception you want to use like if you can see that the user has a low battery level like a server or something like that they're not used to most performance things in our day and we're simpler then we have a screen orientation API screen orientation it's more about trying to make the user experience better for the user so you can lock the orientation you can lock the orientation to portrait for instance if you want for landscape but you also have a few other options you can for instance say landscape primary which means that no matter how we're holding the phone right now when you start the app it's going to go into landscape and if you start moving it around it's going to adapt to how we're actually holding we have the vibration API which is about vibrating the phone but people have the wrong connections as you can see so we moved on from that it was kind of hard to explain so we have the vibrate method which accepts a number of milliseconds so the one at the top here means that the phone is going to vibrate for one second the second one is a bit more interesting because you pass it in an array and that's going to be a pattern which basically means that the first value is going to vibrate for 200 milliseconds and that's going to be silent for 100 milliseconds and that's going to vibrate for 200 etc so you can have all kinds of different worst code experience or whatever on the phone and some people are building really interesting apps like that that you can have your phone in your pocket and you have navigation you're writing your bike or something like that I mean you get an intersection with your phones if you're supposed to turn left or vibrate twice and one that I think is really interesting especially as a job being along for a long time we had HTML code and then we had HR elements etc and then finally we did image roll over it was amazing and now I think what we have is really interesting is so we can connect our code to the physical world so with the device proximity API I can have a device and I can detect how close it is to something else if I move it around it's going to tell me how close or how far away it is and the way you do that is basically you have a device proximity event which uses the metric system and the good thing is you get back the value at 70 meters but you also have a couple of other properties you have the max property and the min property and the max property basically just means the sensor in my specific phone how far can you detect it's going to be 10 centimeters it's going to be a meter and the minimum means how close can I get before you start actually carrying how close I am giving the actual value of your device so in my mind what I found about this API I thought it would be amazing and you could move around everywhere it doesn't support that far distance right now so it only supports 0 up to 10 centimeters and I think over time we're going to support much bigger business as well we also have the ambient light API and with ambient light it's about detecting the light conditions where you are right now so if I had my phone out in the bright sunlight it's going to give me a really high value and what you can do with this is that you can have moon themes in your app in the left theme depending on if you're in the living room or if you're out walking in the street one, you can just change to see a desperate signal like if you're in bright sunlight there might be another contrast that you can use as code to make sure it's more visible so you have a device light event and the device light event returns the value a lux value and a lux value ranges from up to about 12,000 and 12,000 is basically rubbing it against the lamp I tested 15 there of course it goes all the way between there but just sort of remember that below 50 it's going to be quite dark and over 10,000 it's really really bright we also have a page visibility API actually I have to have snow with my slides have you heard about snow? it's amazing there's quite stuff that you can really use here with the page visibility is that you can detect from within your app if your app has focus so if your app has focus you might want to do something and then you know the user might leave the app do something else and then when it comes back to the app you can do something else again you have a visibility change event and then it's one simple property you have document.hidden so is the document hidden? yeah okay well it's going to be in the background otherwise yeah I have focus you need to do everything you need to now I have a few privileged APIs and at this moment you need to be packaged up as been approved by the Firefox Marketplace to be accessing these APIs Browser, if you want to build your own browser so this is a Mexico artist and to take one example if you look at device storage you have a navigator to get this device storage method where you can get into the videos folder here in the videos folder you can create a cursor so you can just enumerate or roll the files you have within that folder and when you get a result for that cursor you can use the file aid guide you can read out any kind of data about the file like what's the size of the file what's the type of the file and in this case when you check the actual type of the file you get the file type of the file not just the extension you can check whether it's actually a video file and then you can create the test player on the fly in the background so like sure it claims to be a video file but does it actually play and you know if it plays then you know okay this is actually going to work and then you can present the list to the user which files that you know will actually run on device not just all it might be video good luck that is good crossover I would say between the normal APIs that anyone can access and then the privileged APIs and also some of the certified APIs which are only tied to us like accessing the telephone for instance you don't want anyone on the web to be able to make calls on your phone for you and that's something called web activities so for instance if you want to interact with the camera right now in Firefox OS you can use an activity you can use the JavaScript code you call a certain activity like in this case the pick activity and you can filter out what kind of files you want to pick so I want to only pick image files from the device then I get a list on the device with all the apps that support that activity for those kind of files so the wallpaper app and the gallery app and the camera app says like sure I can give you an image and then the user can choose what kind of app it is for instance accessing the camera you can't access the camera but through this way it's a mix of your code and user approval so the user will see a menu and they will take the picture or do the call or something like that and then you can do much much more with your app and the way you call an activity within your code is that you call a most activity object and with most activity you specify the name of the activity you have about 10 or 15 of them and you will pick or something like that and you have data specifying what kind of data you want to send into that activity like if it's filtering on the EEG file for instance and then you have a success event handler and error event handler and with the success event handler you get some kind of data back from the app and if you build an app to support a certain activity let's say you have a computer app or an image sharing app you can also say that for activities I support the share activity but I only support it for PEP and GIP files so if any app calls my app through an activity and calling share I want you to display the sharing.hml file to that user it also means with this position I can choose how is being presented to the user window means leave the current app and go into my app and do something but you can also have this position inline stay in the current context keep on working if I go into my app choose an image and then go back and from within your app you can set the message handler so if any kind of web activity is calling your app you have an activity event handler and within there you can print out some data and then you can use post results or post error back to your requesting app then if we look at the future APIs and I think it's really important to talk about the future the thing about the future is also to talk about what are the things that we could have in the first version what are we going to do in the next version what are we planning, what are we thinking about so a number of the APIs that we're working with are things like having NFC through a web API having access to USB to connect the device to something you can access to USB calendars, balacacca, etc one thing I like here where I think Android is much better than iOS is that you can have any kind of keyboard like on the Android you have switch key and swipe and similar which gives the user a lot more options and I definitely hope we can see more options as well on partners like of course we try to make the keyboard as good as possible but someone might have a different idea and then we can also name the APIs so they can hook in their own keyboard here and another thing that's really interesting is where part is seen like how can we have peer-to-peer communication directly on the web through any other weird protocol and just yesterday we actually shipped WebRTC enabled by default in Firefox and Android as well so I'm really excited about seeing WebRTC coming to mobile but it's not really there in Firefox yet so it's being planned it's going to be there sometime definitely if you get a Firefox device right now there are a few default apps being installed like of course web browser, messaging and calendar so these are the apps that we have pre-installed directly on Firefox devices and then depending on the markets being released there might be a couple of extra apps from that local operator as well and one thing I really like about Firefox OS is that since day one everything has been available online you've been able to see the code on GitHub like every command you can see it's being built up with three different layers so we have GONK which is the small Linux kernel that just basically makes it possible to access the screen and things like that and then if we get on top of that which is a rendering engine in Firefox but then as soon as you boot Firefox OS this will go into a web browser window and in that web browser window you can see something called GAIA and GAIA is the user interface in Firefox OS and everything is HTML5 in there and everything in GAIA is on the web so if you want to figure out how the operating system works how the user interface is being built you can go here to GitHub you can see all the code you can see if you like a certain app like I love doing the contacts app I want to build something like that you can go in there, you can look at the code you can copy the code and also if you have an idea how to make that certain app better you can just do a pull-refer and that's the important thing we're not going to get any feedback we'd rather hear what you have to achieve with it as well and to get started with Firefox OS we have the Firefox OS simulator which is an extension in Firefox you just install the extension and you can run the simulator actually you have developer tools debugging and such and a number of APIs you can try to mock support for them in the simulator as well so it's a good start if you're outside or existing mobile web app you can run it directly in the simulator and you can see how it actually works I also put together something called the Firefox OS spoiler like that and a number of these APIs that I was talking about and also the web activities it's just a small test case and the code is not dependent on any libraries so you can just take any kind of small snippet in here and into your own app so if you want to access the vibration for instance just take that snippet so it's a good way to get started and just see all the different things you can do on the device and we have the Firefox marketplace where you just have your app you don't have to have your app there unless you want to the Firefox marketplace is just one of many options there's more about findability and for users to be able to find apps and for you to be able to have payments and sell apps if you want to but you can also have the app completely in your own website and install it from there and we would also like to see different marketplaces we can have a marketplace that only targets games for instance so we're trying to bring as many options as possible to people that aren't simultaneously like you know our marketplace is the only way and we're the only ones we can approve etc because people often like that and as part of the marketplace we have something called the developer hub and the developer hub is just a collection of information for developers talking about how to design apps and also how to publish them the main point with this presentation today as well is just an introduction and I'm going to be there for a few days so you can catch me or any of the other people and ask whatever you want about all the details and we can dig into it but I think what I want to sell to you today is the idea of trying things out so a number of months ago my daughter had a birthday and she was turning age so we gave them this small leather cookies that we're sitting having cake and a little birthday party and they got this small thing where each cookie is a leather so one can be the cookie and one is the leather just to see they can spell things now it took about 30 seconds and this was the first word I like the unexpected I like when people just hack them things and see what they can do with it if you can break it, that's great you can find something that can be even better so there's nothing wrong with that there's nothing wrong with trying failing as long as you actually want to do something and have the ambition to hack stuff that's what makes it really, really interesting and then if you tear it completely apart that's fine too I have this thing I have to have this in here so just slightly over time what I do want you to do well, during this conference and also in the future as well just go out and have some fun I mean, we don't live for that long just hack away and then do some cool shit that's what I expect from you I would need you to come back from ACM and play with CSS after do you think it's much more supporting that ACM and the answer is better if it comes with battery and endless speed okay so on the topic of phones in India the thing is that we don't sell the phones so we have different hardware providers, different operator partners so it's a bit more about which operators that are willing to partner with us and initially has been telecom in Spain and South America it's been Deutsche Telecom in parts of Europe and also TeleNOR in Europe so we haven't really had any complete partnership yet in India as far as I understand it there's a vast amount of operators and officers and all that so I have no specific date, I could make things up but I would like to and I would love to see it come to India I think India would be a wonderful market for partners but it's not... I'm talking about the one interesting exercise with fireboxers as well like right now I mean the different phones that we might have are more powerful than the desktop computers we had a few years ago and the interesting thing here is that we need to have hardware which are low level specs to be able to offer for a certain price and make it affordable for people so for me I think it's quite interesting to see like you know instead of loading four megabytes of data and every job as you apply for those that are invented you need to start thinking more and more about performance again what things you actually use so they actually answered the question I've been avoiding there are no concrete benchmarks like people are trying to do with benchmarks and then also we have a release schedule so something that was true today might not be true six weeks ahead because we have a new version that thing was fixed or improved or something like that so I think the difference with fireboxers we're going to have more frequent releases that can be once per year it's more like with web browser we're going to keep iterating and make it better and we're also trying to give advice as well but not only for fireboxers with any kind of device that doesn't have the same performance as an iPhone 5 it's not everyone has six hundred dollars to buy one so we're trying to tell people how can you make things work better on mobile should you use your quest animation frame instead of something else for Canvas etc etc and I'd love to give you and I can tweet later as well links to advice that we have and we have a few people working for us that's the building one person building the CraftsJS game engine and he was just listing all the advice that he has to make things perform as well so I don't have any actual benchmarks to give you when I'm looking into that the thing to think about benchmarks as well is that you can do benchmarks to prove your point but it's also really easy to piss a lot of people off and then get into a contest of just talking about which benchmark there's no one single ultimate benchmark that's the truth it's all about the perspectives it's all about statistics and I'll stop talking about I hope that's enough catch me later if you I just want to extend on what he asked before so the thing this is where if you're building games on html5 if you're using virtual performance is pretty much close what you get on native and it's really good but when you're building applications which involve DOM you don't really notice much of a performance issue on your own laptop because your processes are really good but when you're on your phone you start seeing that the UI is never as fluid as you'd expect on native apps so are there any words to improve the performance of the way you render your artings because it's become really fast but the amount of work done into rendering is not so much and secondly another thing between native and web is that most of the native platforms have a standardized set of UI components and that makes everything more consistent is there a plan for that in PyPox as well to implement a set of components so that most apps will look familiar to the users all the performance part JavaScript is really fast no matter what platform you're talking about I agree and the thing with DOM of course we're trying to make it better and perform it over time as well but I think it also comes down to the habits of JavaScript developers if you look at most use cases of JavaScript they keep on accessing DOM all the time like it's not always the most optimal way especially when we advise this like on a desktop you might not even notice when you keep on accessing DOM all the time clearing things and changing all that you shouldn't need to keep in mind when am I willing to be able to prize or just tell Max this like it's worth it I think it's delicate to palace between of course trying to make it better from our side but also pruning practices with it when it comes to UI and guidelines it's a really interesting topic I'd love to talk to people to talk to me later and tell me what you think about it we have two camps there we have one camp thinking that well it's just a web web doesn't have any guidelines it's free and open you can build whatever you want and then you have the other camp for instance iOS had a lot of success for being very consistent like it's a consistent user experience and think that we should have really strict guidelines from our box press so what we're trying to do is find a middle ground thing no matter how it works you can do that but if you have something that looks like the native apps or pre-installed apps native is the support that's going to be but like the pre-installed apps one thing is that you can look in and guide for instance like if you like one of pre-installed apps you can look at that exact course another thing is that we have something called the building blocks and the building blocks are basically so you have HTML snippets and CSS snippets to make sure that it looks like the pre-installed apps we're also looking more and more into web components and we have something called the celebrate which is just making more modular components for building well app headers and content and things like that we're trying different options so it's not just to have to use this library we have to use this guideline it's more about if you have a smorgasbord options but you know you pick what works for you and of course it's Firefox one it's here right now so we're also trying to figure out what works best what gives the best results for app developers we have one last question and then you can work Robert for that thanks for the talk my question is to do with open web so in this context of surveillance and stuff I know Mozilla is going to be open web that's for sure but then in terms of communication technology what is Firefox OS promise to mobile users people are paranoid using even android or you can't trust all the androids or all of android so that way in that context is there something Firefox OS users can expect in terms of privacy and stuff we have something called Mozilla persona but just to make sure if you look at the web if you look at the technology any website you go to you can comment with our Facebook blogging or you can test an app or something like that but to do that log in they can access all of your data if I want to write a comment they want to know when I was born and where I grew up relevant I would say so with persona for instance we're trying to in general with persona trying to build out the identity system for you where the data is encrypted no one else actually access it and you're completely in control but initially with Firefox OS it's more about right now getting an open platform out in the market and making available for people and also about where we can go forward it's the only days for that we do want to do that we do want to help the technology in any way we can but it's only right now awesome everybody give it up for Robert