To see what we’re aiming for in the 23.10 MVP see the overview below and let us know what you think:

Additionally, we could support other signals, for example, by computing the ratings slope one could image a “most improved” category. This is similar to what Steam does, and they can still compute pseudo 5-star ratings while providing a simpler UX. We’re also looking to simplify ratings with a +1 or -1 approach. Finally, nothing here stops users from installing applications the old fashioned ways. Deb support will land later because resources are always tight (we’re a small team). So, I’m describing this as a “snap-first app store” not because we won’t support debs, but because we’re designing the experience around snap metadata. Doing that is hard to get right and restricts design choices in other areas. The App Store will support debs, but it’s a non-goal to try and present debs and snaps as two options for the same app. I’ll provide more details in a separate post but I want to briefly call out two points: I write “new” because there’s prior art that’s helped jump start this (big shout out to from the community here). I’ve mentioned previously that we want to land a new flutter-based app store in 23.10.

This is enabled by using conventional commits in our repositories to enable auto generating release PRs for eventual publishing to (see and to learn more). This pulse he has brought us a step closer to automated releases for our flutter repositories. You can read more in this in Jan 2020 continues doing awesome things in flutter. That is now sorted and all rules have been rewritten in javascript. You might wonder why I’m leading with this update, until you read that the previous version, 105, was released in 2012! The blocker for a straightforward upgrade was polkit moved to javascript-based rules, and to support that, it introduced a dependency on Duktape. I’m happy to announce that polkitd 122 landed in mantic. All this to say, expect fluctuations in the metrics I share because our processes are evolving. In time, this will support capacity planning and give excellent insights into where we’re spending our time (ie maintenance, packaging, building new features, etc). Let’s jump straight in.īecause we want insights into where we’re spending resources, we need to make sure our ticket metadata is complete. Tim again with your fortnightly desktop update.

Download Mozilla Firefox 114.0.2 free