But that is my point exactly.
“…they are prioritizing them over devices and services that would more dramatically improve their offering…” to YOU, but not to ME.
The items you would have prioritised (XBMC, Tasker, WMC, Kodi) are all useless to me.
Items you would have de-prioritised (Sonos, IFTTT, Logitech Harmony) are items I was already using before SmartThings came along and therefore are high on my list for integrating with SmartThings.
I agree that more effort should be put into the application approval / publication / installation side of things so that the connection between developers and end-users becomes seamless / invisible. (I.e. the “App Store” approach, but including all the supporting elements and processes before the store itself). Recent movement on the developer documentation front is an encouraging first sign, as were rumblings of app approvals in the wind…
One thing to bear in mind in all this, however, is that the SmartThings team has grown considerably and is likely to continue growing. Progress in one area does not necessarily mean another area is being starved of attention. You can’t complain that “they spent effort doing X when that effort should have been spent on Y” if they involve different competencies / skill-sets.
The SmartThings team is covering a fair range of topics (Hub hardware, Zigbee networks, Z-wave networks, software development toolset and documentation, cloud infrastructure for SmartApps, iOS development, Android development, WinPhone development, writing SmartApps, developing device handlers, product website, community websites / forums, Samsung skunkworks, integrating (and liasing) with third parties (Philips, Logitech, TCP, IFTTT, Aeon, GE, Fortrezz, Schlage, Kwikset, etc.), etc.).
It’s not going to be easy co-ordinating and prioritising all those moving parts and we should look to assist them wherever we can. One way we can assist is by providing constructive criticism.
I see criticisms such as the need to improve the publishing of and accessibility to SmartApps if the platform is to grow beyond the niche enthusiast market as valuable. Undoubtedly the team is already aware of this, but they need to understand the extent to which this is felt by their customers.
I see criticisms such as “they should have integrated X before integrating Y” as lacking value because:
They are typically a personal opinion readily countered by the
personal opinion of others - i.e. they verge on a matter of taste,
akin to the dreaded “iOS vs. Android” feuds which I so loathe.
They are complaining about time and resource already expended rather
than how best to expend those resources moving forward.
Rather than complaining about the integration of Sonos (etc.), which many others find very valuable, why don’t you champion the merits of an integration which you would like to see. Investigate how it might be achieved, put forward suggestions on features that would be valuable to such an integration or traps you would like to see avoided.