Yes, but what’s the point to install so early and buggy release it if you don’t have an app to test and you only have one watch ?
Oh come on! This is the watchOS 26 Beta Thread. in Every. Single. Beta. Thread. someone takes it upon themselves to tell people they should have a backup, not use their primary device, blah blah blah. It's as regular as Christmas.
No one doesn't know that!
There are people who want to try the new thing. What's wrong with that? If you don't, that's fine, but hanging out in a beta testing thread is an odd way to show that.
More importantly than the opinion of people in a forum is that
Apple has changed its view on this. It used to have a much more protective approach but given that literally anyone can install the DPs, it has obviously decided that benefits it gets from widening the pool of testers outweigh the risks of support calls. (Incidentally no, I don't believe you can get support at an Apple Store, and I don't think you should be able to. Apple provides feedback mechanisms, and you should use those. Them's the breaks. What's downhill of choosing to apply a DP is you should get comfortable putting on the big boy pants. Other opinions are available, etc.)
Now, for the record, I do have a developer account. But this is actually a
perfect example of
beta testing doing exactly what it is supposed to!
People with Hermès watches represent a small subset that likely would not have surfaced in any appreciable number, if at all, of developers keeping watches purely for testing. Why would you get the watch with a fancy strap when "everyone knew" that this was "exactly the same" watch internals as the Sport and regular steel models? You may remember this informed criticism of the Edition models: who, went the argument, would spend so much money on something functionally identical to the cheaper model?
But, it turns out the firmware differences associated with with custom watch faces likely are the differentiator, and this has very quickly — and more to the point,
efficiently — been identified as a problem. Who knew? Evidently, not Apple! So, this group of watches which by the way also represent customers willing to give Apple more money for "exactly the same thing" and so are presumably a small but rather attractive demographic of people self-selecting to be on the wrong side of price discrimination, would not be tested. When the release was pushed to the normies, how would that go? All-but bricking every Hermès watch that got upgraded to watchOS 26? It would be a PR fiasco! Instead, within a few hours, Apple knew that there is a small but quite serious bug — and the Feedback app tells us so. The variables will be whether Apple thinks this number of affected watches is worth a quick patch, B3, or maybe that's already locked and we'll need to wait for B4.
This is the beta program working exactly as intended.
And as to the forum: numerous people have submitted bug reports, and through this very group I learned this from DanRyb:
Have you tried putting on low power mode? Do it for one of the day options, because otherwise it turns itself off. I got mine charged to 100% after I set lower power mode to leave on for like 3 days lol. I powered the watch off in the meantime.
I might have got there myself, but this was faster. And this is the workaround: it's not a fix but will render affected watches usable suboptimally for now, but more importantly, be able to get sufficient charge to be patched or receive a subsequent beta when released.
So that's the community working: we established a problem, hopefully warned a few people off, collectively escalated in sufficient numbers to Apple that the bug is on someone's to-do list to investigate, and we know how to get ourselves into a position where this is recoverable. And all within a few hours. I'll take the win.