 So, I'm here to talk to you for a bit about open source fitness apps, namely Vega, Fila, and how we're creating an exercise wiki. Before I get into that, I'd first like to define what is actually a fitness app. Well, a fitness app, that's a broad term of broad category of apps that covers a wide range of physical activities for people with a wide range of expertise with varying demographics, but what brings all of these different apps together is they all help you improve your physical fitness. Unfortunately, what's also very common with these apps is that they're oftentimes proprietary, which means that you don't really have full control over your data or over your habits, over what's running on your computer or phone. And the problem with that is, let's walk through a scenario. Let's say you install this app, you build your habits, you use it to track your walking or cycling, running every day. You build up a lot of data, you track your progress, but then suddenly it is shut down. And then what do you do? Well, you have to find a different app, you have to completely change your habits because you can't really use the app that you've been used to anymore. You have to hope that the alternative allows you to import data from the app. You also have to hope that this app will let you export your data. So quite a change, but that's not the worst case scenario. It can also happen that your app can leak your data, which has happened in multiple cases and there were real life risks associated with that also in multiple cases. So we'd like to change that. And by we, I mean me, I'm the author of Feel and also Roland Geider, who was supposed to originally give this presentation with me but couldn't make it today. So we want to change this and we want to make free and open source fitness apps the norm. So that people wouldn't have to compromise on their privacy or the control over what they run on their device or their habits just to be fit. So this is our goal. Here's where we are now. We have these two apps that you can use right now. And there's also an API that anyone can use. It's a public API associated with Beggar. I'll go into more detail about each of these. So my app, Feel, is a simple guided workout app. Basically how it works is you open the app, you see a list of workouts, you choose a workout, and then this app guides you through that workout, telling you how many seconds you have left before the break and then before the next exercise, you can choose from some pre-made workouts or you can create your own. And this app runs on Android as well as Linux. It's a Flutter app, so it's easy to port to other platforms. And all your data is stored locally. And the problem with this app is that for now there's only 57 exercises that you can build the workouts from. While you do have images and descriptions, et cetera, for these exercises, there's not that many workouts that you can actually build. But this is going to change, and I'll get back to this. Then we have Vega, which is an online application that allows you to create your own workout schedules, create your own meal plans, and then helps you follow up on them. You can track all of these things via this web interface, and it's for more experts, more seasoned athletes. This is a web application, but you can host your own server, so you still have control, and of course it's all fully open source. And there's also client applications for Android as well as for Linux via FlatHub. There's also the Vega API, which Vega pulls its information from. And this API gives you access to all of the things that you store in Vega, including your account details, meal logs, nutrition plans, workout schedules, et cetera. But most importantly, it also hosts the Exercise Wiki, which is a very important aspect not just for the users of Vega, but also for pre and open source app developers, because suddenly it creates a centralized resource that developers can use to exercise data, exercise images, exercise beta data, such as which muscles each exercise targets or what equipment you need to use for each exercise. And all of this is licensed under the Creative Commons Share Like license. All of this is just like with Wikipedia, contributed by a range of people. And really it's an invaluable resource that one person couldn't create by themselves. The beauty of crowdsourcing is that everyone contributes a little bit, and then you build something huge that no one person could easily create. And we see this as really kind of a launchpad for various pre and open source fitness apps that they can use, because suddenly it becomes much easier to create your own app for your own niche that you target to your demographics of choice. So we're building this. Vega right now has 350 exercises in its Exercise Wiki. There's more than 22,000 accounts on there. It also has more than 2,300 GitHub stars. So it's relatively popular among developers as well. The Wiki is relatively new and there's some bugs being sorted out. So this exercise number is sure to grow in the future. But we still haven't reached our goal of making free and open source fitness apps the norm. So how do we get there? Well, we need you. We need the community to contribute exercises to help us build apps and more. There's a number of ways you can contribute. I've mentioned the Wiki. You can go on vega.de today and contribute an exercise or contribute changes to an existing exercise that's on there. You could add more information. You can revise the steps if they're not correct or there's not enough information. You can upload images. I would hold off on uploading images for now unless you have public domain images that you can fully share because this is still being worked on. There's missing functionality for specifying license. So unless you have public domain images, don't upload images yet, but maybe save them to a folder for uploading at a later date. Speaking of images of photos, in my experience, a lot of people don't tend to like taking photos of themselves and publishing them online for people to use and see. And this is one of the reasons why FEEL uses this low-poly look, this triangulated look. And what you can do if you're feeling shy about submitting your own photos is download this app called Foist Triangulator. It's a Java app that you can use. It's on FlatHub, but you can also use it on other platforms, of course. And you can add your image, create a low-poly version like this, which you can customize where the points are so that it looks good and so that it's anonymous enough to your liking. And then you can export the SVG and submit that so that your face is obscured enough. You don't have to feel shy, but you can still contribute to this open source wiki of exercises that we have. And then besides the ways of contributing, there's also the standard ways you can develop. You can help with the development of these two apps or you can develop your own app, perhaps integrating some of or all of Vega's API, including this exercise wiki. You can help us translate. You can translate via weblaid or you can translate exercises via the Vega wiki. You can help design. You can help test. And, of course, you can spread the word, share on any social media that you happen to use. So I hope you're as motivated about making the world of free and open source fitness apps happen. If you are, you can visit these links. There's also under these links links to chat with the community, so you can talk to us there. And I think we have a little bit of time for questions. We have to go on to maybe community integration. Right, so the question was if we can integrate with hardware such as smartwatches, fitness, the trackers of all kinds. And this is maybe on the roadmap. Right now we're focusing on more core stuff. Such as this wiki. But I'm sure that eventually there will be support. If you'd like, you can help us implement this. And potentially, if there's more free and open source apps, there are some open source apps already that do have this integration, mostly on Evdroid. Perhaps we could collaborate with them as well. Yes? I would like to ask more details about your plan to make this norm, because in my experience, almost every user doesn't care about privacy unless we're open source or proprietary fitness switching application or something like that. So what's your plan actually to make the application so good that they will stop using the proprietary applications in favor of this? Right. So the question was how do we get people to, how do we get people to use these free and open source applications so that they become the norm? And I think the answer here is, right now, if you look at the landscape of fitness apps in general, there's a ton of fitness apps, but no clear ones that people would recommend. And I think that creates an entry point for free and open source software, because apps come and go. Apps are being canceled all the time. There's mergers. There's redesigns. There's all sorts of things. And there's no one clear app to use. And I think the advantage that the free and open source world has here is that really you can focus on building apps for a specific use case. And these apps, then, because they're open source, even if the original maintainer leaves can then be maintained if they're useful to people. And also, we can have joint efforts, like this exercise wiki that everyone can use. So really, I think we can grow communities in a much more efficacious way than closed source projects can, just because we share a lot of things among various open source projects. Any more questions? Yes? One thing which seems a bit of a nuisance is that Garmin will only license their API use to commercial entities. Right. Is it worth registering one of these as commercial for purposes of getting a common API? So the question was whether we can. So the question was Garmin currently provides access to its API only to commercial entities. And it's a question of whether it's worth it to create a commercial entity to be able to access this API. And I would just say that I personally haven't specifically thought about Garmin. Maybe, again, this is something worth visiting in the future. It's also a question of whether it might not be better to just integrate with some resource that already plugs into the Garmin API so that you'd have your data from Garmin somewhere in some centralized piece of software. For example, Google has its do tracker that amasses all sorts of fitness data from everywhere and you can plug into it. But it's something that we'll have to look into going to the future. Maybe, in Garmin, you can take it. Yes, we can potentially convince Garmin to open it up. Yeah. All right, thanks.