Facemaker v1.3.121

Thank you for your insight, I always like to know other people's opinions and experiences 

Just to make things clear, 90% of my customers are hobbyists.
There's a huge community in Europe and Asia regarding custom watchfaces, people who, like me, love to customize and create watchfaces. There are countless Telegram channels dedicated to custom watchfaces.
And people buy Huawei and Amazfit, because they can easily customize their watchfaces and they can't do that with Garmin, at least not until now.

Facemaker was a huge success before the Huawei european store closed, many designers made more than 5K/month, because they were able to build watchfaces that were both complex and beautiful in a small amount of time.
And yes, there are always the spammers, those trying to make an easy buck.
I won't allow just about any guy to use FM for monetization, it is only available to a handful right now.

And they'll be able to create a complex watchface for Garmin in a couple of hours... just watch the video I posted above.

I'll still provide this service to my users, those who want to monetize it will be able to, as long as they're accepted on the FM store.
Most of them have hundreds of ready made watchfaces they'll be able to easily convert to Garmin.
And the FM store will be an indexer, it won't host the watchfaces, so my users will have an extra stage to show their watchfaces, one that is not in a chaotic situation like the one you mentioned with he Garmin store.

Again, thanks for your knowledge, I appreciate it 

Have you looked at Garmin's Faceit?  You can easily create custom watch faces, and access both  native and CIQ complications.

I would never publish anything in the store unless I had buildable source for it,  To understand ERA bug reports, that's a requirement.

FaceIt is for non-developers to build their own watch faces.  You really want to try it. 

What about buildable source with facemaker?

Facemaker outputs the full source code, along with the PRG.
When the user chooses to monetize on export, only the PRG and snapshots of both the normal and AOD screens are output, for obvious reasons.
When monetization is involved, a trial watchface is created, with extra code that contacts the FM endpoint to validate the trial time and purchase status.

And concerning FaceIt, thanks, I'll surely try it!
I didn't mean to seem disrespectful whne I mentioned they were on a different league, mainly because Facemaker is much more complex and allows you to do so much more.
I never used Photoshop or any other image editor again to build my watchfaces, because I create all images in FM.

The buildable source is really a requirement if you put in the garmin app store.  Do you understand what ERA reports are?  The dev gets a crash report with a stack trace of where a problem occurred, and without the source, you can't do anything about it or even look at why it might have happened.

No problem, I can enable the source code output too for monetized watchfaces!

That won't really help, 'cause they'll not really be capable of fixing it, they'll have to send them to you and you'll need to fix the bugs, then let all of your users know that there's a fix so they'll be able to release a new version to their users...

Facemaker said:

Most of them have hundreds of ready made watchfaces they'll be able to easily convert to Garmin.

That sounds like a bunch of new spam watchfaces to me