Https://graph.api.smarthings.com Failed to load devices

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

@prempoint

What does “officially published” mean technically?

It means they get to appear on this “SmartApp MarketPlace” screen of the SmartThings native mobile App, without remuneration of any sort (plans for a payment system like Apple App Store or Android Play, have effectively been abandoned).

---

Publication requires a submission through a review process with nebulous criteria: The documentation and process are improving, but the processing queue is up to several months long; repeadtedly if a SmartApp needs to be resubmitted due to a rejection or even a hot bug-fix.

http://docs.smartthings.com/en/latest/smartapp-developers-guide/submitting-smartapps-for-publication.html

---

NB: Acceptance and publication of web services SmartApps does very little to increase their security. The submission process does not require an audit of the service provider’s external services linked to SmartThings. For more details, please read and contribute here:

SmartTiles (& "other" External Services) Security

Continuing the discussion from SmartTiles Dashboard 5.4.2 - July 13 (www.SmartTiles.click): Hi John, @625alex may add details in his own words, but I’m providing first-line support while “Version 6” of SmartTiles is under development (no release date announced), so here’s a start to help put this in perspective. Version 5’s source code also open for a while and was reviewed by various Community Members, so they can chip in as well, and, the fundamental OAuth security model utilized is a fundamental piece of the SmartThings Platform. First of all, there’s no value to me replicating the official SmartThings Documentation of the architecture involved (“Web Services SmartApps”). In order for you to fully understand the security model, I must first point to the Documentation and assume th…