 I'm going to talk about micro G like what it is now and what we're going to do with it in the next months, two years. So first of all, I wanted to know, like, who of you actually knows what micro G is and who doesn't. So is it like, okay, so it's majority knows some like these one sentence thing that I always use to explain to people is that it's just framework to make the. Everything running on your Android device. So all applications that you use to run on Android will also run with micro G. That's the idea. What you can do with micro G and all of this obviously without Google. So we don't want to have Google always involved with everything. And if we can get rid of it, then that's a good thing. And that's what micro G is about. So I'm kind of starting with with Android first because I have to. So, you know, that Android is supposedly to be open source. Google always promoting it is as open source. What they mean is there's the Android open source project. And it opens up a project. It's kind of a completely open source operating system based on the Linux kernel providing like all the services, a framework and SDK and so on. It's like everything you need to have a full operating system and implementing like applications on top of it. So it is technically something that completely open source. But if you talk about about Android, then you usually are not talking about the Android open source project. You're talking about something that at something on top of AOSP, which is a few additional SDK functions and some subsets that run in the background. And a lot of end user applications like Google Maps, all the stuff that you're used to or some are used to from a normal Android smartphone is not part of the AOSP and is also not open source. So that's why this saying that Android is open source that is used by Google a lot is just it's just not like reflecting the reality of what people understand. And there's a term of Android. It's just that they can't claim it because it is the Android open source project which is open source. OK, so this kind of the things that you get in there in the in the in the Android stuff specifically from Google. So I'm only focusing on the Google parts because usually if you buy a phone from whatever manufacturer, there's also stuff from other companies in there like the manufacturer, the chipset manufacturer and so on. So it's various components. But Google has this kind of set of things that they put on every every phone basically, even the non Google phones. I mean, Google always already has their own phones and they put more stuff even on those. But this is what goes on basically every Android smartphone and it's like two additional SDK functionalities, which is the Widevine DRM system and application in the library so that applications can embed maps. And they also provide two services or two main services. They provide a lot more, which nobody really cares. So don't focus on it here. And that is one thing that's called the poor man GPS, which is locating your device based on on Wi-Fi or GSM mobile networks or Bluetooth speakers or whatever. So that's the one service which always uses Google obviously for for locating you. And the other one is what's called Google Play Services on the end user side. And if you talk to a vendor that will always Google call it Google mobile services because that's what they are buying from Google. It's just Google Play Services to the end user. And that's a thing providing a ton of features nowadays, which is a new version of the maps component, but also like push notifications and even include security updates for the TLS library of Android. So if you don't have that, you actually get to use old TLS libraries, which tend to have security issues. So even security updates are provided only through this proprietary channel. And many more. So it would have been too much slides to mention all of these features. So I just go with this important ones. So that's what Google stuff is in the Android system. And that's where MicroG basically comes in. So we want to kind of implement all of these features that are from Google. And we have the maps, the original first version of the maps library, which is feature complete and runs pretty fine. And we want to make it like in a way that all the applications can use it, right? So we don't want to restrict in any way. And we don't want the applications to be modified in first place to be able to use it. We want everything to just run directly. And we even include the Google applications. So on top of the, as mentioned, we have the service and framework. And we have the end user applications like Google Mail. And we even want the Google Mail applications to run because there are users that need Google Mail because they have Google Mail for their work environment or whatever. So they should still be able to use as much free software as possible. And that's when we want to make sure that we can have the services running, which is always running in the background to be fully free software, but still on top they can then decide to, I want to compromise there for whatever reason. So that's why it's possible to run all the Google applications with MicroG. But also another important topic, especially discussion about environment and so on, as these Google services always running in the background, do tracking. They do for advertisement and so on. And that's always consuming some battery, which is completely wasted. I mean, that you have to charge your phone more often and whatever. So it's not like really they are always with the best intention for the users. They are doing what they want to do. So yeah, so that's also like an advantage we have with MicroG. We can just get rid of all of this because we don't implement the tracking, we don't implement advertisements. I mentioned we have already the maps in a fully functional thing. Actually, since 2016, we have finished with that. Only the first version of the Maps library because Google then decided, let's do another one. And that other one was more complicated to realize. So it's mostly finished by now, but it's working on a completely technical different base and so on. So it was kind of a lot of work to get this done. And there's no part of the play services as well. And the other thing that we also have working as fully working is the location based on Wi-Fi. So we kind of build up a community of Wi-Fi and GSM location information providers like OpenData or CloseData because OpenData quality is not always as good as needed especially in this area because you can, unfortunately for privacy reasons, it's not allowed to build up a Wi-Fi network database without the Wi-Fi, a public Wi-Fi database without the Wi-Fi owner agreeing to it because the MAC address of a Wi-Fi is considered private information. So that's why there's closed databases and there's no open database. There's an open database, but it's very low data quality because the device owner has to agree, which most don't do. Fortunately, nowadays there is a project by Mozilla to collect these even though the database is closed. It's an open API and so on. So that's a good thing. And we also support using this database. And the other thing is the Google Play Services which I already mentioned which contains tons of features and which because it's so much features it's not completely implemented everything of it. So we implement the important parts which the new maps versions I mentioned, the push notifications which many apps like especially messaging applications need to use like WhatsApp and so on which some people still want to use on top of their mostly free software phone. And that's why we kind of go with the most important features there but there's tons of features that we don't implement well aware of it being there but at least most applications do work and it's kind of the main thing. And we're kind of constantly improving adding more features. So, yeah, we can improve on that. And yes, so I want to give a bit insight into the future what we want to do. So, but I'm probably going to go a bit fast through it because I don't have so much time. So it's one thing about MicroG is it's basically me doing it and this little outside contributions and it's because it's a huge code base and a rather complex project and I want to make it easier for others to contribute. And I actually would want everyone who wants to just look into it and try things out because this can be very easy to fix actually and it's just people are kind of afraid and I want to make it easier for them to find where is the code that is relevant for them. And there's other thing about not being easy is the installation process. So, especially in the past installation was rather complex. Nowadays there's a great community effort of doing a linear choice fork which is MicroG pre-installed. So it's became way easier for the first installation but it still needs some set up progress. It's not that easy to manage. So you need to know what to do. There's instructions for it or it could be way easier as well. And skipping through this. I also wanted to talk about some not technical things here because in this audience it makes sense to me. And one of the things I want to do is regulations and there's been some regulations regarding Android in the last two years basically. Last year the European Commission decided that Google is not allowed to force the manufacturers, to force Google to force the manufacturers that they must like always get the full set of Google services and applications and tools. So before it was like the manufacturers had to say we are using all of your stuff or using nothing and there was no middle ground and the European Commission said it's not allowed anymore. So the idea was good but nowadays they are just licensing out the services part that everyone wants to need for paid and if you now install on top all the Google stuff like applications and so on then you get it for free. So it's kind of like manufacturers are not really making use of this new freedom because it's more expensive for them. And the other thing is which came out this year is the default of Android always the search engine and the browser being Google search engine and Google Chrome which also the European Commission found is not a good thing and now we get our nice browser choice back on Android which apparently will look like this. Also we get browser choice and search engine choice like we had in Windows but there's an issue with that and that's basically you have to pay as a browser window or search engine to get on that list. So Google is kind of making a public auction so that you can be on the list. Only five search engines or browsers would be displayed. So they're even making money now out of this regulation from the commission. So it's kind of like backfiring here. I also want to talk about industry. So there's some recent movements especially from manufacturers so you probably all heard about Huawei not being allowed to sell phones with Google anymore so they are not selling phones right now in Europe because they feel that they cannot sell a product that isn't compatible with most applications and with other Google services they cannot be compatible. So that's why they are not selling right now and that's kind of also giving all the other manufacturers a sign that there may be a problem with them so much relying on licensing stuff from Google and actually that stuff not being open source. So there's multiple manufacturers now looking into getting rid of it and also trying out MicroG. Sometimes they talk to me and sometimes they don't so if there's a funny email or you probably cannot read it but was contacted by some Android related news website and they told me we have this thing that we got from one of our like some journalists find out that there's a device apparently built a specific Android built for MicroG for this device and did you know about anything about it and in that case I didn't even know about it at that point. So that's that's funny because everyone just wants to write me emails about anything with MicroG and then I get these nice emails. So yeah that's like something that's being being done recently and I really really think there's something going to be forward there and it's also like some other industry people that are interested some companies that are selling specific special versions of Android that are modified for government or company use so they want to get have special version of Android for the employees smartphones so they can be private and so on and they are also looking into MicroG because you know maybe as a government I don't want everything to be shared with Google and there's also something about secure containers or work environments where on top of your smartphones you install the secure container where you can install apps inside a container which is then like send box from the rest of the operating system and you also don't probably want don't want like Google in this container so yeah there's like in this area there's kind of like a movement there and I'm very confident that there's actually in in the next year we'll see quite some public industry usage of MicroG actually so that's a bright future. All right, that's it.