Hopefully including a real fix for voiceover navigation.
As far as focusing on the basics, I regard the voiceover failures as a "canary in the coal mine" for the mobile app as a whole in two important regards:
One) Testing Methodology
If the mobile app is broken 100% of the time for a basic feature in a way that can be demonstrated with a screenshot and there is an official announcement that that specific problem has been fixed when in fact the same screenshot shows that it is broken in the same way, there's a problem with testing procedures. Even with the concept of testing itself.
From the Canary standpoint, it looks like you are testing the fix rather than testing the feature. That is, you are testing from the programmer's viewpoint rather than the customer's. It's like checking to see if a word is spelled correctly without checking to see if the sentence makes sense.
One of my old professors used to say "The hardest thing to remember is what you didn't used to know." Meaning it's really hard to look at a page in a book and see it the way it looked to you when you weren't quite sure which letter was the "b" and which letter was the "d." We see this time and again with the mobile app.
It has really powerful features, but it's almost impossible to find them unless you already know that they're there and you already know what they do.
Two obvious examples which people ask about all the time in the forums are grouping devices so that you can schedule several lights together, and the classic "I just got home" scenario where the porch lights turn on for five minutes and then turn off again automatically.
Can you do both of these with SmartThings? Absolutely.
If you don't already know how to do them, can you discover that functionality easily? Not likely.
The Canary aspect comes in here because trying to find things with broken navigation becomes that much harder when the navigation itself obscures what is there.
I understand if fixing accessibility is not that high of a priority. However, with regard to a focus on the basics, I would respectfully suggest that defining discoverability as a basic would significantly improve the usability of the platform for many markets.