Thank you for your interest in contributing to Android Views! This document provides guidelines and instructions for contributing.
- Check existing issues to avoid duplicates
- Use a clear and descriptive title
- Provide detailed reproduction steps
- Include Android version, device info, and library version
- Attach screenshots or screen recordings if applicable
- Fork the repository and create your branch from
master - Make your changes following the code style guidelines
- Test your changes on multiple API levels if possible
- Update documentation if you change public APIs
- Submit a pull request with a clear description
- Follow standard Kotlin/Java conventions
- Use meaningful variable and function names
- Keep functions focused and small
- Add KDoc/Javadoc for public APIs
Use clear, descriptive commit messages:
feat: add particle color animationfix: resolve touch event handling issuedocs: update installation instructionsrefactor: simplify particle calculation
- Keep PRs focused on a single feature or fix
- Include relevant issue numbers
- Add screenshots for UI changes
- Ensure all tests pass
- Update CHANGELOG if applicable
- Clone the repository
- Open in Android Studio
- Sync Gradle files
- Run the
appmodule for testing
When adding a new component:
- Create a new module following existing naming patterns
- Follow the existing architecture (attrs.xml, custom View class)
- Add comprehensive XML attributes for customization
- Include usage examples in the demo app
- Update README with documentation
Feel free to open an issue for any questions about contributing.