Hi everyone,
Thank you for raising these points, sharing your feedback, and highlighting what matters to you.
Release 1.2 was a substantial one (full list of changes here: MuditaOS K Roadmap & Updates). The next couple of releases may, in fact, be smaller in scope, focusing on specific areas of the system.
I understand it can be frustrating when we address one issue while another, seemingly more urgent one, remains unresolved. A few things are worth noting.
- We receive a large volume of feedback (which we greatly appreciate), but the requests do not always align and, in some cases, directly conflict with one another. When prioritizing changes, we consider the product’s core philosophy and make as much use as we can of quantitative inputs, such as survey data or the frequency of specific errors.
- In many cases, it makes sense to bundle lower-priority but quick fixes into a broader release. Even minor updates to one app often require full regression testing of that module. Sometimes, picking off these “low-hanging fruits” is practical, even when higher-priority topics remain elsewhere in the system. This analogy has some limitations, but if your car has both a high-prio check engine light and a low-prio squeaky suspension, it often makes sense to address both during one visit and run a single road test rather than fixing each issue separately.
- Our developers are quite versatile, but we do have areas of specialization that influence the sequence of work.
Also, I can imagine that not having an answer about when a particular improvement or fix will be delivered can be frustrating. However, we want to approach this responsibly, and sometimes that requires significant time to assess. We don’t want to make promises we won’t be able to keep. That said, I also want to assure you that none of the issues or requests shared here are being ignored. They are all reviewed and analyzed.
To touch on a few examples mentioned in this thread: in version 1.2.0, we changed the fingerprint logic. If an unregistered finger touches the sensor, the screen no longer wakes and does not go to the locked-screen panel with emergency numbers. Emergency numbers are no longer dialed by default in that state. In version 1.3.0, you will be able to choose whether the fingerprint sensor reacts on touch alone or only after pressing the power button.
Version 1.2.0 also included keyboard optimizations. We see room for further improvement in the keyboard and are also planning updates to the calendar, but it is too early to share release dates for those just yet.
There is clearly more to do, and we are committed to continually improving the product. We hope this will be reflected in your experience with each new release.
We’ll be updating the roadmap page with more detailed plans and would appreciate your feedback on each revision.