If you have a question that is related to WFS and the importing of .aab files for publication on Facer please try keep it here.
It would be good if there was a Separate Category . Perhaps @Facer_Official will help in this respect . Let us see what Happens .
Thank you!
Am i right that this Wiki is restricted to posts relating to the importation and publication of WFS watches on Facer and NOT other general or specific WFS topics?
It will be interesting to hear @Facer_Official opinion on the topic of how far they will support WFS
No @BIELITZ . I just had to come up with a catchy Title to get the ball rolling . You should be ranked high enough to Edit the Title and Any of the Topic text . Please post anything you feel is more on Topic here than on the Creator side . I think we have to see how it goes . I think on a WiKi you can keep posting messages and not get the notice not to . Let us see how it goes .
.
I am happy to share what I know about WFS . One thing I know is most of the formulas I have tried to port are working OK .
I think you are right but new topics wouldn’t get a title so the first line of a new topic should be a title in block capitals followed by a new (blank) line eg
THIS IS A NEW TOPIC
This the text
Why are you so hell bent on not having anything WFS related? It’s a tool, just like Notepad is in Windows. Facer Creator is also, just a tool, like Notepad in Windows. Facer Creator is not Facer as a whole. It’s a small piece. Watch Face Format is the future, no matter what the tool is. It’s all the same stuff. I’ll never use Creator, but I’ve become a presence here on Facer. Do you feel threatened somehow by me not using Creator? Are you just longing for the old ways?
Not Quite sure what you mean there my Friend .
.
OK . I think I have got it now .
IN this case I made the first Message a WiKi . So that only applies to that Message . So if a contributor wants others to be able to add to their Message they make it a WiKi as well . May be not such a good Idea . I just wanted to try something . It will be muck]ch better if @Facer_Official create a new category for us .
I am not sure a wiki is necessary. They are usually informational rather than discussions with questions.
Why don’t you just create a forum topic as usual on the appropriate Facer board? It has been mentioned that WFS is a tool that is used in creating a design for Facer to publish. It seems logical to me that Facer Community can be used as is.
Thank you .Yes there is no need for any of the Topic to be a Wiki . I was debating which Catagory to post the Topic in . I settled for General as a catch all . I think the main reason I was keen to get a Catagory like Resources / Hands is it encourages people to participate and realise this is a sharing community and it is fine to talk a bout WFS and or any Tool that will help us be Creative .
Firstly, I’m not hell bent on anything - its clear that WFS is the future. I’m just wondering why Facer, after making so much effort, expending time and resources to upgrade Facer Creator just to allow WFS creator or whatever it is called to take over.
You are, of course right Facer Creator is just a tool as is WFS’ equivalent, but there is a difference - Facer Creator is Facer’s and WFS is Samsung’s.
Secondly, Facer has allowed or perhaps better, made it possible to ‘design’ Apple watch faces in Creator. So far Facer has only allowed WFS watches to be imported into creator. Maybe in the future, it will integrate more WFS things into Creator - i dont know what their plan is.
Thirdly, once (if) Facer integrates with more WFS then its obvious things other than importing and publishing WFS watchfaces could and should be discussed here.
Fourthly, it is Facers’ decision @Facer_Official whether they make a new section here - there certainly has been enough noise to understand what is wanted.
Lastly, this is the best User Forum on the planet and the most helpful and when WFS is more integrated into Creator then the forum will naturally expand and become the greatest User Forum on the planet - full stop!
I guess I completely misunderstood your points in your comments prior to this one. Your last point is why I wanted to have some WFS visibility here. This is the greatest user community in the world!!! I’m aware of at least 30 people that frequent both forums. This is by far the best tho.
I have a question, why is it not important to have a key for Facer? Doesn’t your designs need to be signed as if in Google Play? Or is Facer the one that has the key? Curious on who all uses the rod file or who publishes with a key?
Good question . I think you only need a Key to Export the .apk file . Ed ( ludwig ) probably has a more comprehensive Answer .
I think it actually is important. It’s pretty easy to harvest a watch face APK file from a watch with various utilities. If that APK isn’t signed, it can be distributed as if it’s someone else’s work.
I harvest the APKs all the time because I can’t stand the fact that I can’t have more than one face on my watch at a time with the Facer app…and on top of that, when you change faces, you have to reset ALL of the complications. I harvest the APKs, and sideload them to my watch so they’re there permanently.
I am always a bit Nervous of sideloading Faces as I am not sure that they are not Bugged.
So what’s the difference between .aab and apk. Can .aab be harvested also? Why does 1 platform choose to use .aab and another apk? See I have alot of questions… I just load all my faces from WFS and they stay on my watch until I delete them.
That means you bugged it if its your own… lol
The primary difference between AAB (Android App Bundle) and APK (Android Package) is their role in the app ecosystem: an AAB is a publishing format used by developers to upload to the Play Store or Facer, while an APK is the final executable file that users actually install on their devices. The singed AAB becomes the signed APK after it’s compiled.
It’s an APK that already came from Facer, so I’m not nervous about sideloading it. I don’t sideload crap downloaded from the interwebz.
@kallyjeen41 & @ed.ludwig
Just as a heads up, any .apk file can be treated like a normal Zip file by changing the .apk extension to .zip. I would assume that would work in reverse also.
