Cross-Device Preferences Sync Update
Apex Infinity has taken the next step in account continuity: the visible Preferences model in Companion now follows the signed-in Apex account across devices, making setup feel more like part of one connected platform instead of a series of isolated installs.
Another important piece of Apex Infinity continuity is now in place.
After account-backed UX ownership, synced libraries, purchase visibility, internal support tooling, and cross-device favorite locations, the next layer was obvious: the visible Preferences experience in Companion also needed to follow the user.
That now works.
Preferences can now follow the signed-in Apex account
Until now, Companion preferences still behaved more like local setup than platform state.
That meant a user could sign into the same Apex account on more than one device, own the same UX, restore the same library, and keep the same saved locations, but still have to rebuild their actual Companion setup device by device.
That was no longer the right product behavior.
The visible Preferences model in Companion can now follow the signed-in Apex account across supported installs. If a user changes settings on one Companion device, those changes can appear on another device using the same account instead of forcing the user to recreate the same setup again and again.
That is a meaningful shift in how the platform behaves. It makes Preferences feel like part of the account-backed Apex Infinity experience rather than a pile of local-only state.
Why this matters
This is about more than convenience.
As Apex Infinity grows into a connected system of hardware, apps, creator tooling, and account-backed ownership, the platform has to remember more of the user across surfaces.
That continuity now includes:
- UX ownership
- library restore behavior
- purchase visibility
- favorite locations
- and Companion preferences
Every time another part of the experience stops behaving like an isolated install and starts behaving like shared account state, the overall platform becomes more coherent.
That is the real value here.
The product model is getting clearer
This preferences milestone also reinforces an important product boundary.
Companion is the place where the user authors and manages these settings. From there, Companion can still send those settings onward to the rest of the system where appropriate. That keeps the user-facing setup experience grounded in one clear surface while still supporting the larger multi-device Apex Infinity model.
That distinction matters because it keeps the platform understandable even as more behavior becomes connected and synchronized.
What comes next
The next big continuity conversation is the logbook.
Preferences were the next natural sync target because they are visible, user-authored, and central to daily use. Logbook continuity is also compelling, but it is a larger product problem with different expectations around storage, history, privacy, and conflict handling.
For now, the more important result is that Apex Infinity has taken another real step toward becoming one connected user experience instead of a collection of separate installs.