New app: Brevier

Brevier is a reading browser without JavaScript: it fetches a page, reduces it to Markdown on the device and renders it in the reader's typography. It also reads Markdown documentation straight from git repositories, and RSS/Atom/JSON feeds. I am the author.

• Reproducible build: Binaries + AllowedAPKSigningKeys. This recipe was run in the buildserver-trixie image the way the fdroid build job runs it, and it built 0.5.3 and verified it against the APK in our GitHub release. Our release workflow also rebuilds every APK unsigned in a second directory and runs apksigcopier compare.
• Store metadata is upstream, in fastlane/metadata/android/en-US/: title, summary, description, changelogs, icon and screenshots.
• Updates: tags vX.Y.Z. versionCode is a literal in android/app/build.gradle.kts. The Rust version comes from android/rust-toolchain.toml. The NDK is pinned both here and in Gradle, and I'll send an MR when it changes.
• arm64-v8a only, as in our releases.
• License: the project is dual-licensed MIT OR Apache-2.0. The field takes one identifier, so it says Apache-2.0.
• Anti-features: none that I know of. The default search engine is DuckDuckGo Lite, and gh: addresses use the GitHub API; neither is needed to read the web.
• AI: Brevier is developed with an AI coding assistant (Claude); most commits say so in a Co-Authored-By trailer. This recipe was also drafted and tested with its help, and I reviewed it.

Checklist

Policy

• The app complies with the inclusion criteria.
• 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.
• 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.
• 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.