Skip to main content
Thank you for your interest in contributing to Namida! This guide will help you understand how you can contribute to the project.

​
Ways to Contribute

There are many ways to contribute to Namida, even if you’re not a developer:

Translation

Help translate Namida to your language

Bug Reports

Report issues you encounter

Feature Requests

Suggest new features and improvements

Documentation

Improve documentation and guides

Code Review

Review pull requests and provide feedback

Community Support

Help other users in chat groups

​
Important Note About Building

Building Namida from source is not currently directly possible.The project includes proprietary or private components that are not covered by the open source license. While the main project is open source, certain components remain the intellectual property of namidaco.For more information, see GitHub issue #37.

​
What This Means

  • Read and study the source code for personal learning
  • Modify the code locally for educational purposes
  • Submit pull requests with improvements
  • Fork the repository for personal experimentation
  • Contribute to discussions and code reviews
  • Build and run the app directly from source
  • Redistribute the app under a different name or license
  • Use the code for commercial purposes without permission
  • Rebrand or repackage the software

​
Reporting Bugs

Found a bug? Here’s how to report it effectively:
1

Check existing issues

Search the GitHub issues to see if the bug has already been reported.
2

Collect logs

Go to Settings > About > Share Logs in Namida to export error logs.
DO NOT SKIP THIS STEP. You will likely not get help without providing logs.
3

Create a new issue

Use the [BUG] issue template on GitHub.
4

Provide detailed information

Include:
  • Expected behavior: What should have happened?
  • Current behavior: What actually happens?
  • Steps to reproduce: Detailed steps (1, 2, 3…)
  • Screenshots/videos: Visual aids are very helpful
  • Logs: Attach the log files from Step 2
  • Device info: Android/Windows/Linux version, Namida version
  • Possible solution: If you have coding knowledge, suggest how it might be fixed

​
Bug Report Template

When creating a bug report, use this structure: 
## Expected Behavior
[What should have happened?]

## Current Behavior
[What actually happens?]

## Steps to Reproduce
1. Go to...
2. Click on...
3. Scroll to...
4. See error

## Screenshots
[Upload any screenshots or videos]

## Logs
[Attach log files from Settings > About > Share Logs]

## Environment
- Namida Version: [e.g., v5.6.1]
- Platform: [Android 13 / Windows 11 / Linux]
- Device: [e.g., Samsung Galaxy S21]

## Possible Solution
[If you have coding knowledge, suggest a fix]
Good bug reports with clear steps and logs get fixed faster!

​
Requesting Features

Have an idea for a new feature? Here’s how to request it:
1

Search existing requests

Check if someone has already requested this feature in the GitHub issues.
2

Create a feature request

Use the [FEATURE REQUEST] issue template.
3

Describe the feature clearly

Explain:
  • The problem: What issue would this feature solve?
  • Your solution: What exactly do you want to happen?
  • Alternatives: What other solutions have you considered?
  • Additional context: Screenshots, examples from other apps
  • Similar apps: Apps that implement this feature well

​
Feature Request Template

## Is your feature request related to a problem?
I'm frustrated when [describe the problem]

## Describe the solution you'd like
[Clear description of what you want to happen]

## Describe alternatives you've considered
[Alternative solutions or features you've considered]

## Additional context
[Screenshots, mockups, or additional information]

## Apps
[Other apps or services that implement this feature well]

​
Contributing Code

While building from source isn’t possible, you can still contribute code improvements:

​
Code Contribution Process

1

Study the codebase

  • Read through the source code on GitHub
  • Understand the architecture and coding patterns
  • Look at recent commits to see the coding style
2

Identify an improvement

  • Find a bug to fix or feature to implement
  • Check if someone is already working on it
  • Comment on the issue to let others know you’re working on it
3

Create a pull request

  • Fork the repository
  • Make your changes in a new branch
  • Write clear commit messages
  • Create a pull request with a detailed description
4

Respond to feedback

  • Address code review comments
  • Make requested changes
  • Be patient and respectful
The maintainer will test and integrate your changes if they’re approved.

​
Code Quality Guidelines

When contributing code:
  • Follow Flutter/Dart best practices
  • Write clear, descriptive commit messages
  • Comment complex logic
  • Keep changes focused - one feature/fix per PR
  • Test your changes thoroughly
  • Respect the existing code style

​
Helping with Documentation

Improving documentation is a valuable contribution:
  • Fix typos and grammar errors
  • Clarify confusing explanations
  • Add missing information
  • Create guides and tutorials
  • Update outdated documentation
  • README.md file
  • GitHub wiki (if available)
  • Issue comments and discussions
  • Community guides in Telegram/Discord

​
Community Support

Help other users in the community:

​
Where to Help

Telegram Chat

Answer questions in the community chat

Discord Server

Provide support on Discord

GitHub Issues

Help troubleshoot reported issues

GitHub Discussions

Participate in discussions

​
How to Help

  • Answer questions from new users
  • Share workarounds for known issues
  • Guide users through troubleshooting steps
  • Link to documentation when relevant
  • Be patient and friendly - remember you were new once too!

​
Translation Contributions

Help make Namida accessible to users worldwide:

Translation Repository

Visit the dedicated translations guide for detailed instructions

​
Testing Beta Versions

Help test new features before stable release:
1

Download beta builds

Get the latest beta from the snapshots repository.
2

Test thoroughly

  • Try new features
  • Look for bugs or regressions
  • Test edge cases
3

Report issues

Report any bugs you find following the bug reporting guidelines above.
Beta versions may be unstable. Always backup your data before testing beta builds.

​
Financial Support

Support Namida’s development through donations:

Buy Me a Coffee

One-time or recurring donations

Ko-fi

Support through Ko-fi
Cryptocurrency donations: 
Bitcoin / ETH / USDT (BEP20):
0x95b2834c84def92860df773d8b3d80d4c296d748
Donations help improve Namida and show appreciation. You can also support by starring the repository on GitHub!

​
Code of Conduct

When contributing to Namida:

​
Be Respectful

  • Treat all community members with respect
  • Use welcoming and inclusive language
  • Accept constructive criticism gracefully
  • Focus on what’s best for the community

​
Be Professional

  • Keep discussions on-topic
  • Provide constructive feedback
  • Avoid personal attacks or inflammatory language
  • Respect differing viewpoints

​
Be Helpful

  • Share knowledge generously
  • Help newcomers get started
  • Acknowledge others’ contributions
  • Celebrate successes together

​
License Information

Before contributing, understand the project’s license:
License: Custom End User License Agreement (EULA)Copyright: © Copyright (C) 2023-present Namidaco <[email protected]>

​
What the License Allows

  • Read, compile, and modify the code for personal usage
  • Contribute to the software
  • Study the code for learning

​
What the License Prohibits

  • Redistributing the program under a different name or license without permission
  • Commercial use without explicit permission
  • Rebranding or repackaging the software
See the LICENSE file for complete details.

​
Getting Started

Ready to contribute? Here’s how to begin:
1

Join the community

Join Telegram or Discord to introduce yourself.
2

Explore the project

  • Browse the GitHub repository
  • Read the README and documentation
  • Look at existing issues and pull requests
3

Find your first contribution

  • Look for “good first issue” labels
  • Check the translation repository
  • Answer questions in the community
4

Make your contribution

Follow the guidelines in this document for your chosen contribution type.

​
Special Thanks

Namida exists thanks to contributors like:
  • @MSOB7YY - YouTube client powering the YouTube section
  • @010101-sans - Creator of namida_sync
  • @cameralis - Awesome miniplayer physics
  • @alexmercerind - Technical assistance
  • @lusaxweb - Iconsax icon pack
  • All package maintainers who made Namida possible
  • Community translators on the translation repository
  • All contributors who report bugs, suggest features, and help others
Your contribution, no matter how small, makes Namida better for everyone. Thank you!

​
Questions?

If you have questions about contributing:

Translation Guide

Learn how to translate Namida

Troubleshooting

Get help with common issues

Build docs developers (and LLMs) love

Get started for freeTalk to us