Firstly, Quadrant v24.11 is a very small update. The smallest one in a long time. This is due to the fact that I've been busy at school and other things (some related to Quadrant).

Quadrant v24.11 changes include:

• The use of the Carousel View introduced in Flutter 3.24
• The app now opens a wiki page explaining how to fix the app on Windows. This is due to the fact that Quadrant requires Developer mode to be enabled on Windows and many users have it disabled by default.
• Dependency updates

What's going on behind the scenes of Quadrant ID / my API

I've spent a considerable amount of time on making my API, which powers Quadrant ID more stable and consistent. This includes the API v3 update, which made the paths used by the API easier to read and maintain. However, this month I've completely changed the internal structure of the API.

New code structure

Now the internal code of the API is significantly more organised. The code is now contained in a monorepo. This lets me keep the code split into different pieces, which makes it easier for me to maintain, as it makes different components of the code separate and isolated. The separation also has a big advantage, it lets me split different parts of the API into different Docker images.

Different parts of the API now run separately from each other

What does this mean? Previously, everything under https://api.mrquantumoff.dev was a monolithic package, meaning that if Quadrant Sync fell, everything else would fall too. Now, on the other hand, everything is separate, I can disable one part of the API, without affecting the rest, or if a part of the API goes down, the rest can stay up. For example: Now if Quadrant Sync's container crashes, Quadrant ID, Quadrant Share, Quadrant Feedback, and other services remain untouched. Splitting the API into different containers also helped me reduce the size of containers. If previously the whole API took about 2.3 gigabytes of space, due to me not really optimizing the Docker image, now it consists out of 6 small containers, each taking about 25 megabytes of space.

Hopefully, that explained the stuff that I've been doing in November clearly. Now let's move on to my plans/ideas of what I want to add to Quadrant.

Potential future ideas for Quadrant

• Quadrant Settings Sync - I've been thinking about letting Quadrant ID users sync their settings across devices, this would be very useful for people with secondary devices.
• Quadrant Companion app - I'd love to play modded Minecraft on my Steam Deck, however installing mods on a touch screen is kind of annoying, and Quadrant on the Deck is not perfect, it often doesn't let you use libsecret, which makes Quadrant ID/Quadrant Sync unavailable. However, if there was a simple app that attaches itself to a LOCAL device (not synced with Quadrant Sync), then it'd be easy to install mods on a Steam Deck.
• Identifying unknown mods - as most of you probably have already noticed, Quadrant only indexes mods installed by the app itself, identifying unknown would be very useful for a lot of Quadrant users.

PLEASE COMMENT ON THIS ARTICLE TO LET ME KNOW WHAT FEATURES DO YOU WANT TO SEE IN QUADRANT (INCLUDING THE ONES MENTIONED HERE)!