@Ben I think that the community is inferring from the fact that indie apps created by lone developers leverage widgets and SmartThings does not. If a lone developer can implement widget support and the large team at SmartThings cannot, the lack of support must be intentional.
Nothing the SmartThings team has done has affected the community’s confidence in your development team’s abilities…which is a good thing. The challenge comes as a result of the fact that the community believes that the SmartThings development team has the skillset to implement a feature and that feature never arrives.
Additionally, while the platform is open, the SmartThings development team plans are a huge black box. The community doesn’t know what is coming, what will change and when. While it is a balancing act to provide insight into development plans while maintaining timeline flexibility for your Project Managers, it’s possible to categorize projects in ways that allow visibility:
Coming Soon - Projects in final testing which will be deployed in the next 3 months.
Pending - Projects in development for which no ETA is available but will deployed at some point.
Under Consideration - Projects which have been proposed by the community or internally which show significant promise.
Wish List - Projects for which the internal SmartThings team has not dedicated any resources, but could become part of development plans after other projects are completed.
Ultimately, you can’t take the attitude you did in the previous post “I think we care” and then have little to nothing to show for it. Don’t just open the platform, open your communications and your plans. To say that you care, then to expect your user community to “wait and see” about how much you care while suffering through a poor experience and limited visibility into future plans is to miss the entire point.
Currently, SmartThings plan to enable widget support is to have an end user write a tutorial on creating EndPoints, then another end user to write a tutorial to show how to leverage these EndPoints with Tasker, then have the Tasker community’s team write a tutorial to show how to deploy Widgets. Seriously? At the very least, it’s entirely possible for SmartThings to auto-generate EndPoints when new Things, Apps, and Hello Home phrases are added with the expectation that an advanced end user may want to leverage these EndPoints.
Ultimately, there are many ways to facilitate widget support. Checking in to the forums every few weeks to post an emotional defense to a reasonable perception by your customers indicates how tone-deaf your organization is becoming. Fortunately, you’ve recently been bought by a company who can teach you how to be experts in being tone-deaf to your customer’s needs. Under their expert guidance, I expect SmartThings to implement a variety of “features” that the user community neither needs nor wants which work intermittently and only serve to confuse the platform. See: Magazine View, Air Gesture, Smart Scroll, etc.