Customization And Device Experience Update

Since the last blog post, the work has been centered on something that sits right at the intersection of product and platform: making customization feel real from creation all the way to the device.

That has meant tightening the authoring workflow in Face Studio, improving the way custom faces are managed once they are published, and extending more of that experience across the device family instead of keeping it isolated to one display type.

This is one of those stretches of work where the individual fixes matter, but the bigger story is that the entire path is starting to feel more complete.

Face Studio Is Becoming A Much Stronger Creation Tool

Face Studio made meaningful progress.

The editor is now more predictable across iPhone and macOS, project organization is clearer, validation is easier to understand, and the publishing flow is more disciplined than it was even a few days ago. That includes persistent validation state, better handling of unsaved changes, stronger control over when publish is allowed, and more intentional safeguards around what gets released.

The goal here is simple: creative tools need to behave consistently. If the state of a project feels fragile or confusing, the whole product feels less trustworthy. Tightening that workflow is a big part of making Face Studio feel like a real product surface instead of just a useful internal tool.

Publishing Is More Deliberate Now

The publishing path also got stronger.

Projects now carry more of the information they need before release, and the publishing process itself includes clearer checks around authorship, validation, and ownership. Unpublish support is in place, published work is treated more carefully, and local project behavior is less likely to drift away from what is actually live.

That may sound procedural, but it matters. The moment custom content becomes something that can be shared, browsed, and reused, the surrounding controls have to mature along with the editor.

A Capability For Edge That We Had Not Originally Planned

One of the more interesting changes in this round of work is that Apex Edge now supports a capability we had not originally planned to bring over in the same way.

We are keeping the implementation details fairly quiet for now, but the important point is that Edge is no longer being treated as a permanently narrower experience in this area. A feature that had effectively been living in the Apex Classic world is now being carried into Edge as well, which moves the two devices closer together in a way that feels much better from a product perspective.

That does not mean the two displays are becoming identical. They have different form factors and different strengths. But it does mean the philosophy is changing: if something materially improves the product and belongs on both, we are increasingly willing to do the extra work to bring it across.

Companion And Device Behavior Are Catching Up Too

The surrounding pieces are moving with it.

Companion is getting better at understanding which assets belong to which device, and the device-side behavior around custom content is becoming more natural as well. That includes cleaner apply paths, better restore behavior, and interaction changes that make it easier to move between built-in and customized experiences without feeling stuck.

These are the kinds of details that decide whether a feature feels polished or merely possible.

Where This Leaves The Platform

The main takeaway from this stretch of work is that customization is becoming a more coherent product story across Apex Infinity.

Face Studio is stronger. Publishing is safer. Device behavior is more intentional. And Edge is getting closer to Apex Classic in an area where we had not originally expected the two products to align this closely.

That is the right kind of progress. Not just more features, but a better and more complete experience across the creation, management, and device sides of the platform.