Quadrant Next is (almost) ready!
There are a few issues that are left to fix.
It's been almost 2 months since the last Quadrant update. However, I've got good news to share.
Quadrant Next is ready,
but there is a distribution related issue that I've got to address.
Microsoft Store
See, the previous framework on top of which Quadrant was built (Flutter) has good tooling to provide updates straight to the Microsoft Store, however the new framework that I'm using to build Quadrant Next (Tauri) doesn't support Microsoft's preferred packaging format (MSIX). Tauri only supports .msi and .exe installers, which CAN be distributed through Microsoft Store, but they have to go through some serious moderation first. That moderation is code signing. Code signing is a good idea; however, its execution is extremely flawed. Code signing requires a certificate provided by a Microsoft-trusted provider and all of those providers charge ridiculous money for said certificates. The prices can go up to 800 USD for a certificate. The only way around those companies is the Microsoft Trusted Signing service, which charges 10 bucks a month, but it requires a lot of ID verification stuff, which is a lot of hassle. I'll try to resolve this in any way I can, however I will not be releasing an update on Linux before Windows and vice-versa. Both platforms will get the update as soon as it is ready to be live on both of them.
Changelog of Quadrant Next:
Quadrant Next doesn't have a specific version yet, but it's most likely going to be Quadrant v25.1 or v25.2
- New UI: Quadrant has been rewritten entirely, and therefore has a new, more unique user interface written in React + Vite.
- New backend: Quadrant's backend is now written in Rust instead of Dart. This lets Quadrant be more stable and consistent in a lot of aspects.
- No RSS or changelogs inside of the app. They might come back as notifications in the future, but that's not certain. I'm still thinking about them. For now, they're not available, so if you notice that something's different, you'll have to go to this blog manually.
- New logo! This is a new era for Quadrant and in order to celebrate it properly, I believe that Quadrant should have a new logo.
The new logo is a more evolved version of the old one.
- Some unused features were retired, such as: Quadrant Feedback.
- Some feature's behaviour was altered: Now you can't update a modpack to a new Minecraft version. You first have to change the modpack's Minecraft version and only then update the mods in it.
What does this mean for the future?
This whole rewrite makes maintaining Quadrant a lot easier.
Are there any downsides of this rewrite?
Sadly, yes. Since I can't test the app on a mac at all, macOS support has been dropped entirely. It might come back in the future (if I ever get a mac for long enough to debug the app on it). However, anyone who wants to fix any existing bugs on macOS is welcome to do so, because the proprietary components of the app are separated from the proprietary ones, so anyone who's willing to fix bugs can do so.
Linux users might experience worse performance, due to the webkit JavaScript engine being utter garbage. However, the moment Tauri provides the ability to package CEF or any other JS runtime I'll be more than happy to implement it.
What about the old Quadrant (Classic)?
I'm not completely disabling the old codebase the moment Quadrant Next comes out. The old app will be available on Microsoft Store under the "Quadrant Classic" name. It won't ever get updated though. I'll delist the old app in a few months after the stable release of Quadrant Next and rotate the Quadrant ID API keys whenever I bring changes to the Quadrant ID security infrastructure, which I plan to do sometime this year.
Can I install Quadrant Next right now?
Yes, you can grab the latest release manually. Grab the .exe installer for Windows. Linux builds might be slightly unstable on the Github releases page, but you can check them out. Also change the update channel to "preview" until the stable version of Quadrant Next gets released.
I think this is about it. Hopefully, I can get the app published properly soon. See y'all soon. - Demir.