🚀 A new era for Facer Creator has arrived!

Announcements
142

The 7 Ultra only came in an LTE version.

3 Likes
143

BTW . On WFS we have a tag [WTHR_IS_DAY] wich works fine. My guess is that IS DAY will become available on all WFF watches . I bet Facer can reibstate it . What we will not get ls SR SS . We will have to talk with @amoledwatchfaces about that .

3 Likes
144

I did not know that. If your theory is true, I’m surprised they started the deployment with the Ultra then.

3 Likes
145

@ed.ludwig
The 7 Ultra is the premium, top of the line in Samsung’s watches that did not come with WOS 6 preinstalled. All the other 7 version watches will get it later and the 6 series even later. That is just how Samsung tends to release updates. Also, Korea and the USA are normally first before other countries.

4 Likes
146

The Galaxy Watch 8 comes with it preinstalled, the Ultra is already getting the stable rollout, the Watch 7 is in beta only in the U.S. and Korea with the full update coming, and the Watch 6 series is still waiting.

4 Likes
147

I wonder when we will see the ability to compose layers in the creator or at least have the ability to distinguish layers by color?

3 Likes
148

Even though it’s actually the same. If we get to that point, it will be pointless to have only PRO versions of features like themes or image embedding. Basic things that every creator should have access to.

3 Likes
149

We will see in time . It will be wonderful to have Grouping .

3 Likes
150

Recently, I’ve been creating more designs in Watch Face Studio (WFS), which of course has different features and languages, so I think I’ll just export files in aab format.

1 Like
151

What do you do about keystore when publishing .aab? Just use one you already have? Or do you have to make a specific one for Facer?

2 Likes
152

I send the .wfs to my watch and then look in the Build Folder . In the rod folder one is automatically created with the Default Package name . No Key necessary Well that is how I did my Test .

2 Likes
153

Yes, that’s exactly right. When publishing through Facer, you don’t need to sign the .aab yourself because you’re not releasing a standalone app to the Play Store, you’re publishing inside the Facer platform. The Facer app itself is already approved and signed, and your watch face is just distributed as part of their app. If you were to upload the .aab as a standalone Wear OS app, then you’d need your own keystore and package name.

2 Likes
154

but say you did just publish with a keystore path and a pack name, Would it matter to Facer? I don’t think it would make a difference as long as they have an .aab file.

The reason I say this is because as soon as I start a new project in WFS, I immediately save it in a folder I designate and from that point on all versions/work are subsequently save in the folder I designate. so the .aab’s in my rod_folders should not have anything in them anyway aside from a blank project.

I hope you understand my meaning and I do this to avoid the problem of losing all your work if you update WFS as I have heard that it will wipeout your build folder.

Additionally when looking in my rod_folders on some of my faces, there are 1,2, even 3 .aab’s with generated numerical names so it would be impossible to know what is in them anyway?

2 Likes
155

I understand what you mean. And you’re right for Facer it doesn’t really matter if the .aab was signed or not, since they only need the file itself to process it. The keystore path or package name wouldn’t affect their system, because they’re not publishing it to the Play Store as a standalone app it’s bundled inside their already approved app.

I also save my projects in a separate folder for the same reason, to avoid losing everything when WFS updates. The rod folder is more of a temporary build cache, so it makes sense that multiple generated .aab files appear there.

4 Likes
156

I’m glad you brought this up, I do the exact same thing with saving my projects to a separate folder. Learned that lesson the hard way after a WFS update wiped my build folder a while back.

Your question about the keystore was on my mind too, so thanks for asking it. The clarification from everyone here is super helpful. Cheers!

2 Likes
157

Grouping is definitely one of the more popular requests we see come in! The team is hard at work on this feature.

5 Likes
158

Oh Yum . We look forward to that . I would Like to congratulate the Facer Team for what they have achieved . Most Amazing .

3 Likes
159

Good point actually. It was one of the first thing I noticed when playing with WFS that you always had to have separate elements for Active and AOD, even for a change in just text colour. I assume that it is because WFF does not support the dual properties.
This will probably get added to the red flags at some point but guessing that actively functional differences get top priority.

1 Like