 Can you hear me? We need the Tizen team production because we're introducing you to the Tizen and specifically for those of you who may not be aware about why there is need for another ecosystem in the first place when there are already available in the market. and I would also like it to be more interactive so that whenever you have any question and all you can interact with me. So to start with, I would just like to tell you why there was a need of another platform in the first place. So Tizen specifically is not that something which we started new. So its basic components started somewhere around 2007-2008 when Samsung tried to first build a platform based on Linux that we used to call Samsung Linux platform. So when we launched the first product in 2008 based on this Linux platform, maybe probably it was too early for the market. So I mean at that time you had hardly heard about any platform selling which were specifically based on Linux and they were multitasking and had so many features available at that time. So what happened during subsequent years is that we had another platform called Vada which you are aware about. I mean most of you might have worked with Vada but Vada was not based on Linux to begin with and then we launched Vada in 2010. So we saw some success in some of the markets specifically in India as well as Europe. But then Vada also had its shelf life, right? I mean when we have to probably compete with the platforms like Android or specifically iOS and Vada being a closed platform and specifically developed only by Samsung and keeping into consideration a lot of developmental costs. So we at one particular point in time had to decide what we do with it. I know many of you must not have been happy when you heard the news that Vada is continued. We still get emails from people, the users of Vada phones that are saying that why did you do it in the first place, okay? Now whatever experiences we had with Vada specifically, I mean we had a lot of voice of customers from Vada and then we thought, okay why don't we apply that on another platform which is basically Linux platform and then maybe try to view a better platform to the users worldwide. But then by that time the landscape had eventually changed. I mean when you had to face Android or when you had to face iOS and Samsung kind of a company coming up with a platform on their own which will be the closed platform to begin with so there may not be many takers. That's why you will see Tizen is basically promoted by Samsung and Intel, right? So now initially it is Samsung and Intel but off late you will see that Huawei also joined in the Tizen steering committee. So basically now the point is when we talk about Tizen there are three elements which I want to focus on. One is that it is purely web-centric. So like you saw the earlier presentation by the Mozilla just now. So the entire focus of Tizen platform is going to be on web. So we would like developers to write applications which are purely HTML5 based and we would also like you to be able to monetize them on different platforms. Now is that sufficient? I mean if so then there are many platforms which are coming up, which are web-centric for example Firefox is one of the operating system which is coming and which is also promoting web specifically then what else could be there in addition to being a web-centric platform? Now what we have seen specifically with Android and with iOS is that both the operating systems actually are in one of the way closed operating systems. I mean iOS and Android is purely dominated and controlled by Apple and Google even though OEMs can use it but then the decision of what comes in which release and all is purely taken by Google itself. So one of the reasons you will see why Tizen is an open-ended platform and why there is something called Tizen association which is going to drive all the decision making is to ensure that there is no single entity which will have the open-ended of the Tizen operating system in the first place. So if you go specifically and if you see the competitive Tizen platform, the first thing specifically we are talking about is source code. So the entire development of Tizen platform will be open sourced. That means not only that we will be using some of the open source components, I mean if you see Tizen specifically uses something called EFL, many of you may be aware about there is something called EFL as the windowing subsystem and Canvas. That's the open source project and we have taken that and it is also using X11 as the windowing subsystem. Then it's also using WebKit too which is an open-ended web engine. So basically if you see all the fundamentals of Tizen platform will be open sourced. Now when we are going to take a lot of components from open source and all, so it is imperative that we should also involve developers into developing the platform. So we have already released Tizen 2.0 but from Tizen 3.0 onwards, any one of you can come and start participating in developing the platform except it is open in the JIT. There is an open JIT available as of now where you can come forward and go to the Tizen association and say that I am willing to contribute to the platform. It is not only as an application developer, not that you have to just go to the SDK and use some API and develop an application and sell it. No, even in the development as well you can come and contribute. So that is basically when we say source code open. Now we say Android also, the code is open but you will not be able to decide what should come for example in the KitCat release, right? You will not be able to decide that you will not be able to decide. Similarly if you go to Windows for its proprietary and there is no question to even come to that discussion. Then when you come to App Store and all and if you see today on the Android side and there is a lot of fragmentation in the App stores, like every OEM is trying to build their own App stores, right? And every other service company specifically, let us take the example of OpenMobile, right? OpenMobile also has their own Android stores. So there are so many Android stores available now. So you really don't know from where to be bought off. Of course Google's App Store is the most famous one but we would definitely like the situation to change. We would not like to have so many App stores in the first place because the problem is that an App Store is dominated by a particular entity. That is where there is a need to open up your own App stores because everybody wants the, I mean everybody wants the high App Store, right? So why specifically for example when you say let's take the case of Samsung itself. Samsung itself has an App Store and Android as well, right? So now specifically when a user is buying a phone and all and sometimes gets confused whether I should download this application from this store or this store or where and so that's what we call fragmentation specifically. But how is it going to be different in case of Tizen and all? Our App Store is going to be governed by Tizen Association and we will tell you what are the members of the Tizen Association. I mean if you see, specifically if you see currently, current board members of the Tizen Association are Vodafone, RA and Dokomo. Of course these are driven by operators. Then we have Korya Telecom, we have LG, we have SK Telecom. Then there are currently many vendors who have already supported Tizen, Samsung, Intel, Huawei, Panasonic, Fujitsu and of late you see Huawei has drive even in the steering committee. That means all the decisions that need to be taken into what should constitute Tizen 3.0 or beyond, what should be the roadmap, what should be the strategy. It will not be decided only by Samsung, it will be decided by Samsung, Intel, Huawei and then the implementation of that roadmap or what features you would like to take even the developers also can come and start contributing. So that way this is going to be a new paradigm shift which you will not see in the existing platforms. Of course how successful it will be depends on how successful the model itself evolves into but if you see the presentation given by Mozilla as well. I mean whatever effort Mozilla is trying to do or WebKit is trying to do is to basically take the shift towards open source, take the shift towards where the developer itself has a say into not only the platform but also into the application development ecosystem. So one example I just wanted to give you here is honestly I mean if you see I mean Samsung kind of company for example you would not have heard about Samsung probably coming out with a platform like this where we talk about so much open source, open source everybody is involved in. Not that Samsung wanted to be a philanthropist and say that no we want to do good for the everybody in the world, I mean that is not the case in the first place. But how different you want to be from the existing ways for I mean ecosystem is what is pushing us into this you might say. So recently actually we were in one of the conferences on the Vintula and IVI identity segment in Barcelona and where we get surprised I mean companies like BMW and General Motors are coming and saying we have a lot of code which we have written for our cars and our vehicles from 30, 40 years and all. They are all ready to open it up because if we don't open it up and all somebody else will open it up and then we get market acceptability and then we will die eventually. So today nobody can even think of maybe probably is there a reason why nothing was to die one day. But then there are many commentators and are who say if you continue to be as closed as possible that is a lot of anger, frustration not only with developers but also with the end users saying that why for example one of the example you are saying is why I should buy another device if I have to probably use another browser, another browser version. Or why is it so difficult to transfer data from my Apple iPhone to another phone which my wife uses probably your wife may not use the same I was right. Why is it not possible for these OEMs to come together and perhaps have a common interface where they can make our life easier right. So that is the frustration which is slowly slowly building up I am not saying that it is going to explode tomorrow. But this is what we have seen and many traditional companies which I mean until recently will not even open even a single bit of their code and all coming at saying that yeah we are ready to open up right. So in that segment and all if you see it is a big transformation for Samsung as well where we come and in such form to say that yeah we really want to share our entire code, entire I mean all the development efforts which Samsung Intel together has done from many years and all will be opened up. For you to see and update and enhance as I said from the platform point of view. Now if you come to this specifically as I said I think in my opening comments itself I explained specifically web. So what Christian was saying above was that one of the platforms and all where he has seen the best web store is Blackberry. It was true some time back and all so you all have the browsers available if you just go itself now and see which operating system or which platform has the highest html5 score it will be Tizen if it is 4.2 out of 500 you can just check it. Second is Blackberry of course maybe his intention was to probably compare those platforms which are already available in the market because Tizen product not being available in the market probably you might not have included but you can check it out. So why we are saying this is when our focus of the Tizen and entire Tizen focus is on web, html5, JavaScript, CSS right. So in such a case our first priority is to see what kind of environment we can give development environment, development ecosystem we have framework to the developers so that when they write an application which of course may be compliant to html5 but what about performance right what about those device APIs with which you would like to control the device hardware the sensors the gyroscope right. So it is of course not a sufficient that yeah we say that we are html5 compliant and we have 100% W3C compliant APIs available but those W3C APIs may not give you access to the camera right. Because if you see the standardization in those areas is so slow probably to be very honest and all it is not slow because it takes time it is slow because it is deliberately made slow. I mean nobody would like for example today if you tell me if the existing app stores for example iOS or Android and all are so popular and all why would they like happily one day you to come up with an Android application which can run on all the platforms in the world. Then how can you write an application only for iOS right I mean when Facebook comes and says that we will write an application only for Facebook only for Apple right. And there is a separate version of Google app application coming for Facebook only for Apple only or for example Samsung only. So why is it because inherently OEMs wanted this fragmentation to be there otherwise what difference I can make I mean how can I be different from you. So I can be only different if I follow standards to be 100% compliant and all right. Then the only differentiation I can make in the hardware okay how best my hardware is. And you know today even if an Apple phone or a Samsung phone is made and all where from the hardware comes most of the hardware components right. So the differentiation can be in the software and all but that's why traditionally it is kept at that okay. Whenever somebody comes and says that we want to discuss an API how can how I can get access to a parameter for example. And then you can see how the discussions go and how much time it takes and all and by that time what happens is a developer gets frustrated. So what he will choose is he will go to he will choose one of the device API which is available in for example Tizen or Firefox and all right his application. Now he will wait for standard to come up it will not come up then eventually he has to port next day he decides I want to put this application to enter. Then he has to make the changes, make the customers know that's how the market has been consistently running. So where we say that our web score is the best and all right because when we are promoting Tizen as an HTML5 open standard based. So which means our web engine, web code, our web framework performs has to be the best. So that's why as I mentioned 492 is the HTML5 score and Blackberry is very close 485. Now if I'm saying that W3C standards is taking time right it's not for you guys to write an application today which can straight away fit into another operating system tomorrow. Then you will say okay what do we do okay when is that going to happen. Honestly speaking in 2011 we thought that by 2012 the entire W3C standard relation will be complete and then we can really give away all the flash all the other things and all and it will be more HTML5. It did not happen, it did not happen in 2013, it will not happen in 2014 as well. Two reasons if you see the hardware itself is also evolving right it's not that okay we will keep hardware fixed and say okay we will write all the standards and then one day they will get complete. While standard relation is moving with its own pace and all the development at the software side and hardware side are also I mean going very fast. So I don't know when they will actually converge and then we can say that now I can write an HTML5 application which will run seamlessly across the platforms. And that is the reason why PhoneGa and OpenMobil kind of companies are coming up and they are giving you their own solution and self selling their own components. So what we decided in Samsung is that okay for example my goal is not only to make a platform and say it's already available anybody can come and write an application. Maybe OEM can come and make a phone with it. By the way if you can see there is one slide where it will show that this particular platform like Google and all will be taken by many other OEMs. It will not be only Samsung or Intel who will make products with it. There will be other OEMs who can come, take the platform, make phone, whatever it is. But then what do we do? For example tomorrow Tizen platform is ready now. We are going to come up with the first product in November. Now let's assume another OEM comes and says that I will use this right. So they take the platform and then they make some web apps and all and they try to sell it. But knowing that the web performance is not what we want today. Okay so one of the examples could be you have seen already Firefox is launched right, Firefox is launched in Europe and all. You can go and check the reviews, the performance of those web apps and all. It's not I am saying that there is inherently problem in the Firefox that's not the case. The problem is if you have an application which is remotely based on some other kind of data and all where only feeds come from one side where you don't need access to the hardware and all then you are fine. But when you go and you have for example a Facebook application where you want to get a handle of the camera and then you want to start a video chat then you see the performance right. Now what we thought is if we go ahead with web app and keep on beating the drum and if web standards are taking time one way is we give our own device APIs. So you will see significant amount of device APIs available from Tyson. But then the slogan of when I go to the developer and say that you will use the platform write an application which will work on another platform also that will not be the case. That's one part A and part B is even if I give device APIs if the performance is not what any user actually demands and all. Do I want to kill Tyson straight away and say that I will focus only on web and all. Yes my goal will still remain that it will be web centric it will be HTML5 but until that we can make it mature and all what do I do. Shall I keep where do you know. So that's why if you see Tyson will give you three kind of interface. I think it's mentioned in the first slide or somewhere where it specifically says maybe can you go ahead. Yeah. Anyway so the point I'm trying to make is that you can write a web application with it with whatever I said 490 to score the web kind of atmosphere we have given. In addition to this one you can also write an application based on 80 C++ interface. So all those guys who do not want to write an HTML5 are not familiar with HTML5 or do not want to move from a traditional CC++ kind of interface. You have a very well defined SDK available where you can write an application using C++ and then that C++ application will give you that performance which you need. So maybe at the same time when you talk to for all those complex applications which you want to write where the performance is very very important we still give an option to write a C++ application. Second advantage is all the applications which we had written for Vada which were available which developers have written. So because we have changed the operating system from a traditional one to a Linux one but we have managed to maintain the JBI signatures and the API compatibility so which means an application which was written in Vada will need to be just a compile and it will work on Python as well that much we have managed to maintain. That means most of the applications which were there in the Vada store will directly go to the Tizen store. So we are contacting those developers directly and telling them this is the way you can compile or you can just see in the source code I will compile and I will put it through the store and go through the certification. So there is another interface available for a fewer native application which will be based on C and EFL. The highest performance application in Tizen will be the EFL application because the only difference which we are trying to show from UI point of view is nobody else in the world is using EFL. So you can expect that our UI or UI interface, the look and feel, the richness will be different from Windows, from Apple, from Android. Otherwise if I make another kind of UI which looks a mix of this and that and also people are not going to provide the interface. So three kind of interfaces available is C. There is a C++ interface and there is a rare vegetable kind of interface. So all these kind of application ecosystems are existing in the Tizen and there are different kinds of SDKs available. The only difference is that native C1 is not available to developers for developing an application. That is purely given as an advantage to all those OEMs who would like a better application. For example if RA tomorrow comes and says that RA is the best application which is selling in Europe and people have got a very good feel and experience while using that application on their existing platforms. Probably we may research to them that this application we can quote has a fewer native C, EFL based because the performance is guaranteed. And we are also sure that RA does not want that application to be a downloadable kind of thing because that is why they probably must be taking some minor. So basically what I am trying to tell you is that we are taking care of OEMs very well because OEMs will be part of the decision making body. They can decide how, as I am doing my field of life. OEMs also will get the source code open. They will also get the reference design applications which are already available in the Tizen store. And then they get it really easy for them to make a phone because they have all the ecosystem, all the applications that have been ready. And on top of that if they have some of the key applications which they want to protect and want to, for the users to feel them better and all then they have another way of actually packaging them with the phone. They will need native icons available, not unwordable, but rated in C's EFL because that part of the interface, that part of the middle end is very close to the hardware. So these are some of the advantages of that. Then another important part is that while if you see the penetration of Android and Apple OS and all, initially it was targeted for smartphone kind of devices the Tizen at the same time is targeting cameras, TVs, tablet PCs as well as the IVI segment. So India is very, very keen and aggressive on launching Tizen on the VQ website. So you will see after some time the dashboards in the car, many of them with Tizen and some of the companies will be launching with Tizen. Then Samsung has already launched a camera NS300 with Tizen. You can just have the review available on the net. And then smartphones is the focus of course. So all the OEMs who are talking about that now are focusing on smartphones. So basically what we are trying to do is that this platform will be a multi-device kind of a platform. And each device category has been taken into consideration while designing and developing the platform. What kind of UI, what kind of format, what kind of resolution, what kind of OS is needed. I mean the car may need a lower kind of OS, what kind of chipset, so those kind of, I mean things have been taken into consideration. And this slide is basically just trying to showcase that why it is probably not so easy for developers to get that much money on the Android. So one of the reasons I probably am attributing it to the kind of fragmentation that is happening on Android, that is basically that last point is trying to make it. But then once that gets into such a state where many OEMs come up and they start using the platform in the first place and there will be some kind of fragmentation which is unavoidable. But from the app store point of view if you can still manage and I mean restrict it to a single kind of app store and also we are still seeing that at least the app level of fragmentation can still be there. Not that the same version of application is developed by another developer next day and it keeps it free on another app store and you have access to that as well. So kind of things probably will be taken care of. I mean this is basically just trying to tell that okay there are only two ecosystems available as of today. I mean they are controlling almost 86 to 90, I mean almost the entire market is captured by them. So there probably is a need and there is also an appetite for any other operating system to come probably they should be able to differentiate themselves. So in that sense and all Samsung has also welcomed Firefox and Chrome coming into this picture because all of them at the end are trying to say that they will be well focused and all. So that's why probably Kaizen's plan will go this way. Okay so I mean most of it we have already covered here and every ecosystem or every platform will of course have these selling points and all that what we want to do for our developer and how we want to help him monetize that these applications to begin with. And by the way I just wanted to highlight here and there is a Kaizen app contest going on currently. There is a Kaizen app contest going on currently for around 4 million dollars. Are you calling? Yeah. Okay so I mean you will be calling that specifically if you are interested. Next. So this is basically a key point here specifically that Kaizen store will be monitored and limited by Kaizen association. So if anybody feels that okay tomorrow Samsung may decide which kind of application will go, which kind of application will get structured and all. That will not be Samsung that entails the decision and all that will be Kaizen association. So the entire framework of Kaizen development is done and run by Linus Foundation and Kaizen association. So it's not that okay Samsung 10 tomorrow says that yeah this is my way and you have to follow it. So that is actually the primary part. And the second part I want to highlight here is that we know that one of the biggest challenges we had when we were having the Bada app store was that developers had to I mean there was a long process of actually going through the certification. But Kaizen association itself is guaranteeing three days. They are guaranteeing that three days of certification for an app the moment you actually load it into the app store will be going away. That means within three days your application can see that it can be available for download and in the service office. Yeah I mean this is what that particular site is coming. So the validation is in three days is what we will be warrantying. And of course another big issue is in terms of billing and I am sure that Jandu will be covering that in detail I know. What kind of billing interfaces we have, credit card, operator in-app and so on. So at the end of the day of course it's again I mean how easy it is for I mean you to get money out of it how will we actually end the application or how applications are discovered in the first place. So all that ecosystem is already available as of now. So when we launch the first device by November and first week of December at all. So you will get a feel of how Samsung phone will actually look like and then probably you may get more interested in involving to develop that application specifically. So that more or less out of my presentation if you have any specific question or any doubt specifically I will be glad to answer that. Is there any device that can purchase applications from the time scope or is that yet to come? So this is the article. Yeah, so as of now as I said the first size of device is going to come in December time frame. But at the same time we had I mean whenever we have new developer conferences I mean we had one in May in San Francisco and there will be another in October again in USA now we didn't have anyone as of now in India. So there for all the participants and all we have actually given them one-one device. So where they can actually come and write their applications. But at the same time I think Chantu will be able to help you I mean he will cover it separately if he can answer it now itself. I mean if he wants some access and is it possible through RTL or something like that. Yes, the application for the development purpose we can help you with something called RTL. You can build your application using SDK. You can test the application on the device connected to the internet. So I will be showing the demo of that how to connect up. So it covers 70% of the applications which are coming up. But if you have application which requires a hardware which or like it requires Ixopome and other things which you cannot do it remotely then please talk to me we will try to help you maybe we will like the device and those kind of things we try to help you. Then like an application they purchase it and wait for the market. You are right for that. But what is his answer rather if you want to experience how an application can be developed with Tizen. And one is that you use the simulator emulator which is available with SDK. You still do not have the device and you still want to see how it actually looks on the device. So we have an RTL interface available where you won't think you can exactly test it, verify and see how you are able to feel everything runs. And then obviously Tizen Store will soon actually start accepting the application because the entire concept of having the developer conference is and then giving devices is that we need applications to come onto the App Store. Yes, the point is then they will go for the sale only when the first device will be available by then. Now for developing purpose Tizen Associates will have a separate developer units that is called an Apple devices. You can just throw that out of the site. So they will be based on the device how well you will keep this in mind. So I added to the political question about the device availability and the revenue generation which is more towards the monetization aspect. So see Android covers say 60-70% of the market in the slide but the revenue aspect is not the same. It's a mass market and then there's a new market. So generation of that is a little bit different in terms of generating money. Next up we have Shantu who is senior technical manager with developer relations for Samsung Media and he will be taking us through the Tizen remote testing.