Cross-Device location Favorites and Platform Delivery Update

Another important piece of Apex Infinity continuity became real this week.

Companion now has the beginning of a broader account-backed sync model beyond ownership and purchased UX. Favorite locations are no longer just a local convenience tied to one install. They can now follow the signed-in Apex account across devices.

That may sound smaller than a checkout flow or a new creator feature, but it matters for a different reason: it is another proof point that the platform is turning scattered local state into a connected user experience.

Favorited locations now have account continuity

Until now, a user's saved locations in Companion were only local to the specific install that created them.

That was fine early on, but it stops fitting once the account model becomes a real part of the platform. If the same Apex account already carries UX ownership, library restore behavior, and purchase state, it also needs to carry the kinds of user choices that make the product feel personalized day to day.

The first of those is now in place.

Companion can now keep favorite locations tied to the signed-in Apex account, which means those saved location selections are no longer trapped on one machine or one phone. That is a small but meaningful improvement in product continuity.

It also matters because it establishes a pattern we can keep building on:

• local changes should still feel immediate
• signed-in users should keep a consistent account-backed experience
• and more of the platform should start remembering the user across surfaces instead of acting like every device is brand new

That is the right direction for Apex Infinity.

Companion logbook behavior got more honest too

We also tightened one of the rougher desktop edges in Companion logbook behavior.

If a user chooses the Google Earth path from the logbook and Google Earth Pro is not installed, Companion now handles that situation much more cleanly instead of letting it feel like a dead-end action.

That kind of polish matters because small operational frustrations add up quickly in real use. Good platform behavior is not only about adding features. It is also about making the existing paths explain themselves better when the environment is missing something the user needs.

Delivery and release work kept moving

This round of work also included another pass on delivery and build reliability across the platform.

Fresh Companion and Face Studio builds were pushed through the current desktop, mobile, and Apple delivery paths, and a few release-process issues were tightened along the way. That kind of work tends to stay behind the scenes, but it is an important part of what makes everything else credible.

It is one thing to add cross-device ownership, account-backed libraries, or synchronized product behavior. It is another thing to keep getting real builds shipped cleanly across the surfaces where users actually install them.

That delivery discipline is part of the platform story now too.

Why this matters

The broader pattern here is not just “more features.”

It is that Apex Infinity is steadily turning more user state into connected platform state:

• owned UX
• account-backed library behavior
• purchase visibility
• internal support visibility
• and now favorite locations

That is how a collection of apps and devices starts behaving more like one product.

What is next

The next logical step is already clear.

Now that account-backed sync is no longer limited to ownership and library state, the next major sync target is the Preferences model in Companion. The goal there is for the visible Preferences screen to follow the signed-in Apex account across desktop and mobile Companion installs, while still preserving the rule that Companion is the only thing that sends those preferences to Core.

That will be a larger step than location favorites, but location sync is exactly the kind of smaller success that makes the next layer easier to build with confidence.