New app: Manja

Abstract for new app inclusion

Manja is a meal wheel and recipe book. You add the dishes you like, spin the wheel, and whatever you ate leaves the wheel until the round is over. It also keeps recipes with photos and nutrition values (built-in USDA data, offline), scans barcodes via Open Food Facts, shows what you can cook from what you have at home, makes a cookbook PDF, and moves everything between phones in one backup file. English, German and Bosnian.

I wrote it because our family kept having the “what do we eat today” discussion, and the recipe apps I found either needed an account, showed ads, or had no way to pick a dish for you. Manja combines the random pick with a full offline recipe book, and nothing leaves the phone unless you ask for it.

Development started in October 2026. The app has been used daily by family and friends through test APKs since then.

• Online USDA search is optional, the built-in data works offline.
• assets/starter/starter_en.manja is a zip of JSON and photos (the starter recipes), not code.

Checklist

Policy

• The app complies with the inclusion policy. Pay special attention to Quality point 6.
• The original app author has been notified (and does not oppose the inclusion). If you are not the author, please paste the link of the reply from the author.
• The upstream app source code repo contains the app metadata in a Fastlane or Triple-T folder structure. The summary and description must be included and images, icon, and changelog should also be provided for better user experience. The en-US locale must be included.

Docs

• Please read the guide first if this is your first contribution.
• Please make sure your metadata follows the best practice in our templates.
• Please read the Build Metadata Reference and make sure your metadata is valid.
• Please read the Quick Start Guide.

Merge Request Setup

• The title of this merge request should follow "New app: app name" format.
• Please make sure your fdroiddata fork is public and your branch is not protected. See https://docs.gitlab.com/user/project/repository/branches/protected/.
• Please read our Git guide if you don't know how to rebase your branch. Don't rebase your branch if there is no conflict.
• All related fdroiddata and RFP issues have been referenced in this merge request
• Please only submit one app in one MR.

Metadata

• Metadata must be put in metadata/<applicationId>.yml.

• Metadata must be a valid YAML file.

• Metadata must use LF as line ending.

• Don't add summary/description/changelog/images or anything that should be provided in upstream repo. Please check the Changes tab to make sure there is no other unrelated files added in the MR.

• Releases are tagged and auto update is enabled unless there is a special reason.

• There is an issue tracker and contact info of the author so that we can report bugs and contact the author.

• An AuthorName must be added. It doesn't need to be the real name.

• External repos are added as git submodules instead of srclibs. You can update git submodules without opening an MR in this repo and the submodule is covered by our scanner.

  Flutter is used as a srclib (pinned to 3.47.6) instead of a submodule. I can switch to a submodule if you prefer.

• Enable Reproducible Builds. We'll use your signature for improved security/reliability, also allowing users to switch between different channels. Do note that if you don't enable reproducible build then the apk will be signed with our key so you can't enable it later. If you can't enable this, please add the reasons here.

  Flutter builds are not reproducible across build environments yet, and I build on Windows. Please sign with the F-Droid key.

• Setup abi split if the APK is large and the splitted ones can be much smaller.

• Only the latest versions should be kept in the metadata before it's merged. If you update the metadata, please replace the old versions with the new ones.

• Don't add any disabled versions in the metadata.

• The commit field should be the full hash. Please don't use tag or branch in commit.

Pipeline

• All pipelines should pass.
• All warnings and errors in the Reports tab should be fixed or explained.
• F-Droid CI runners are under GitLab's FOSS program, so there's no need for you to pay for any CI time. If Gitlab starts asking for phone numbers or credit cards don't submit anything, just leave a note in the MR so we know we need to trigger the CI.

---

Closes rfp#