"SmartThings Classic" vs "SmartThings (Samsung Connect)"

[tgauchat (ActionTiles.com co-founder Terry @ActionTiles; GitHub: @cosmicpuppy)]

@Automated_House

The new app has no concept/Smart app called Routines. But it does have a unique rule builder …
But I don’t think they get exposed in the same way as routines.

Wow…

Really appreciate that SmartThings to informed us of this non-trivial difference. Though, mea culpa if this obvious from any published documentation. Remember: We were all told repeatedly that the “old” (Groovy) API would remain available and functioning for a “some time while we maintain both the new system and legacy systems”.

Concerns about Direction of Developer Workspace

Absolutely Not. Raspberry pi was just one example. When you publish code via the IDE today it’s being “hosted” by someone (SmartThings). We need to stop looking at this through the lenses of how this worked in the past. For the non-coders, we are trying to build a platform that does not force you to use code. For the developers we are trying to build a platform that will allow you reach more people in a published and controlled way without needing to pass around the source code. And lastly, No. We aren’t throwing anything in the bin overnight. There is going to be a long transition period before all of the new stuff is even fully in “production”. Then there will be some time while we main both the new system and legacy systems.

Lots of existing SmartApps (including ActionTiles) use Routines. So … available, but not compatible with the 100% recommend “new mobile App” is problematic; even if, technically, no promises were made to the contrary.

---

The Big Questions:

• Will the ability to create and run “classic” Routines be added to the new App?

• and/or How will new “Automation” routines and Scenes be exposed to execution by “new” (and “old”?) SmartApps?