Hopefully they'll rewrite Shazam's Apple Watch app using the private first-party APIs so that it actually works rather than randomly crashing 50% of the time.
The state of third-party apps on the Watch is awful. It usually takes 10 seconds for an app to start on a Series 2, and sometimes they just get stuck on that loading screen. If you manage to get an app running, the UI library has ridiculous bugs like accidentally enabled screen rotation where turning your wrist flips the content by 90°. (Unlike a phone, there's no reason at all for a watch to react to orientation changes.)
I could sort of understand these deficiencies for a hurried 1.0 product, but it's been three years and it's still this bad. There's no API for watch faces either. I get the impression that Apple truly doesn't want third parties on the Watch at all.
If they "truly" didn't want third parties on the Watch "at all" they wouldn't have released the watchOS SDK or made it possible to write, build and publish watch apps on the App Store.
This wouldn't be the first time that Apple releases an SDK, decides internally it's actually not something they want to support, and then just leaves it languishing in a semi-broken state because it would be too much trouble to cancel it outright.
The state of third-party apps on the Watch is awful. It usually takes 10 seconds for an app to start on a Series 2, and sometimes they just get stuck on that loading screen. If you manage to get an app running, the UI library has ridiculous bugs like accidentally enabled screen rotation where turning your wrist flips the content by 90°. (Unlike a phone, there's no reason at all for a watch to react to orientation changes.)
I could sort of understand these deficiencies for a hurried 1.0 product, but it's been three years and it's still this bad. There's no API for watch faces either. I get the impression that Apple truly doesn't want third parties on the Watch at all.