They are a lot better about telling us what they are planning than other companies I've worked with. At some places they're not even allowed to discuss current development efforts or interact with the public in that capacity at all.
We'll do our best to continue to communicate with all of you, but I'll leave the description of specifics about any future plans to Alpha Monkey. :)
I know there have been requests for more visibility into bug reports, etc. I've been actively tracking threads and making sure you get answers. Sometimes, the response may simply be that the issue has been reported and we'll get it added, enhanced, or fixed. This means that we have created a ticket in our issue tracking system, which are reviewed and prioritized regularly.
Thanks for all of the great feedback and your patience!
Getting past preview means adding features involves a little more process, so we can't be as responsive as we have been the past. With regards to seeing if activity tracking is enabled, it's not a matter of if but when.
Move Bar notifications is a little trickier. You'll notice that on Data Fields and Watch Faces there aren't any APIs that allow you to register for a callback. This is because those app types run within a limited resource context (watch faces in low power, data fields during activities). Right now the app type limitations happen at the module level over a class or function level. My thought specifically with activity tracking was that it was important to provide the API to data fields and watch faces, but adding the notifications would cross it into widget/app territory. That's the compromise that was made to bring in activity tracking.
