 Hi, everyone. Can everyone hear me fine in the back? I hope it's audible. Is it audible at the back? Okay. My name is Leena. I'm talking about MDM. MDM is Mobile Device Management. Just before I start, I just want to know about how much familiarity is there in the audience about MDM. So, quick show of hands. How many of you are aware or familiar with MDM? Okay. Very few. How many of you have used any of the MDM tools? Okay. How many of you have created your own MDM solutions? Okay. So, I hope this will really help you to build some MDM solutions. So, my talk is two parts. First, I'll give a quick overview of MDM solution. MDM, what it is and why it is being used, and then I'm switching on to my experience with MDM while working with multiple products. So, let's start. So, MDM is, as I mentioned, it is centrally managing devices from a single location. It should not be as complicated as this. So, when you say it's centrally managed solution, this is the kind of picture that you get. So, it should not be like that. It has to be something as simple as this. And it has to be simple. It has to be in-duty. And this entire talk is about how we can create and what are the options available. And what did I learn while doing this and some of the failures too? I hope I'll share some of the failures we had so that you guys don't have to make the same mistake. So, MDM actually started off as with the enterprises, especially with the big enterprises, with the concept called enterprise mobility management, where they allow their staff to use their own devices within the premises by ensuring that the certain security policies that they have in the enterprise are being enabled on the devices that they bring into the premise, such as password policies or PIN policies, or even encryption of certain content, allowing the content to be used only within the premises. But in the recent past, especially with the Android and devices, generally taking a lot of influence on different businesses, you've seen enterprises, businesses using devices where there are a lot of field staff. For example, delivery boys, where there are a lot of delivery staff, MDM is a solution that they will need to control these devices. And it can also be where devices are used for data collection, where they go into the field, collect data, and then use it. So this kind of devices has to be managed remotely because these people will be on the field almost all the time. Another use case it's being used is where it is, where devices are being used as information chaos, such as POS systems or where it is streaming content. And that is another place where MDM is becoming useful nowadays. So another term that you usually hear in the MDM world is BYOD, that is bring your own device. And the fragmented nature of Android is complicated everywhere and it is not different in MDM because we have to allow the control and that kind of control has to be working across all kinds of versions, all kinds of manufacturers across. And this is a graph that shows what kind of fragmentation is existing in Android. And this is very, very challenging in the MDM world. So now let's look at some of the existing solutions. These are big players of MDM solutions. Almost all of them are, have shattered RR in the area of enterprise mobility. And either they have been acquired by bigger companies. For example, AirWatch was acquired by VMware. And similarly, other companies have been acquired by bigger enterprises. And these are usually targeted at the enterprise mobility space, not at the space where devices are used to control for devices for controlling, or MDM solutions for controlling devices used by the field staff or for information task. Now, in a fourth theory, let's go to some stories, especially the stories that I have to share with my experience with MDM. For that, let's go to Sabaganda. Sabaganda is a village in Gujarat. This, if you search for Sabaganda, it's a district in Gujarat. If you search for Sabaganda, you see it is famous for Wi-Fi-enabled villages. And it's not completely all, or not all villages are Wi-Fi controlled, but there are quite a few villages which has a lot of Wi-Fi coverage. And the beauty of another interesting thing that is happening there is that they have a lot of devices, Android devices, being used for data collection, so especially in the healthcare department. So there are quite a few IS officers who are tech savvy, who are the district, who are holding the position of district development officers, along with the tech savvy doctors, they have developed apps and use that for collecting data, especially in the health industry and across other departments too. So what kind of data they're collecting? They collect data about the health data, health information about the villages, especially the pregnant women and children to improve their health and the child mortality ratio. And they also keep track of their immunization schedule so that on the day when the immunization, that they were vaccinations are due, they go to villages, take them to the health center, make sure that they get the correct vaccination and then make them aware about immunization and giving them enough data about how to make them aware about immunization and importance of vaccination. And for this, so they have developed apps for all this and there are around 1000 devices in the field, especially around 600 of them being used by healthcare officers and they carry this to the villages for collecting all these data. So let's look at their challenges, some of their challenges. Connectivity is still a challenge that because of that we all have, even if we are not in village. But apart from that, some of their challenges are keeping these apps, what they have in their devices, up to date all the time, making sure that the content that they have on the device that they use for increasing the awareness with, it's not in sleeping. Okay, so, and apart from pushing content and app, another major challenge they have is they don't have a registry of the devices. They don't know who uses these devices, where it is located and for what kind of data collection is happening on these devices. And then let's look at some of the solution that we spoke about in a couple of slides back and how it will fit into solving their problem. So like I mentioned, almost all the solutions such as AirWatch or our mobile iron are targeted at bigger enterprises and the cost is one of the biggest concern that they have for using any of these apps. So, and you don't need 80% of what they provide. You need only certain percentage of the features that these solutions provide. But you also may need changes to those kind of features and you will not get it because they are targeted at certain certain kind of customers. So, so one of the IAS officer in Sabar Gandhi, his name is Nagarajan, he approached us. So I work for this company called Multunus and so he approached us whether we can build a solution for them. And they have been other customers who have been approaching us to ask similar questions, not exactly the same, but similar questions. So that is when we started off thinking about open source. And so we've started building an open source solution which contains the very bare minimum of MDM solution. Right now it only contains device tracking. You can register a device in the app and then you push apps to those devices. And that's all right now. And it's in the process of deployment in Sabar Gandhi and it takes time because it has to reach all the thousand devices. So in the next few weeks we'll know how it is being used and what kind of problem they still have and we'll add more features to the system once the deployment cycle is over. So we need all of your help. I'm talking in this conference because this is an Android conference and this is an open source solution. So we need a lot of help from you guys to help us move this forward. The vision of this particular, this eye of his officers and the under helping hands he has is to take it outside Sabar Gandhi outside Gujarat and take it across India to help us automate and use devices for more efficient and efficiency, effectiveness. And that can't happen without all of your help. So please, please give us suggestions. If you already know how to build MDM solution, give us suggestions, we can improve the solution. And or if you want to start, let's speak in GitHub and then we can collaborate on it. So that's about one story and let's move to another story. This is a different story. This is not related to open source. This is about information chaos. So we spoke about how MDM solution is required for free staff. Now let's look at the other example. This is in US, but again in the health industry. So you might have seen in almost all the clinics, the TVs being played with content, sometimes with very informative content about health and other things. And that's very common in India also. But this particular customer with whom we work for, they went next step, what they did was they used tablets instead of TVs to show content, informative content to the patients. So the advantage with tablets are they can replay this, they can interact with the tablet, they can even share those content with either themselves or with their friends so that they can watch it again. So this is a case where the device is installed and there's hardly any interaction with the device once it's installed and you have to control it from a remote location. And so the standard challenges that we spoke about, app updates, content updates. Apart from that, there are a couple of more. That is this particular app which is streaming the content has to be running all the time. It has to be on the front end, front line. And this, depending on the hours of the clinic, the app, the device has to be switched off so that we don't drain the battery a lot. And especially on whole days, it doesn't have to be running all the time. And these kind of things has to be remotely configured. And apart from this, we also had a very interesting challenge with this, that is playing Adobe Flash videos. So that was a time when, I think I have five more minutes. Okay, that's a time when Adobe removed Flash app from the Play Store and Android stopped supporting for that. So luckily we found that we were able to find the APK and then we were able to play Flash ads. But the problem is with, so in the last talk he mentioned about easiness of onboarding. So when we are setting up a device, we have to make sure that all the required apps has to be installed on the device. So that is when we went with the custom ROM solution for MDM. So what this custom ROM helped us was to remove all the bloatwares, install all the required apps, including the Flash apps into the ROM, and also configure certain stuff, like setting up of certain volume level or say certain Wi-Fi settings or screen timeout settings, et cetera, et cetera in the ROM itself, so that the entire thing is automated. So the custom ROM was possible in our case because we were targeting only one device. The BYOD was not there. If it was there, all of you know that shouldn't have been a solution at all. And it also allowed us to install apps as system apps. Systems apps have special permission and it cannot be installed by the users. So any accidental uninstall of the apps also could have been, was avoided by using system apps. So all this was possible with custom ROM, but custom ROM, like you all know, has its own cons, that is it voids the warranty, but the customer whom we worked with they were completely fine with that. And it also, you can imagine at times you may break the device and then you're gone. You can't get it back. So how much more time I have? So my idea was to cover that what is the landscape of MDM and I explain different use cases with my experience where I have seen MDM being used. And so now let's go back to the initial thing that we started about security. So what about security? So security can be provided to an extent by device management API. That's a special type of API provided by Android which allows you to set up certain policies on the device, but it requires specific special permission from the user. The user has to accept that this particular app can be installed. This is different than the normal manifest permissions that you give in your app. And so that's an area to explore if you need to enable certain policies on policies. Those policies can be password policies or encryption policies for certain area in your storage. And lastly, about Android for Work. That's a very recent player in this entire game. This is based on Lollipop's multiple profile concept. Now starting from Lollipop, you can have multiple profiles in your device and you can switch between those. And this allows, if you're a Google apps user or your enterprise users, Google apps, then you can use Android for Work to enable device management and also with the possibility of BYOD. That is, it can work on any device. And if the device is not running on Lollipop, you can download a specific app and install. But this is still on the early stage. It's not completely open. It's available only on request basis. But something to watch out for, this might help enterprises a lot to manage devices remotely. And that's pretty much about MDM. So what did we learn by building it? We learned that we can use standard APIs to build a MDM solution, very bare-bound, not a very complicated one. And that is what most of the enterprises want. And onboarding has to be very smooth as much as possible, automate the things. And at times, you can look at options like custom ROM, if that's the way to take. But custom ROM also comes with its own baggage. So be careful when you are choosing that. And we have big believers in continuous delivery. So release early, release often. Use features, switches to enable disabled feature and get feedback and change your approach or change your plans, depending upon how do you get the feedback on. And lastly, about having a good monitoring system. We literally paid the price for it, not having enough of it. We had a big failure with that. It's very important in case of an MDM solution, because once you hardly have any access to the device. And the business revenue mostly depends on the device. So if you lose track, then getting it back is very, very complicated. That's another story I can talk in some other. We had a big failure with that, that I can talk in some other talk. And so I just want to conclude with asking for you for the contributions. So please, please get in touch with me if you have any further questions. I'll be available here. And this is my social aid. Thank you. I don't think we'll have any time for Q&A. So if any questions, you can take it offline. Am I audible enough? So just one, give me a minute, because this is a hardware demo, and things always go wrong. So I just, OK, so a quick show of hands before I start. How many of you have heard of beacons? OK, so a lot, right? So beacons, Eddystone, physical web, some one of those keywords.