 Hello everyone. My name is Marcel and I'm here to tell the story of the audio player. I started around one year ago when I was searching for a streaming solution for my kids to have them playing their music files from a shared library on the tablets. And after searching a lot, I started with a fork of an old app called mp3 player which was pretty abandoned and not really operating back then. After getting it up and running and fixing the most basic issues, I decided to put it up to the app store to make it usable for other users. Then the story started. One year later we had quite a lot of feature releases being at version 2 already and with the current version over 19,000 downloads made us pretty happy and was a little bit more success and then also corresponding work than we had expected at the beginning. The audio player itself, all the features you would expect from an audio player, all the major MIME types, mp3, flag, whatever you need. Standard features like ID3 tagging, media folders, a lot of core next-cloud integration like integrating into the share dialogs. We have the share player. It's integrated into the files app that you can play the audio files directly with the one click from the files. Search integration, favorite integration, smart playlists, everything you would expect here and we even managed to get it maintained in seven languages and we put up quite some documentation in the wiki also. To get there was quite some challenge because we are only like a two-man team. It's myself doing all the development and then Thomas, Thomas Marx was the specialist for everything that comes to languages, grammar, grammatics and especially testing. We are really non-professional developers. We are only doing this as a hobby. So we really had to fight to get the app that far. Some of the main issues were, for example, the documentation. If you look at the API documentation, as far as I know, the next cloud still doesn't have one. I'm still using the own cloud one. The documentation or the community developer support was sometimes a little bit, could have been better. If you're a beginner, the documentation like the demo apps are there, but it's hard to get up and start it if you're really non-professional developers. And then also if you have to deliver apps to several releases of own cloud, next cloud, different versions and then all these depreciations which come from year to year made us quite some headache. It gave us a lot of trying error, a lot of patience in the IRC, next cloud dev channel or in the forum. In this context, some special thanks to Bernhard from the news app. He had some very patient support for a lot of, let's say beginner questions and he helped us a lot. And the third source to get everything running is our other GitHub apps to serve there and search how they did it. So over the year, we ended up with around a thousand commits, only mostly by two of us to get the app up and running. The only chance to deliver the app in this scale was to focus then on a very detailed testing strategy. We have currently two pies and one web hosting packages to operate for ourselves different instances from next cloud, on cloud, current version, previous version, plus some betas and then all the database combinations. So currently whatever we fix, whatever release in a new version, we tested across six test instances to have all the possibilities covered as good as possible for the user. We documented test cases which we managed via the GitHub project, which is very helpful here and with this precision, we managed to keep the tickets count to around 10 for a new feature release which saved us a lot of work afterwards. Where do we want to go? One of the main features that we are currently working on is the integration of streams also. We can include web streams like web radios also in the audio player. So perhaps even then including playlists files like these M3U files, code cleanup, better handling of huge libraries. This is always a task with users of 20,000 and more audio files. We did quite some improvements there for the performance, packet and Java front-end. We still want to tweak a little bit more. And then perhaps some more integration into other apps like the notifications or perhaps a player integration into the dashboard app. We have to see what we can find out here. And to close this, a little request for support. We have two issues where we are really fighting for a long time and perhaps someone here in the audience could contact us later for some support here. We still did not manage to connect TrantFX to our repo. Somehow we were not possible. I'd like to get some support here. We are still searching for a CSS guru. We have one ticket still open for almost half a year already where I can't figure out how to solve some certain position tagging CSS issue. If someone could volunteer here to support on these two things, they would be very happy. Thank you, Andes.