Faces Management And Device Polish Update

Since the last update, the work has shifted from enabling customization in principle to making it easier to live with day to day.

That has meant a better faces experience in Companion, more complete built-in and custom face behavior across both device types, and a round of polish work that makes the overall flow feel less experimental and more like a coherent product surface.

This was not about introducing one giant new feature. It was about tightening the whole path around face selection, delivery, fallback behavior, and device parity.

Companion Now Handles Faces Much More Cleanly

One of the biggest improvements in this stretch of work is that face management now has a clearer home inside Companion.

Instead of being buried inside Preferences, faces now live in their own dedicated section. That sounds small, but it changes the product in an important way. Choosing, sending, and managing faces is no longer being treated like a minor settings detail. It is now presented as a first-class part of the device experience.

The faces view is also more organized than it was before. Classic and Edge content are separated more clearly, built-in options and imported custom options live in a more understandable structure, and the app is better about telling you what is currently selected and what is actually active on the device.

That makes the overall experience easier to reason about, especially as more content starts to exist across more than one device type.

Built-In Faces Behave More Intentionally Now

Another important improvement is that built-in faces are no longer treated like an awkward special case.

Classic now has a cleaner path for choosing among its built-in analog and digital looks, and Edge has a more intentional path back to its built-in default presentation as well. Reset behavior is clearer, built-in selection is more direct, and the app’s faces screen is doing a much better job of representing what the product actually supports instead of showing placeholders that no longer match reality.

That matters because the product should not make a distinction between “real” face behavior and “default” face behavior if users experience both of them the same way. The flow now reflects that much more honestly.

Device Behavior Is Closer Across Classic And Edge

This round of work also brought the devices closer together in an area that used to feel uneven.

Apex Edge now behaves more naturally when custom content is active, including better restore behavior and a more complete path back to the built-in experience without making the device feel stuck. That puts it much closer to the level of flexibility people already expect from Apex Classic.

The important point is not that the two products are becoming identical. They are still different devices with different form factors and different visual languages. The important point is that the gap in basic experience is getting smaller, which is the right direction for the platform.

The Visual Side Is Catching Up Too

A lot of this work was also about presentation.

The faces UI in Companion now does a better job of previewing what you are actually choosing. Classic previews are fuller, Edge previews better reflect the rectangular device shape, active selections are more obvious, and the overall layout is easier to scan on desktop and mobile.

Those are not just cosmetic tweaks. When users are deciding what to send to a device, the quality of the preview directly affects whether the feature feels trustworthy.

Why This Work Matters

The main outcome from this push is that customization is becoming easier to manage, not just easier to build.

Face Studio remains a core part of the creation story, but the surrounding layers now feel stronger too. Companion is better at organizing content. Built-in and custom behaviors are more aligned with each other. Device-side restore and fallback behavior are more intentional. And Edge continues to pick up capabilities that make it feel less like a second-class destination for customization work.

That is the kind of progress that compounds. It makes every future faces feature easier to introduce because the basic structure around the experience is getting stronger.

Where This Leaves The Platform

At this point, the platform is in a better place than it was even a few days ago.

Customization is not just something that can be created and transferred. It is starting to feel manageable, understandable, and consistent across the tools and devices that surround it. That is the real story in this round of work, and it is the foundation the next round will build on.