Just use Xcode

Any reason why you're running something no longer supported and expect it to work still?

No one has had this issue because Apps are implemented on the watch with the watch version of the iOS UI and functionality. There are no shortcuts.

Please post your question on the unity developer forums over at unity.

Yes, these are different design paradigms see the focus example for when there is a change in data and how this is used to trigger a UI element focus under accessibility. https://developer.apple.com/documentation/swiftui/creating_accessible_views/

Is the application yours?

If the app is not yours, it's none of your concern how the owner opts to beta test their application.

Purchase an MDM solution if you want to manage the settings for corporate devices; what you're asking to do is most likely on an App level and not a device level using the APIs mentioned for apparent privacy and security reasons.

How else do you propose Weather Apps present the information? How else do you propose Wendys and Mac Donalds make their burgers? And for the records, the Apple Weather App doesn't use a tab bar controller. Something tells me you're an ex-disgruntled employee of Luni. How else would you have known to point out something like this? It looks pretty petty on your part.

Right now, you're running in O(n^2), and as your screen size gets larger, 1080p vs 2K vs 4k vs 8k, the lengthier your runtime becomes. Moving this to Metal or OpenGL will be the better option since GPUs are faster than CPUs. Explore changing from for loops to something recursive. The BGRAPallet and the pixel buffer ptr should also be the same size, or the first N BGRAPallets are processed, then you're left just updating the position 0 of pixalBufferPtr for another million plus cycles.

objectToUse and nameToUse of MyView should be a Bindable<Object> and Bindable<String> parameters to a pair of matching local variables, so when a data change occurs, it will trigger a UI update. You should also use return in each case.

You cannot use @EnvironmentObject var context: TrimmedContext outside of a View. Remove @EnvironmentObject from the property wrapper. Change  @StateObject in TrimmedView to @EnvironmentObject

You cannot use @EnvironmentObject var context: TrimmedContext outside of a View. Remove @EnvironmentObject from the property wrapper. Change  @StateObject in TrimmedView to @EnvironmentObject

Report this here: http://bugreport.apple.com/

Give it some time, after the welcome party is over it will settle into its actual spot after the curiosity is over. It's also too early for any analytics.