Proposing a change to design
Factors influencing design
If you want to make changes to MuseScore's design, you need to show that you have thought about:
- Consistency with existing designs (or why you think a new approach is needed)
- Ease of adoption for new and existing users
- Quickly perform common tasks (basic features)
- Flexibility to perform less common tasks (advanced features)
- Localisation (translations and regional variants)
- Portability (across devices and platforms)
- Scalability (across screen sizes and pixel densities)
- Accessibility (for people who are blind, colorblind, partially sighted, or motor impaired)
The above factors do not necessarily apply in all cases. For example, if you want to change MuseScore's icons then this should have very little impact on accessibility or localisation. However, if you want to rearrange where the buttons that use those icons appear on the screen then this will affect accessibility, and if you want to display text next to those icons then the text needs to be translatable.
The best way to check that you have covered all the above points is to make a post in the Development and Technology Preview Forum. Your post should include:
- A description of your idea
- Diagrams or a mock-up of any visual aspects of your design
- An outline of how it addresses each of the above factors, or why you think a particular factor doesn't apply in this case.
You should send a link to your post to the MuseScore Developers Chat on Telegram to make sure it comes to the attention of developers. You should do this before you start doing any coding on your design to save yourself from having to make significant changes later on.