 Hi, so I'm Camilo and I was here like in our academy like two years ago And I was presenting the music player I was working on back then it was called babe then last year I came back because I Modified the player and now was before he was using kid widgets and Last year it was now using kid quit controls and then the story of the my project is when begins so this is a quick overview of The things I will talk about in this presentation So about the motivation of the project and the history What is the project? What is based on what are the parts of the project the current state the goals the plans the road map and There's no time for questions. We'll skip that and I will give you some info So I was as I was telling you and the project started with a music player that was called babe Then there was problem with the name, etc. And it was changed to babe Away as you want as you pleased to pronounce it Anyone's before using kid widgets, then it was moved to Kid quit controls and then it was eventually moved to use kirigami so that's kind of the history of the project and Then the motivation was to have an ecosystem but before that when I was working on weight I was Creating components and then I start working on another application That was called peaks and index and I noticed that was duplicating the word because it won't control I was using them babe. I was also using an index So I moved all these common controls to a single place and then that was called Maui kid so The motivation was to have an ecosystem to have time integration and to have a cohesive design between the applications There were 10 eventually the motivation on the gold was to work on Convergence because of kirigami and QQC too because then the music player and the other two applications Now we're working also on Android so the motivation is to have conversion cross platform multi-platform and That leads to have data that I think of between devices and also responsive design So this is like a timeline Then There is wave Then my wiki is born Then you get straight into my way project and Then just this year the whole money project was creating to the kitty and now it's part of the It's a community project So this implies some refactoring and transformation because before my wiki was like you a I was doing components of my wiki that were already available on kirigami so Now kitty my kid uses a lot of kirigami and just up from top of it specific components for the more applications So as I was telling you now the project isn't created on kitty and all the sources are The in band instance So what is the my project? So the my project? Essentially is a group of tools working together to achieve a multi-platform and converges environment the money project runs on Android and Linus depth steps and also on plasma mobile It is based on Qt quick contrast to kirigami also the Android PI and the kitty frameworks file Uses interfaces between Different libraries depending on the target system. So for example on linux. He uses the Kio Attica, etc. And Android uses the API So if we want to have my wiki running also on Windows, then we will have another interfaces Same for Mac on iOS, etc So the apps are being shipped by default On the distribution that is called nitrox. I don't know if you have heard of it and they are packet package as up images And a few apps are also going to be cheap on the plasma mobile images So basically this is like what is based on Now I'm gonna talk to you about the parts that Compone the my way project which are the applications the libraries the services the framework and the human interface guidelines And right now we have a applications We have picks that is the image and gallery viewer boom, that is a notes taking application and also it tries to work as a Spocket like you can collect links from the internet and The idea is to have all these applications to sync the data between Devices so if you have it on your Android phone the same that is going to be shown in your just a computer We also have commander that is a terminal emulator We have not that that is a simple text editor library that is a PDF viewer Dialer that is a contacts application way a music player and Index that is the file manager. These are some screenshots of the this index the file manager that means the application and the image viewer and These are the other applications So all these applications run on Android and also on plasma mobile We have a few libraries We have a library called lift up that essentially what does is allow us to sync data between devices using Right now we are using next cloud to do so so we have web that and CC that with that for syncing Files and CC that for syncing contacts and eventually also calendar We have also another library That is tagging that allows to share metadata tagging between applications. So if you have a tag in Index you can also see the attack be shown in picks also in wait, etc. So the services are Ready-made interfaces to the target system So it's very easy with Maui kit. They are framework to for example on Android Get an active notification to share the sharing dialogue To get the contacts from the Android PI same for Linux We also have the Maui style that we use on nitrox on Android and On plasma mobile and also on other distributions. We use the default style. That will be there one from plasma We have the FM that is file management tools the interfaces we kill for Linux and We have a simple implementation on Android We also have a store They allow this application to have content to get content from the stores and it is based on Attica both for Android and And finally we have an editor. There's a simple text editor and it's a backend Right now. We were working on how to see using that highlighter to work also on Android and the framework the framework is basically Maui kit which Is the composition of all these UI controls and Those those controls follow them how we have the human interface guidelines And we also have templated and abstract classes So basically when the project was being curated there was this question of why to have another Framework when there already was Kirigami and Basically the answer was always the Maui kid is a specialization of Kirigami instead of Being why proper purpose is very specific So it introduces extra components and tools to quickly clear to create Maui apps So we might keep you create Maui apps. So the current state So that All the applications except the terminal emulator are running on Android plus mobile and Linux For release candidate there is already index the firm manager picks and the music player way For beta is dialer There is not a there is boo and commander in full alpha is library All of the applications are working as expected. Just some are missing some features This is an screenshot of the fire manager running on desktop and on Android. This is actually a screenshot so the goals for the project are To work in convergence We really want to have a single application for if you're in poll index to be powerful enough to be run on desktops And also on your phone. So instead of having to have dolphin just running on On your desktop computer and our solution running on your phone. We want to have a single one We also have Want to have consistency in our ecosystem And I think that is based a lot on how we're gonna work on a human interface guidelines We have to have we want to have time integration between the applications and the underlying system And we want to keep working on class in cross-platform not only on Android and Linux, but maybe expand to Windows All right, and finally For as a bit important the design to have a smooth and cohesive Look and feel and this is like a long-term plans or something that is already in discussion And we want to work on a launcher in a shell that works for our target platforms So you will work for Android for plasma mobile and desktop the same Launcher in jail. We also be working on refining our human interface guidelines. We want to work for that on the integration with the kitty frameworks file libraries and Find ways to make the project more available to the users for the users to play with it because right now the Degenerated APK packages are not available on any store. They are like sometimes pushed to a g-hop repository So this is the roadmap for like a Near future as we will make in official releases for the applications. They are ready a With the new polishing the syncing services to make it as reliable as possible And we will continue contributing to upstream libraries use by Marie like Kirigami And write the documentation There's no time for question So the information and there will be two both sessions There's first one is that the two act tomorrow the first one is general about the Maori project and It's a general overview of the project Where we will discuss about the UI framework that is my we keep the libraries the services and the apps And we want to have input from the community about the goals the roadmap and the future plans And also discuss its place inside the key community and the second one is just After it and it's a specific about the Maori kid and the Maori high So if you want to join us, you're welcome and If you want to Join us on telegram we have this group where I usually share APK packages so you can test the applications and and for news we have these medium publication Under there were under it. There is a lot of Maori Black posts and that is the main web page of the project that are the Kitty in band instance repository links and Finally, I will be tomorrow in a table around here showing the applications running on plasma mobile on some different Android Screen-formed factors phones and also on the desk if you want to check the applications out tomorrow And that's it. Thank you