Greetings, everyone! My name is Andres, and I am the developer of LemmyApps.com. Today, I would like to share what I have been working on for the past several months.
What is LemmyApps.com?
LemmyApps.com helps users discover Lemmy apps that best suit their needs. Whether that means apps that are open source, free, etc.
This is the first public release, so expect bugs!
What does this site offer?
- Use the API to get apps, releases and platform information.
- Sort apps by last commit, last release, downloads and many more attributes.
- Filter apps by platform, open source, free, and in-app purchases.
- Users can submit apps and update their listings with new releases easily.
- Users can claim apps and update their author profiles.
- Supports every platform and sub-platform – including lesser known stores.
- Every 6 hours, information is aggregated from GitHub, GitLab, Play Store and the App Store.
Roadmap
- [ ] More modern and responsive design
- [ ] Add filtering for specific Features
- [ ] Add product images via carousel
- [x] Support additional platforms like Codeberg
FOSS Commitment
LemmyApps.com will be FOSS soon. I am looking for a .NET developer interested in helping review the code for any security issues. Please email me at support at lemmyapps dot com.
Feedback
Please share your feedback in the comments below!
P.S. If you think the design is ugly, feel free to use the API to make a prettier website! I invite friendly competition. After all, my goal is to help spread the adoption of Lemmy apps.
Also, Memmy is shown as having a recent commit 23 days ago - this commit was created by a bot here, and isn’t actually indicative of active development. It may be worth ignoring commits from depandabot when checking for the most recent commit, if that’s possible.
Thank you for pointing this out! LemmyApps uses the “PushedAt” field from the GitHub repository response to determine the latest commit. However, this appears to be the latest commit across all branches, including
dependabot/*branches.I may have found a workaround that considers just the main branch. I will add this to the priority implementation list.
If you end up only considering a single branch, it would be a good idea to let app owners change which branch is considered “main”. Many apps have a main branch that stores the live code state, and a second development branch where all of the work is done. When an update is released, code is pushed from the development branch to the main branch. In this setup, it would make the most sense to show the most recent commit on the development branch rather than the main branch.