 Hi, everyone. I'm Andy. Obviously, I'm working on the Android app. And like Björn, I also want to talk to you about how you can contribute to the app's development, which basically means I'm going to talk a little bit about the process. And I'm also going to have some numbers to click with this. Yeah. First, why would you even want to join development? We had our first release on the 12th of June. We're growing pretty fast. So we got, well, I sent these slides to yours, I think, on Thursday evening. So they're already outdated. We are at more than 17,000 active users now. I just checked it on my phone. And I'm a little bit lying. I say we've got four months and four feature releases. That's at this very moment, not true. So I'm happy to announce that today, within a couple of hours, we're going to release 1.3.0. The next feature release, which is going to bring a lot of new stuff to you, like filtering and also bug fixes, the way we handle the Javu files. And we've got a pretty good rating right now. It's 4.6. Well, it's actually nearly 4.7, but I just cut after the first digit. So that's three things I value. It's the people. So you contribute to an app that's already widespread. I care about execution. That's a good thing here. We already could do four feature releases. So it's basically a new release each month. We didn't do one in August because everybody from us was on vacation. That's basically the reason why we didn't do it in August, what we do today. And we're pretty successful. So you're able to join a team, also get new experience in how to develop apps, how to deal with an app that's quite popular on the market. So it's basically a win-win for everybody. So now you have an idea and you want to go to get it launched. Unfortunately, it's not just one step. You have an idea, boom, it's on your phone. We still have to do some steps in between. We tried to keep it lean. We're still focusing on quality when it comes to the app, but not wanting you to have to wait for new features for like half a year or even a year. So basically five steps. To not get you frustrated, the easiest thing is to just start up the discussion, could be on the forum, and at some point move to JIT Hub. Open an issue, have a discussion, then we're going to label it approved at some point. That's a good thing. So, you know, it will be implemented at some point. Then it'll move to to develop, which means that's going to be one thing. We're going to develop in the near, near future, probably the next release or the release afterwards. Then we start opening a pull request or whoever does. Many is going to be in developing. That basically tells you that it's still been worked, people are still working on it, and it's not done yet. So it's something in between, and then we're going to label it to review. That's basically done by the contributor, which has its feature complete from a development perspective, but nobody has taken a look at it. So one quality measure we then take is doing a review, which is enforced. So you can't merge any change to our master branch without having a review from at least one person who's in a maintainer list, so they have to check your code changes. If that is done and everything works out fine, it's going to be labeled to release. It's also going to be assigned to a milestone, so you have a pretty good idea when you will get it on your phone. So now you want to do a contribution code wise. So you simply, you can either fork or you already have right access on our repository. So basically open a new feature branch, do your development, and already open a pull request, have a discussion about changes, get some help from the community. What I usually do, I just post screenshots and ask the complete designers list to give me some feedback, or even if I have a problem, if I don't know how to solve it from a user experience or UI perspective. I should talk to Jan, Mario, one of the other guys. When I think I'm done, I simply label it to code review. Then usually Tobias does my code reviews. And it's also a trigger point. As soon as something gets labeled to review, which means feature complete, it's going to be pushed to a better app, which is distributed via asteroid. So if everything runs smoothly, the code review is done. I did all the changes Tobias demands me to do. We also have the CI builds. If they are turned out green, yay, all tests are fine. We simply merge it. Then it's back on the master. And if we got all the features we're planned for and you release to this stage, we simply going to release it. So yay, ship it. So that's what we're going to do today. And like Björn also said, you don't have to be able to code or even want to code to contribute to our app or any part of the ecosystem of NextCloud. You can either help us with translations. Right now we're supporting 32 languages. But for this release, we only have five at the complete stage. And the others are pretty close. We're talking about 89% done of the translations, but we're still missing the 2%. So you don't have to have any IT background, know how to code or stuff like that. You don't have to have any idea about Android itself. You can simply translate text and this is going to help us. It's going to help us a lot. You can join the designer team. Like everyone, everybody's always welcome to help. There's also speed subs things. You can advertise the app with your friends. It's open source. It's free on Android and on Google Play. You can trust drive new releases. We've got several channels. We do release candidates. That gives you a good impression of what's going to be the next stable. You can test it on your environments. Give us feedback so we can do late-minute fixes, even though every release candidate or the release candidates of the next release have to survive in the wild for two weeks. Else we're not going to do a stable release. Yeah, that's basically it. Report issues. So if there's anything you're missing in the app, a feature request or if you have any bug which really enacts you, just tell us. We're going to have a discussion and I'm sure we're still able to fix it and resolve any matter. So thank you.