What's the best way to release a Smart App beyond our developer account, for UAT?

Hi. We’ve developed a prototype Smart App for a client. We’ve tested in developer mode and we’re happy that it works. What’s the best way for me to now complete UAT with my client? Is there any kind of limited release, or is the only available next step to publish for general consumption?

The app ties events from SmartThings devices in to a specific third-party system, and so is of no use to the general user who isn’t signed up to that system.

In addition, just to note that we expect to release features for client review every few days over the next few weeks, so we’re interested to know if we have to go through full publication each time, or if we can update our app.

(Finally: how do we even publish a smart app for everyone to use? We can’t seem to find a link to request publication…?)

Many thanks in advance.

Tagging @jody.albritton @nayelyz

Hello @Data_Catalyst,

Currently, the developed SmartApps are available for self-publish, you could share your SmartApp’s repository with the corresponding users so they can make the registration process and install it.

If you apply continuous changes to the SmartApp code, there is no need for them to register again the application unless the URL to access it changes.

Thanks for your reply.

Currently, the developed SmartApps are available for self-publish

Our smart app has OAuth authentication, connected by a Webhook endpoint, and was not developed with a repository. We’re professional developers, and we need to distribute the app to regular users - there’s no question of them being able to install code. Are SmartApps really only for hobby use - not a real development platform at all?

If you apply continuous changes to the SmartApp code, there is no need for them to register again the application unless the URL to access it changes.

But what if we need to include more devices. At the moment we are tracking events from four or five different sensors, but we intend to add more, incrementally.

Hello @Data_Catalyst,

A workaround could be hosting your SmartApp and provide the access URL for users to register it in the Developer Workspace.
If you modify parts of the SmartApp definition, users would need to reinstall. The Registration process should repeat in case of modifying the target URL or scopes.