Thank you for your interest in contributing. This document outlines how to get started and what we expect from contributions.
Be respectful and constructive. Focus on the work, keep discussions professional, and help maintain a welcoming environment for everyone.
Before opening a new issue, search existing issues to avoid duplicates. When filing a bug report, include:
- A clear description of the problem
- Steps to reproduce
- Expected vs. actual behavior
- Device/emulator details (API level, manufacturer if relevant)
- Screenshots or logs when helpful
- Fork the repository and create a branch from
main - Make focused changes with clear commit messages
- Follow existing code style and project conventions
- Test your changes locally (
./gradlew assembleDebug) - Open a pull request describing what changed and why
- Install Android Studio and the required SDK platforms
- Clone your fork and open the project
- Sync Gradle and run the app on an emulator or device
Write concise, descriptive commit messages. Prefer the imperative mood:
Add policy details screenFix dark theme status bar contrastUpdate Compose BOM to 2026.02.01
Keep pull requests focused. Smaller, reviewable changes are easier to merge than large refactors that mix unrelated updates.
By contributing, you agree that your contributions will be licensed under the Apache License 2.0.