Redo suggested commits
This commit is contained in:
parent
9e2395fa29
commit
eb2a28c800
|
@ -7,13 +7,13 @@ These are some basic principles that we want maintainers to follow when maintain
|
|||
NewPipe is a media player for devices on the Android platform, thus it is intended to be used for entertainment. This means it does not have to be some professional
|
||||
application, and it does not have to be complicated to be used.
|
||||
However NewPipe might not focus on the casual user completely as there are
|
||||
many features that are a bit more "techy" and may require some knowledge about
|
||||
some features designed for more experienced users which may require some knowledge about
|
||||
code, however in essence NewPipe should be easy to use, even for your average Android user.
|
||||
|
||||
1. __Don't add too many special
|
||||
features.__ NewPipe does not have to be an air plane cockpit. Do not try to fill every single niche that might exist. If people want more advanced features, they
|
||||
features.__ NewPipe does not have to be an air plane cockpit. Do not try to fill every single niche that might exist. If people wanted more advanced features, they
|
||||
would use professional tools. If you add too much functionality, you add complexity, and complexity scares away the average user. Focus on NewPipe's scope as a **media player** for the end user, and only as such.
|
||||
2. __Design the UI so that it is easy for the user__. Try to make it comply with
|
||||
2. __Usability of the user interface should be prioritized.__. Try to make it comply with
|
||||
[material design guidelines](https://material.io/design/guidelines-overview/).
|
||||
|
||||
|
||||
|
|
Loading…
Reference in New Issue