21 lines
No EOL
1.5 KiB
Markdown
21 lines
No EOL
1.5 KiB
Markdown
# Accepted Additions and Requests
|
|
One of the reasons I built Auxio was out of frustration with other FOSS android music players, which had too many features, frustrating UI/UX flaws, or both. Therefore any additions will have to be accepted by **me** (OxygenCobalt) before they are implemented or merged.
|
|
|
|
## Bug Fixes, Optimizations, Architecture Improvements, etc.
|
|
These will likely be accepted as long as they do not cause too much harm to the codebase.
|
|
|
|
## New Customizations/Options
|
|
While I do like adding new behavior/UI customizations, these will be looked at more closely as certain additions can cause harm to the apps UI/UX while not providing a lot of benefit. These tend to be accepted however.
|
|
|
|
## Feature Additions and UI Changes
|
|
These arent as likely to be accepted. As I said, I do not want Auxio to become overly bloated with features that are rarely used, therefore I only tend to accept features that:
|
|
- Benefit **my own** usage
|
|
- Are in line with Auxio's purpose as a music player
|
|
|
|
This does not rule out these additions, but they are not accepted as often as others. I will also hold off adding features until I'm able to implement them without disruption or strange behaviors.
|
|
|
|
Feel free to fork Auxio to add your own feature set however.
|
|
|
|
## Additions that have already been rejected
|
|
|
|
To see an up-to-date list on all of the features that have been rejected, see [this link](https://github.com/OxygenCobalt/Auxio/issues?q=label%3Awontadd-technical%2Cwontadd-out-of-scope+) |