Is it possible to mark watchfaces whose “Settings” page is not available anymore? I mean, just go through the watch catalog, open each watchface “Settings” and if you get an error 404, mark it in the Pebble Store. I have downloaded a few nice watchfaces, and their Settings page has disappeared.
Just a suggestion.
Seems like a good idea to me; would be even better to have similar reporting functions for things like whether weather still works.
Same for the Apps, too many are outdated.
Generally it would be for the best to have the current store “Marked as an Archive” where you find all of the Watch faces and Apps. The “NEW” Store would automatically contain only those Watch faces and Apps which are only recently updated (2025) and those whose full functionality was confirmed by (let’s say 10 users 
).
You see, I think there is no valid point to have 15k+ watch faces and thousands of apps if they not even partially working. Plus time to time you stumble upon ones that require payment for full functionality to work and to pay to watch face or app that has been updated in 2015 is quite risky in my opinion.
Cheer
MArtin
Also, what technologies does the web based settings page use? Can a mini-server be made to run on our phones, and the settings HTML be pulled and cached on the phone so there is no external dependency? Asking from a layman’s perspective, there may be more I don’t know or understand, so please forgive me if asking this is a stupid question.
Again, just a suggestion/query.
I’ve been asking this as well. I know enough to get myself in trouble, but not enough to create something. I’ve always wondered if one could use a hosts file in the app that would point the ip address that the settings page is trying to call toward your proposed mini-server on the phone or on your personal domain.
However, I assume that you’d still need help from the developers of those apps and watch faces because you need the HTML/code of the settings page. I believe someone on Github had tried to archive some.
Hi all, upon further reading, I discovered that there are two methods to “do” the Settings in Pebble Apps and Watchfaces. The old method was devs using their own web hosting to get the settings page up and running while the new uses something Pebble developed called “Clay”.
For apps/watchfaces using Clay, they are guaranteed to work properly today. Including those that use the “old” method (and maintain the web hosting ).
The felons we see in some apps and watchfaces not allowing us to change default settings are those that did the old method and did not maintain the web hosting for the settings.
So, I want to rephrase my original question. When looking at apps and watchfaces in the Pebble store, can it be flagged to show if it has a working “Settings” by seeing if it uses Clay (I assume, as a layman there must be a JSON file in the installer). Also, a nice sort function to the Pebble Store, where we can sort by date, popularity (hearts), or fully working (presence of Clay).
Do you guys agree, or am I asking too much here?
When looking at apps and watchfaces in the Pebble store, can it be flagged to show if it has a working “Settings” by seeing if it uses Clay
I think that wouldn’t really fully cover it, since as you note there are plenty of hosted-config watchfaces that still work! Also, it is possible (though this is fairly rare, I only know of 1 app that does it) to build an offline non-Clay config as well, it’s just kind of difficult since it’s involves squeezing the entire config page HTML into a single data URL (which is actually what Clay does behind the scenes.)
I think just the ability to flag non-functional ones would be ideal. (This could also cover other types of abandoned-web-service faces, like where weather no longer works.)
You’re right, and I hope Core looks into this, and any improvement is better than current situation. My habit is to look at the last version publish date and if it’s before 2025, question how badly I want that app or watchface. I think Core/Pebble can do better.
I think it could go like this:
Sorted!
I think that having 15k+ watch faces and apps have no value if customers come and see them non-working, I can deal with that but someone else could get wrong impression about quality as whole when you download for example 3 faces and 3 apps and half of them is broken.
MArtin