If you have any questions for Alex and Robert, please add them to this thread. We have many discussion topics about various issues and topics throughout the community so please keep this thread to questions only.
I would like to know if SmartThings is going to adopt an internal MFOP target (maintenance free operating period measured in days, not percentage of transactions) as a measure of reliability. It doesn’t have to be published. But I don’t yet get the sense that the team’s concept of reliability is the same as a typical consumer’s.
Could you give us a Smart App State of the Union? I’m curious if the current model–which relies heavily on voulenteer developers to create and support key functionality–is working as you all intended. Or if there is some larger vision that moves to a sustainable (paid) App Store, or moves more key functionality in-house.
I’m thinking specifically of rules engines (Smart Rules, Rule Machine), voice interfaces (Alexa, HomeKit), dashboards (SmartTiles), and the numerous community-developed device handlers. All of which seem like integral parts of any modern home automation system.
I would like to have some updates on SHM and when functionality such as Lights & Switches or Doors & Windows is going to make a reappearance. Would also be nice to know how the platform performance improvements are coming along, been very sluggish the past few days for me.
On my side, I’m posting the same questions that I posted in September 2015:
1) What is the ST technological roadmap as per the community developers perspective?
As developers, we don’t have any clue where ST is heading…
a) How SAMI & Artik will affect the development platform?
b) Which UI capabilities (ex. access to rooms) will be available in the coming months?
c) What is the vision for local processing? Will developers be able later to use local processing for their own device handlers and smartapps? If yes, how certification for local processing will work? What are the best practices (if any)?
d) App store: yes, no, maybe? And, if yes, when?
2) When a “real API” layer will be available?
What I mean by real APIs is some API and security layers that don’t require to explicitly specify each device as a REST endpoint.
3) How do you envision the developers beta program in the short and mid terms?
The beta program was supposed to allow developers to test new ST app versions, and new products.
So far, there has not been a lot of initatives in that regard.
And, I will add this one:
4) How ST will truly support its community developers?
In the past, ST support has sometimes blamed the ST community developers for issues affecting
the platform and asked the end users to use the stock integration devices instead.
I’ve experienced myself this ST behavior as I’ve developed many custom devices (such as MyEcobee, My Neur.io and My Automatic devices). I can tell you my code is as good as any stock ST device (and often brings much more features).
(ActionTiles.com co-founder Terry @ActionTiles; GitHub: @cosmicpuppy)
Based on your website, and a few other developers who have added external mechanisms for actually selling their SmartApps and/or Device Type Handlers, I’m glad you included point (d) above.
While there will always be a certain amount of code and mentoring provided by Community developers free of charge, the effort to provide ongoing development and Customer Support requires the incentive and sustainability of revenue. It is difficult to get trust and market exposure without a “SmartApp store”.
SmartThings’s Customers need the opportunity to decide for themselves if they wish to be SmartApp Customers too. The SmartApps we currently share, and would like to sell, add significant incremental value to the product / platform. We need acknowledgement of this with firm progress on the concept and/or other genuine support.
(www.rboyapps.com - Make your home your butler!)
I have questions that have been begging answers for a while now:
ST has been claiming for a while now that they have an all new “redundant” fail proof scheduler called Ticker. Why is it still losing schedules consistently? Is there a fundamental flaw in the ST architecture or is a gap in the SDLC processes? What’s the solution?
@slagle has been pushing this and claiming that ST’s going to get their act together for uniformity in the UI across Android and iOS. If I were to go by the latest Android and iOS releases, it seems that things are going further apart. So is there really a plan to get it converged, if so how? Is there a unified code base? Is there a unified test plan or UI design team / UAT team?
I’m asking these question because I’ve heard many promises but seen little that I can claim has “moved” the needle in a significant manner.
I really would hope a Developer “Discussion” would be just that, a discussion with the community. I certainly hope this isn’t just another heavily moderated one way talk.
Please try to hit the critical questions and also respond to follow up questions in the chat. Lots to cover on Security / vulnerabilities, progress (or the lack thereof), promises of open sourcing SHM, video core, etc.
What is SmartThings doing to change the way it supports its community developers? And when?
Question: What with all the issues SmartThings experiences and to this day still experiences, from the app, to the hub and to the platform, where some changes made in one place seem to often affect other areas (sometimes significantly), ignoring the technical aspect of it, there seems to be a (maybe significant) disconnect between departments at SmartThings,
Would you say there are issues between departments, communicating and collaborating effectively and if yes, what are you doing to fix this.