Facer Originals Exclusive Partnership

General
21

I think the point here tho is, the things that Facer is missing, that do actually exist in Samsung Watch Face Studio/WFF. A large number of tags in Facer that existed before the WFF transition are understandably gone now.

I think what people don’t realize, and I actually didn’t either until I started writing my own IDE is that WFF can not contain any executable code. It is a Declarative only system. Before WFF executable code worked in Tizen, and older WearOS (mostly for backwards compatibility). …and as Google says, it is in the name of battery conservation.

So the bigger picture now is, why isn’t Google Exposing more Tag Data for us to use? The general consensus is Battery Conservation, and Privacy, plus adding these at the OS Level mean they have to work on all Hardware Platforms. The other thing is, once they add something, they are publicly contracted to keep it there, and stay consistent.

The part that frustrates me as a software developer is that they don’t even expose an API that would allow me to write an WearOS app that can expose new Tags. I’m not sure why that is, other than control. It would take the weight off of their shoulders when it comes to being responsible for the things I just mentioned.

The more I dig into the history of WFF, the more I think we’re lucky to even have Customizable Complication Slots. I think that was a compromise on Google’s part.

The bottom line is, If Samsung would’ve stayed with Tizen, and not moved to WearOS, this never would’ve been an issue. They’re transitioning from Tizen on most of their other devices as well. I guess they’re done being OS developers.

2 Likes
22

They (Google+Samsung) just sugarcoat it with the “battery conservation” and “do not wake up the power hungry main processor with mere watchface, let the economical coprocessor handle it, do not demand more stuf” excuses. When there can be a list of complications attached to your face when you customize it, and there can be list of styles and list of color themes related to current watchface made by user and list of tap to swap images, then there for sure could be user triggered integer variable stored and handled same way as such list without any consumption rise. What is the point of using “middleman” complications for a job the main watchface declaration could have handled too, had they put right links in their new format? When the watchface gets lit, there is a counter running for turning it off. Why same counter could not be used for watchface conditions? It is already consuming resources, it would just be put into more use.

3 Likes
23

I only publish her and still not a partner and not rewarded

24

I think we’re in agreement on these points.

25

Just to be a bit cynical here, if you don’t know what the problem is - it’s the money!

1 Like
26

Sorry, Facer is rewarding PARTNERS that only publish on Facer.

27
Who can apply?

Active members of the Facer Creator Partner Program who meet the program requirements and are ready to make their watch face catalog exclusively available on Facer.

Want to become a Facer Creator Partner Designer? Apply here.

1 Like