Wear OS 6+

We are fully compatible with Wear OS 6 and newer versions of Wear OS

What is different on Wear OS 6.

With Wear OS 5 and 6, Google is introducing a new, stricter system for watch faces called the Watch Face Format (WFF). It's a completely different approach that reshapes how watch faces are built and what they can do. Embracing this new standard has required us to rethink, redesign, and reengineer large parts of our app.

This has an effect on what is possible with Pujie. Some of the features we had before are not supported with WFF. Starting version 7 of Pujie, we cleaned the UI in order to support only those features which WFF can also handle.

Because of this some JavaScript feature are not longer supported, please have a look here for an explanation.

Other features, like additional views, extra time zones, certain data tags, tap automation, Tasker variables and parts of our JavaScript functionality, are also no longer supported due to the new format’s restrictions. We know these were popular, and we wish we could keep them all — but we’re making the best of what’s possible.

Why do watch faces need to be validated?

In Wear OS 6 Google requires each watch face which get's installed from an app like Pujie to be well formed and performant. Therefore a quick validation step is required before you can add a watch face to the library or before you can send a watch face to your watch.

During this validation step the watch face is checked for performance and further validity. In most cases in Pujie this will succeed. If it does not succeed, you might need to reduce the complexity of your watch face.

You can do this by moving all static items to a graphics element and placing them together in one element. Furthermore, make sure to use a black background in ambient and try to keep your ambient mode simple.