When is planned the next release of WFS?

Hi,
Is there an ETA for the next release of WFS? When there was still Ron as moderator, I recall he was saying a new release should come soon after 1.6.9 Beta with more tags and improvements, but months after, it seems nothing in sight yet?

I have also a request for a next version to take in consideration, if possible.

I would like to have the possibility to change opacity tags for each element inside the root/default element when you add them to style editor. Now opacity tag works just for the root/default element.

Case example:

  • I have a default image (img-A) with a condition in opacity tag (condition-A) but I want that a user has the ability to turn on/off in watchface Settings different images(A1, A2,Ax…) with different condition(condition-A1, condition-A2, condition-Ax…).

I add multiple different images under the root/default element using + Style, which I would like to select in Customization editor and each of them has a different condition based on opacity tag.

Right now in WFS you can edit Properties of just the root/default element, like Tags in opacity with a condition, and this reflects in all the other elements added on style editor.

But I would like the ability to change Tags condition in opacity for each sub element, once selected, to achieve different conditions that a user can select in the watchface Settings. Now you can’t. The sub elements of the root/default element inherit the same opacity condition.

Is definitely possible manually manipulating the XML but uncomfortable.

In the XML you can edit each element of the list, so is possible:

<ListConfiguration id=“x”…
<ListOption id=“0” …
<PartImage name=“image1”…
<Transform value"CONDITION_0"
…

<ListOption id=“1” …
<PartImage name=“image1”…
<Transform value"CONDITION_1"

The goal is for an user the ability to choose different settings for a condition that shows different images or elements in the watchface Settings.

It’s possible to implement in the next version of WFS?

Thanks

Apparently and sadly, this forum after departure of Ron, has become totally unmoderated by any Samsung representative with knowledge about WFS.

Can any WFS representative have the courtesy to answer to my 2 questions?

Thanks

The usual release date of WFS is August, but this could be slightly changed due to other factors.

Sorry, I can’t share this, but I will surely share your request with the team.

Thanks for your interest in WFS.

2 Likes

Good day @fowziya.ah,
As Google has just recently given us all a deadline of August 30, 2024 to update our watch face projects’ API target to 33, will the next Watch Face Studio release be expedited to release before August, so we all don’t have to scramble to download the WFS update, upgrade our projects, and republish them to the Play Store by August 30, 2024?

https://forum.developer.samsung.com/t/new-target-api-33-for-watch-face-when-the-new-watch-face-studio

If there is a more appropriate way to make this request, please let me know and I will take the appropriate steps.

Thank you.

1 Like

i agree with you. we need either a way to resolve to this sdk lower version issue.

OR we need a new watch face studio update to fix this issue. This issue is of urgent nature. Since few developers including me have also faced this warning on newly published watchfaces as well made in latesf Samsung Watch Face Studio 1.6.9.

The more this issue is delayed the longer it will take with less time available for developer toupdate all our watchfaces. I have more than 90 WFs to update.

I updated 30 WFs in last 60 days and as a result of this all my efforts have been multiplied with 0
Please update WFS.

This has put all my progress to a fullstop. Even if a new watchface studio is relased today it will take me minimum 30 to 50 days to issue and release updates for all my watchfaces.

Hello all,

This is Jakia from Samsung Developer Program Team.

WFS team is working on new version. Upcoming version will support Target SDK version 33 and it is planned to be released within August, 2024.

Thank you,
Jakia

Hello,
Google has set August 31st as the final update deadline for Wear OS developers. This date creates significant time pressure, especially if the new version of Watch Face Studio is planned to be released within August.
This situation can be particularly challenging for developers who have 50 or more watch faces in the Play Store. A short period of one month may not be sufficient to update, test, and publish such a large number of watch faces to meet the new standards. In this case, it would be beneficial for Google to make efforts to release the new version of Watch Face Studio earlier.

1 Like

@Jakia.Sultana, can you give us a more specific date yet? First week of August? Last week of August (I hope not!)?

Developers who are depending on this new Watch Face Studio release to keep Google from deleting their work will need enough time between your release and the end of August to update all their watch faces. If you wait to release WFS until midway through August or late August, you will be hurting many of the developers who have a large amount of watch faces they will have to update.

Is there any chance you have a stable beta version of this upcoming release that could be made available to us ahead of the full release, to give developers a head start on updating their projects?

Thank you,

2 Likes

i also agree with what you.

If only this sdk issue is fixed and a minor release for it. August update is a little too late . Will put pressure on developers who have more than 90 to update… even if released in August lot of time is requires to every watchface.