Face-Off’s editor can turn supported parts of a Huawei HWT design into a Wear OS project. The result depends on the HWT layout and the features inside it. A readable dial is a useful starting point, but the conversion report decides which functions still need work.

Import a working copy

Open the Studio editor, choose Open project and select the .hwt file. Keep that archive separately. Once it opens, use Save project file to keep a portable .faceoff.json master with the editable layers and artwork.

Read Conversion review before changing the design. It separates imported, approximated and unsupported features. A source that fails to open may use a different binary revision or exceed an import limit; renaming or repeatedly repacking it will not supply the missing format support.

The current importer handles parts of legacy binary V1 and a separate nested-XML resource layout. Binary V2 remains unsupported. Those profiles do not have identical capabilities, so a successful port of one face does not establish support for every HWT from the same watch family.

Check the clock before the decoration

Start in Normal mode and verify that both hours and minutes work. A face can have a complete authored AOD clock while its normal clock is incomplete. Test midnight, noon and a late-evening time, then look for leading-zero and hand-pivot errors.

Supported bitmap hour digits can use 12-hour, 24-hour or device-preference behavior. That changes their time binding. It does not repaint a baked 24H legend or translate words already drawn into an image. Treat those as separate artwork decisions.

Open Review project to compare Normal and AOD scenarios. Check missing artwork and font findings as well as the time. If an imported face already has an authored ambient design, review it before replacing it with a generated one.

Treat data support as a feature-by-feature check

Supported legacy profiles can retain battery and step-goal artwork, including selected circular meters. Step percentage follows the Wear OS goal. The circular conversion approximates the source masking, so inspect the direction, edges and endpoints at empty, partial and full values.

Heart-rate meters need both a known source mapping and supported image geometry. Some are omitted even when the source value is understood. Stand-up progress has no mapped portable equivalent here. Other health data, weather, notifications and tap actions may also be absent. Nested-XML ports currently omit combined metrics, circular meters and unsupported providers or options named in their report.

Use custom review values to make a gauge change visibly. A moving preview confirms that particular preview path; it does not prove a real sensor supplies readings on the watch. Wear OS exposes its own WFF data sources, and a Huawei source identifier cannot be substituted blindly.

Build and test the Wear OS result

Repair or document the remaining findings, save the master and use Build for Wear OS when builds are available. An exported .wff is editable source; Download APK retrieves a completed build. Studio’s builds are private development packages for testing.

Install on a compatible Wear OS watch and select the face. Check the active clock, ambient appearance and any supported data changes against the same project revision. Also reopen the exported source to catch bindings that only looked correct before export.

Keep conversion limitations with the prepared listing. Describe the working Wear OS features and any omissions, and show screenshots from that result. A source preview from Huawei cannot stand in for a screenshot of the completed port.