MuseScore Web Team Introducing

My name is Dmitriy. I’m a Product Manager of MuseScore.
Today we are launching the new group. In this group, MuseScore Team Members will make posts about changes in our products: what we are doing and how we are working.

It won’t be an official group with “dry” marketing texts. The group will contain personal messages from our team members, no matter what their specialization and English language level are. And no censorship or editing here. And, I think, it's a right time to apologize for possible grammatical and lexical mistakes in this text now  =)

We are going to use this group to inform our users about all the changes in the project (not only big ones). If you are eager to know what’s going on in MuseScore, you might want to subscribe to this group. But please notice: only team members can create posts here. All posts from non-team members will be deleted: please use Improving MuseScore group for your posts.

At the moment, MuseScore team is working on development of the whole branch of MuseScore products. But, unfortunately, sometimes the importance of issues we are currently solving is pretty hard to see.
In this first post I want to share, what happened this year, with you and also to talk about our plans.
We are going to grow MU to the new level. We believe that Open Digital Technologies is the future of “musicians market”. And here we can be leaders!

Our goal is to make our products the most useful and the most functional for musicians. It means that we should develop as fast as possible: Release new features, make UI better etc.
But in order to go faster, we need to solve some issues which block further development.
Year 2018 started with a huge task: updating the technical platform of

In the first quarter we implemented new search engine, all groups’ functionality, partially scores functionality. This was a very hard and important work, the result of which is sometimes not obvious for the users (and it is the best result, as usually users see the result of this kind of work only if something has been broken 🙂 )

But if we do it today, tomorrow we’ll be able to do 3 times more.
But it doesn’t mean that we stopped development of new features.

This year we’ve released some updates related to community: 
- New community index page with simple search of new text content.
- New WYSIWYG editor in community posts and comments: Now you can create nice and readable messages.
- We’ve relaunched the “MuseScorer Of The Month” project.
- We are making some experiments with “Hubs”. We are trying to make scores searching simpler. This can help to raise the “view count” for content creators.
We are going to solve the spam problem in scores, and a lot of plans with the “Browse” page and “Hubs” page improvements.


We are continuing to contribute into the MuseScore notation software. In the beginning of the year version 2.2 was released. There was a lot of important improvements. Now we are developing 2.3 and focusing on development of 3.0.
Our major goal here is to make the 1st  public beta version release for mass testing. We should make 3.0 as stable as possible to achieve this goal.

Mobile development

Here we are also having much work to do. We are moving our apps to the new technology platform which helps us to make the apps more useful and compatible with design requirements for iOS and Android. At the moment, our apps are in public beta testing, and I hope, that in near future new apps will be released in stores.

Then, we are going to improve UI of the apps. Also we are going to work on the integration of mobile functions with (Mobile app should be a real alternative of the mobile version of the site).


We are working hard to make a lot of improvements in every product. Unfortunately, in big projects like our, sometimes shit happens and we break some of the features from time to time. We are testing all the functions before releasing, but nobody except for real users knows the real cases of using products. So real users are the best testers for us! We are fixing the bugs really quick thanks to our users’ quick feedback.

All our team members are ready to solve the issues: every staff member takes time to read and to answer our users’ questions in “Improving MuseScore” group, and to reply to some support requests. 

Finally, I want to introduce to you the part of our team responsible for website development:

@abruhanov - our leading developer. He is responsible for the development of all new features and partially for platform updates. 

@Ximich - our chief developer. He is in charge of platform migration, project architecture and product optimisation.

@jilizart - UI-developer. He is responsible for the visual part of development.

@AlexanderT - Community Manager. He is responsible for the community, site content. He re-launched the MuseScorer Of The month project. Also Alex is testing our desktop and mobile products. He also consults us about all kinds of music-related questions, as he is a professional educated musician, saxophone player.

And me - I’m responsible for all MU products development including the website.

I hope that users will be happy with the results of our work. Because all that we are doing - we are doing for you: if you are happy - we are growing.

Add your thoughts
6 months ago