@Enzo_Pirrotta Thanks for your understanding. I’m very frustrated by my oversight. Never wanted this to happen. I think I had a bit of tunnel-vision while building the framework. I hope the designers will understand and we can have a good relationship in the future.
With this framework, many of their designs will cross over to these watches.
@Ken_Van_Vliet I’m the creator of this app.
There is no relation to Watchmaker whatsoever.
I want my framework to be able to create a working watch assembled out of individual elements that are layered and are controlled by data from the watch.
It’s a new framework, build from scratch.
I’ve actually haven’t seen ANY watchface creation apps before (probably because all are targeted towards Android Wear)
In this smartwatch segment, there’s an absolute void in custom watchface creation and display applications. The only one in existence is @Cronosurf_Watches , but they have no custom WF option. That’s why I’m building one myself.
I did not know your designs were limited to Android Wear / Watchmaker app.
I’ve always assumed they were watchdesigns “only”.
I guess this would be an issue for using specific watchfaces without consent.
There are already a few good watchfaces available from @Andrew_Davis as an example. He’s a very active WF designer on this community.
I’d really like your cooperation in the future, if my framework is growing, to have it accepted by your group of designers so these Smartwatches can be served with excellent WF designs.
As you might have seen from the V22 example, I can use multiple screens in a WF design either as informational screens or Night/Day WF screens.
That was one of the reasons I picked the V22, because it had an excellent night WF.
Currently I’m trying to incorporate as much system data and features found in most WF into my framework. I think I have to install?? Watchmaker to see what features are necessary to facilitate your WF-es
I’m actually glad you’re talking too me. You could have been cursing at me now…
@Ken_Van_Vliet
Yes you misinterpreted my intent.
There are a lot of WF designs available on Watchawear. They are tagged as “Gift”.
I never assumed they were Android Wear exclusive, because I interpreted them as design in general and not AW programmed.
I never used anything else than the graphical elements.
Based on these individual elements of the designs I and others started looking for ways to use them on our watches. All methods we’ve found were not satisfying the needs. That’s were I decided to learn to write an app myself that could fill all the demands/wishes.
Believe it or not I started this yesterday afternoon and got this working in 2-3 hours. I couldn’t believe I got this done so fast.
In the last hour tonight I’ve started the programming of a new WF design and I’m almost finished in 40 minutes. That’s a good second attempt for my framework.
It’s still all manual programming, but It’s my first day on the job.
In time I would like this framework to grow into a versatile app.
But I’ve got much to learn on the way.
@Ken_Van_Vliet If I’m understanding him correctly, he is trying to build an engine SIMILAR to WM but for non-Android Wear smartwatches. He only used this design as an example of how the engine could be used. I could be mistaken, but I think that’s what he means. As someone fairly new to the Wear community, before I got my 1st watch less than a year ago, I was looking into the non-Wear watches but this was the main reason I went with my old Moto - no custom watch faces.
Personally, I commend him for what he’s trying to accomplish, but I completely understand your reservations about his way of going about it. I hope I’m not intruding with this post, just wanted to try to clear things up for everyone involved.
That’s 100% true. Like I said, he definitely went about things the wrong way. Not sure if that was intentional or a language barrier issue. I still think those crooks I found on ebay should be punished for what they’re doing because you guys could absolutely charge for your designs and spend your time and effort on designing these and just let us use them and that’s one of the greatest things about the Android community as a whole. But yes, it all hinges on the common courtesy of asking permission beforehand, which it seems some people have a hard time doing.
For information…
missing/deleted image from Google+
Eventually what will this move is that every designer will be so disgusted that steals their work, they will simply stop. And then there will be nothing to feed your beautiful Android watches.
@Ken_Van_Vliet You have an interesting point.
It’s also a problem in the wording I’ve used and how they are interpreted.
I’m building a framework that uses graphical elements of watchfaces. I don’t care if they come from AW or WM or other WF designers.
I just want a method to be able to get custom WF on these Non-AW watches.
The copyright issue of existing WF is a separate matter from my goal and both should be respected. Therefore matters have to be clear if and which WM WF’s are free to use on NON-Wear apps.
I’m building a WF app, not distributing copyrighted WF’s (sorry for the V22 demo) or even monetizing copyrighted WF’s.
I can’t control others if they adapt/cross-over existing copyrighted watchfaces using my framework for their own use. Also if they want to share a WF app build with my framework, they should know that using copyrighted material is not OK.
I’m aware that with building this framework I’m creating a lot of issues with your community.
The red line in this is protecting your copyrighted works, but also trying to find a common ground to extend your artwork into this smartwatch sector with the consent of the designers community.
Here’s what I’ve interpreted from the “Gift” description:
#1: “This file is free to download and enjoy!”
I’m free to download and use it for my own use.
#2: Please mention the artist and where you found this.
I can publish (not distribute) what I’ve made with this WF on Social Media, but need to credit the designer
#3: “And It is requested, if you use something from WatchAwear, You add your work to WatchAwear.”
If I create a new design with the individual elements on WA, I must publish it on WA. Probably it’s also a good thing the credit the designer(s) of the elements
#4: “You are not allowed to add any downloads from WatchAwear to another website without permission from the author and from WatchAwear.”
Don’t distribute the copyrighted works!!
Questions:
So is it wrong if I use a WF design for my own use on my newly developed Framework (#1)?
Am I allowed to show it working on my Non-AW smartwatch to the public (#2)?
#3 - In the future we contribute back, but only in design, not programming (WM)?
#4 - No question about this.
I am a moderator of Watchmaker. I suggest people to stop using Watchawear immediately and to remove all content they feel is at risk, especially of it falls under the giftware category. @Ashley_Hansgen @Davie_Bowmore
@Kenneth_Tan_Fotograf , feel free to use any of my 200+ faces there, which are all tagged with my name. Some came out quite nice I must say, lol.
@Ken_Van_Vliet About the Snyper:
That’s one of the in my opinion bad methods of creating custom WF.
These smartwatches have an XML file and an image container. They unpack the APK, rename the filenames in the XML and exchange the images in the container. Then repack the APK and install it on the watch. This add the WF to the preinstalled list of WF’s on the watch.
Drawback is that it only allows faceplate, hour, minute and second hand. Nothing else. Also all the hands have to be dead center WF.
I’ve never tried this method, because it’s lacking.
Looking at the Snyper post, the author posted the artist name, but possible copyright rules would not allow him to post the APK.
@Ken_Van_Vliet If anyone is making a profit here off of Watchmaker faces, please send names to the moderator team for review! @Michael_Palombi
Until further notice I’ve removed the APK on request of the artists.
I hope in the future we could get the authorization to publish it again.
Wow - just seen this now.
Can I get a status update of where we are now?
Has there been any kind of resolution here?
Thanks @Jeff_C for stepping in. This Community has strict rules about using works from other sources and we enforce them. I am sure that this was a genuine mistake by @Kenneth_Tan_Fotograf and it seems he has taken steps to fix the situation - as you would expect.
@Ken_Van_Vliet1 , @Michael_Palombi and @Cyrille_LE_RAY - please let us know if we have any breaches we are unaware of where permission was not sought or granted.
@Pablo_Eleven_Pablo11 I’ve been talking to Ken van Vliet explaining that I’ve used the V22 as a template for getting the framework tested for my new custom watchface app.
I’ve already removed the APK’s and asked them to consider granting my app to be used to enable non-Android Wear users to build CWF from their designs. There are also a lot of other sources to get designs, but copyright has to be an issue if the APK is going to be published.
In a response I mentioned that ANY Android Wear WF can now be converted to my framework and that wasn’t received well.
I had to explain that I wasn’t inviting people to steal WF from them, but I just wanted to make clear that with my framework all the features that are available for Android Wear WF can now be designed for non AW smartwatches.
I hope my honest intent for building this app is more clear.
@Pablo_Eleven_Pablo11 p.s. this thread is one for the history books.
Already almost finished with another watchface. WITH permission from the author. Full post will follow with APK when I finished the touches 
@Kenneth_Tan_Fotograf actually any Wear watch face can be dismantled and re hashed to work on just about any face engine if you know what you are doing.
I think the main issue here is that some of these very good face designers make a living at this and rights / permission has to be sought.
Now you know why all the moderators here make such a big deal about copyright. This is a prime example. Word gets around very quickly in the smart watch world and we have to stand by our rules for a very good reason.
These guys are considered our colleagues and their work deserves respect.
I fully understand that this was a mistake on your part because I know that you do actually comply with the rules on a regular basis.
Yes, that’s what I wanted to make clear. I’ve made a mistake publishing it as an example of the new WF app creator. Therefore I’ve removed the APK.
Copyright AND permission has to take precedent
@Ken_Van_Vliet You’ve asked if I could get the leds in your V22 to work.
The answer is YES.
Yes, I did it before in Zooper. (I’ve used V22 always as my testcase) In Zooper I used a sliding mask to dim the leds.
Yes, in my new framework, I can turn individual leds on and of as I like.
Last night I’ve build a new (with the authors permission) watchface, It has on the left 2 dimmed leds. if the watch goes under 25% I light the left one op in red.
If the watch is charged the right one turns on yellow/orange and when charge is >98% the yellow led turns green. (Actually it doesn’t, a new green led lights up over the yellow one.)
So looking at the V22 design, the led bars could be changed into small led droplets and turned on individually. (That’s just a design observation I have)
In Zooper engine, the left was battery remaining and the right was Wifi strenght.