Contributing

IzzyOnDroid is free to use for everyone due to the hard work of our community. If you are willing to join our community and help us out that would be great!

Below are some common tasks that we can always use some extra hands with. However, if none of these tasks work for you, feel free to look around our Codeberg org or contact us.

New app request

We are always looking for people willing to help out with new app inclusion requests on our GitLab.

If you see any issue which doesn't seem to have been tested yet (anything without approved label), you could help us out a lot by testing it.

Basic app repository check

Checking if the following is true for the repository hosting the app is very helpful:

1. Is the source code available under an FOSS license? Also note that, especially when mixing libraries, there might be license incompatibilities (e.g. an app licensed Apache-2.0 can not use libraries with a stricter license like GPL-2.0).
2. Is Fastlane configured and does it look OK? Any issues (e.g. short_description.txt longer than 80 chars, messy/missing full_description.txt, featureGraphic with wrong proportions)?
3. Description has enough details (so users get an idea what the app is about)?
4. Are releases tagged? Do tag names match either versionName or versionCode?
5. If you have the knowledge: check the code for possible issues

App tests

If the app request issue has the needs-on-device-testing label, we still need someone to test the app. If this could be you, great!

First off, check if the developer attached an .apk file to the most recent release on their Codeberg/GitHub/GitLab/etc and check if it's less than 30MB. We cannot currently accept apk files over 30MB. Does it exist and is it small enough? Then we can test it. If not, ask the developer to attach an .apk or try to reduce its size.

1. Before you install it to your device: download the APK and upload it to VirusTotal (also look through the permissions and "interestring strings" on the details page there - especially be alerted when the "behavior" tab shows up: give it a thorough look!) and, if possible, other library scanners at your disposal – e.g. Pithus.
2. Install it to the test device/emulator
3. Make sure to enable network monitoring/logging - e.g. in Netguard, PCAPdroid or AFWall+ (root needed)
4. Test if it starts
5. Watch out for outgoing network connections (some red flags: right after start, without user interaction, unexpected network connections, connections to places like Google, etc.)
6. Check if the app seems to does the general things it promises to do (no need for it to be fully bug-free, just generally be usable)

Fixing other issues

Look around our Codeberg and see if any of the repositories have any issues you can help with. Most will need you to have development skills, but occasionally we also need artists, translators or other groups of helpful people :)

Mirrors

You have experience with web hosting, and a server with some disk space (currently, 50 GB are fully sufficient) a well as a good internet connection? Maybe you'd consider hosting a mirror of the IzzyOnDroid repository? That would be exciting! Please, don't hesitate to contact us!

Verification Builder

You enjoy tinkering with builds, have experience with fixing them, maybe already found our rbtlog repository, and even run such a builder for yourself? We always welcome independent builders. More people confirming builds independently, means higher trust. So once more, please reach out to us if this fits you!

For those who got just curious now: head over to our rbuilder_setup repository, which allows you to set up your first builder within less than 5 minutes, on a Linux system (and we heard, even on WSL and Steam Decks).

Donating

Donations definitely also help. They allow people to take time off from their day job and allow us to buy cool stuff (servers or stickers for events). Please look at our OpenCollective and our Liberapay for donations.