Is this the end?

[urszula]

@Neko Thank you for your thoughtful feedback. I completely understand the point you’re making, especially around trust. Even when an issue is not catastrophic, how quickly it is acknowledged and addressed can have a very real impact on someone’s confidence in the product.

We also understand that reliability of the existing experience has to come first. New features are exciting, but they matter much less if the core functions people already depend on are not working as expected.

In the case of the missed-call notifications introduced with MuditaOS K 1.6, our team has been investigating the issue and is working on a hotfix. We’ve also paused the remaining batches of the 1.6 rollout so that the corrected version can be released without exposing more users to the same problem.

One thing I would add is that, from the outside, a fix can sometimes appear much simpler than it is to safely distribute as a software update. Even when the community identifies an effective command or workaround, our team still has to validate the solution across different device states, configurations and upgrade scenarios, and make sure it does not introduce another regression elsewhere.

That said, your broader point about responsiveness is absolutely fair, and it is valuable feedback for us. We know that trust is built not only through the features we add, but through how we respond when something goes wrong.

[Michal_Kicinski]

We also like the direction of bringing more open-source philosophy into our products, and increasing the role of the community.

But I think the topic is a bit more complicated than it may look from the outside.

As a company, we are responsible for the reliability of the whole system. If something goes wrong, like recently with version 1.6, we need to catch it and fix it. Usually we manage to catch such things before release;-) With 1.6 the issue was caught during the release, so we are doing a hotfix.

Today there are already way more than 10k Kompakt phones working around the world, in many different setups and configurations. And at the end of the day, we as a company are responsible for making sure that all of this works properly.

We have quite an extensive testing team and put a lot of effort into keeping the device stable. And if. You compare stability of Kompakt to let say Minimal Phone, or Light Phone 3 (all 3 in early stages of market existence), we can be quite proud of stability of our software - I write it not to pump our egos or make “empty marketing statements” but that was a reality we observed.

And this is probably the biggest question around open source for us: how to open things more, involve the community more, and at the same time keep the reliability of the device on the level we are responsible for.

MuditaOS K is quite a complex piece of software, and it is relatively easy to change one thing and accidentally break something else somewhere in the system.

So for us this is definitely an interesting and important direction, and we have a few ideas how it could potentially be approached. But it is too early to make any promises.

If you have ideas how this could work in practice, definitely share them. I think this is exactly the kind of topic where community input may be very useful.

There are also some licensing limitations around parts of the code, including some app and driver-related components, so there are several layers to the subject.

So yes, we also like this direction. It is just not as simple as putting the code on GitHub and saying: now it is open source.