 So you already said it, I'm Andy, I'm a community member since the start of NextCloud, also worked on the app before we did the fork, and we're out for like slightly more than a year. So I want to share our experiences, how the app's doing, how we adapted to the success of the app. So, well, it's been 14 months to date, and we did around about 11 stable releases. Stable release to me means it's either a bug fix release, minor version, or even a major version. So this is just stable releases. We also do nightly builds and whatever, but this is what we provide to the user as stable versions. The adoption rate is pretty nice, it's 78%, which is slightly more than 100,000 users. So that's not downloads, it's actually active installations on devices. The download number is rather about 130,000. So within the last four weeks, we grow by 12,000 users per month, still actively using the app. And this number keeps growing. So last year we started with about 6,000, that's just doubled. Also for the ratings, we're still pretty successful, it's 4.2 now, which is still pretty good for an app on the App Store in Google. So we did quite a lot of progress in different areas. Like I already mentioned, now we have 11 releases, last year at that time we just had four. So we do this quite regularly. The ratings went a little down, but that's also due to big numbers. If you know math, the higher the amount of ratings grows, the more likely it is you end up with a 4.1 or 4.0, so it's impossible to have a five-star rating, like on average. But to be honest, we also had some problems with the auto upload function, that'll change with our next release. So I'm pretty confident that also the rating will go up again. The number of commits grew quite a bit, so that's like more than a third of new code commit-wise added to the app. We put a lot of efforts into, well, we use statical code analysis tools to get the better maintainability of the code base, so-called technical depth, the amount of time we would need to spend to fix all issues within the code that might make it instable. We were able to get that down from like over a day to, well, this number is already outdated since last week, so it's less than 11 hours now. We fixed more than a couple of hundred issues or tickets, so the amount of pull requests or bugs or feature requests we did within this year grew from like nearly 100 to over 600, that's also due to the fact that now we get two paid developers who work for the next cloud as a company, so we can put way more efforts into the app development, and also the amount of contributors grew quite a bit. To me, that's one reason for it, that Frank decided that we don't have a CLA, so you don't have to sign it that allows the barrier to actually contribute codes. We had over 10 new contributions taking part in the Hacktoberfest last year in October, so what do you do now? We grow by like 2,000 people a month more, by month, by month, by month. You've got over 100,000 people who actively use this app, so if you hit a buck, the amount of people who may or may not be annoyed by it keeps growing, you need to keep the app more stable by each release since the amount of people you might hurt gets bigger, so what do you do? In the beginning last year, we just had a small tool set. We used TransFX, which is still in use all over the ecosystem to do translations. We started with Travis, since that was a natural fit if you use GitHub. They used LGTM, which is the acronym for Looks Good to Me, to enforce code reviews, and we really took the time to do manual development builds, to push that out to users who were eager to try new features and give us feedback, and all that is time-consuming, the amount of users is growing, so you just don't have the time to do that, so you start to do more automation and use better tools. So we moved to Drone, which gives us a lot more freedom how we handle our builds. We still use TransFX, because that seems to work nicely, but for example, we now replaced the LGTM with Puller Proof. Puller Proof is also a nice online service with a lot of flexibility, so with Puller Proof, we now enforce two code reviews per feature, so at least two developers have to give you a thumbs up, and if it's flagged design, it also enforces a designer review. So we need a third approval, yay. We automated the dev build, so every night, all features that are flagged ready for dev will be auto-merged into another branch, creates a release, and push it to fDroid. We started using Codesy, which is a bunch of tools who run on every commit, on every branch, as soon as we push it to GitHub. Runs stuff for unused code, looks for stuff that's not error-prone, typical programming mistakes you can make, and lists it all up and enforces you to fix it, so the code can't get worse than it's been before. So if you build in a new warning, you can't merge this feature to a master branch, you need to fix it. So that's how we get a better code quality over time, and we also started to use Lint, which is a natural fit for Android, and also Tobias, who's also an Android developer on the team, enforces that you can't create new warnings or errors. It has to go down, or at least not go up. So we get a better maintainability of the software, simply over time. So what you can also expect in the near or further future, we're going to do more for testing, for automated testing, to make sure we don't have regression issues, start to do more for integration tests, get back to shorter release cycles. We used to do it like every four to six weeks. Now the newest release still is in development, which should come out during the next days, which will be a really big one. You're going to hear about that later on. Started to use more coverage reports to see how much of the code is covered by testing, use further tools for code analysis, and also get back to provide quicker app store feedback, because that's something that really helps with ratings. At least the next cloud users, they do change their rating if you fix stuff. And last but not least, over the year, over this first year, also the Android ecosystem in regards to next cloud grew quite a bit. These are just including the next cloud client, nine apps, but they're still far more where you can do contacts and calendar things with Daftroid. We've got several bookmark apps out there done by the community by third parties. We've got news readers, SMS backup, like if you get the text messages on your cell phone to get them to the server, notes apps. Passman is still in alpha to do password management. So also that keeps growing, and it's something we want to push. Tristan mentioned it for interoperability to, well, make these apps better integrated so they can work together, but still be independent. So thanks.