You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've missed this watch face ever since moving to the pixel watch 3 which launches with wear os 5 and enforces the usage of watch face format (wff) and I'd love to be able to use it again. I understand that it might be a huge endeavor and I'm just wondering
The text was updated successfully, but these errors were encountered:
I have considered re-implementing the watch face in WFF, however it appeared like being a high-risk/low-reward situation so I haven't made any effort on it.
Reasons:
The Hybrid Interface is not enabled on Pixel Watch 3, even if it has the hardware capabilities (auxiliary MCU). Even if I implemented it, I speculate there would be minimal battery gains, if any.
The WFF format was enforced by Google despite developers being vocal about their concerns with it, i.e. its lack of adoption and restrictions.
(opinion) XML is not fun to write, or easy to maintain.
I only own an OG Pixel watch and do not intend to upgrade, unless the battery life improves significantly on some future model. One day of battery life is not good enough for me; having to choose between sleep tracking and finess tracking is not acceptable.
Due to this, I am more or less unable to test the watch face properly, even if I adapt it to use WFF.
Maybe, when I find the time and courage, I shall delve into WFF. I am leaving that possibility open.
Update: I have started on a WFF implementation. I am unsure if I will achieve feature parity, but at least I can, after some tinkering, have pixel-perfect font rendering, which I thought wasn't possible.
I've missed this watch face ever since moving to the pixel watch 3 which launches with wear os 5 and enforces the usage of watch face format (wff) and I'd love to be able to use it again. I understand that it might be a huge endeavor and I'm just wondering
The text was updated successfully, but these errors were encountered: