SmartThings Community

Concerns about Direction of Developer Workspace

samsungsmartthings
integration
developers

(Jody) #21

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.


"SmartThings Classic" vs "SmartThings (Samsung Connect)" App
(Jody) #22

It is required to be HTTPS


(Carl) #23

I just opened another thread about this problem of “https requirement” and the complexity of the new development model.

Am I missing something? From my point of view, I need to develop a network-hub-connected (UPNP&SSDP) device, but the documentation for hub-connected devices seems to specify it will be only zigbee and zwave… :frowning:


(Jody) #24

The documentation for hub connected devices is not complete.


(Joel W) #25

I am not a new user, but have grown my system by using the generous work of the community. What happens to all the time I spent setting this up. Let’s face it most of the Device Type Handlers provided by SmartThings are far from as good as the ones created by the community. Smartapps like Ask Alexa, WebCoRe, Big Talker etc, what happens to them. Also I am on a Mac, and very few of the work a rounds are for Mac. Windows, Raspberry Pi YES. I and many others are very concerned, that the promise of a system for everyone is going to be a pipe dream, and gone in a puff of smoke. I have so many devices that ST doesn’t support, what about them???


(Jody) #26

@joelw135 @RobinWinbourne @carl.debilly @GRClark @eric182 @Jwwhite @Danabw

I have merged all of the concerns about SmartApps, development, and publication here.


(Joel W) #27

You better have a long list and a sharp pencil ready!


(John P. Hoke) #28

I am feeling the same way - which is perhaps why other options are starting to pop up to fill the space that (from my perspective) ST is abandoning with these changes.

I am seriously starting to look at migration paths from my current set of solutions to other options such as Hubitat for this reason alone

:+1:


(Robin) #29

Most developers on here are quite happy sharing their source code and also happy when others improve upon it and cite the original author.

SmartThings has never been open source, nor claimed to be, but the community generally has been. (Bar a few aggressive and morally questionable businesses).

I see a SmartThings App Store in the making which, while making a tidy profit for SmartThings, will destroy the community spirit… what works now will require payment to keep it working in the future?

I just hope developers maintain the spirit, with open source code duplicated on GitHub… I like to take custom handlers and rearrange, re-size tiles, add extra tiles etc… if we end up in a closed source App Store, then that ability will be lost right?

This isn’t a rant @jody.albritton, and I apologise if it comes across wrong. I just need to understand the facts as I’m in the middle of a huge new build project and need to decide if ST is still the way to go.


(John P. Hoke) #30

So there will be a long transition period then it will all break when we throw it away - not overnight but over the (figurative) fortnight? Regardless it does have this feeling of "Yeah we know you all invested time and treasure to build to your needs within the processes and standards that are available, but hey … its all going to go in the crapper and you will need to redo everything or migrate to other solutions and redo everything

If that is the case, why not migrate to a fully local processing solution and redo everything … gotta do the work anyway.


(Jody) #31

No. We are not taking anything away. When I say transition, I mean that we have been building all of these new ways of building apps - hopefully people will see the value in them and use them.

Not at all.

Local Processing is one of the reasons for these changes. The current groovy based model designed for a certain kind of operation. The platform was designed for a certain kind of operation. A lot of this retooling is going to give developers more access to local processing and other features that were previously unavailable.


(Robin) #32

That’s all I needed to know, thank you :pray:t6:


(Jody) #33

No. The old way will continue to work. Your hosted groovy smartapps will continue to work. But groovy smartapps are not the future of the platform. They will still work but all of the new tooling and infrastructure is being built to be more modular by design.


[RELEASE] Resilient - My Ecobee Device & ecosystem v5 - The smartest thermostat under ST with new "comfort tips" features and Unique Integration with Echo/Ask Alexa
(Joel W) #34

Jody, I don’t want to sound repetitive, but I am not a programmer, and want to grow with the community. If everything will have to be self hosted, how does an non programmer do this. Sounds like a daunting task. Also how do we get the hosted content if we don’t program? This question is very important to me and to a large portion of the community, that depended on the hard work of others.


(Carl) #35

I’m pretty sure he means will continue to work as-is, you won’t need to move your apps/handlers.


(Joel W) #36

Yes I understand that, but eventually it will be gone. What most people don’t do is “Read Between The Lines” SmartThings is going to make this a Pay for content system. If you can’t host it pay for it. They don’t say it, but I have been in business long enough to see it coming fast. I can see the headlights of that train moving down the track.


(Robin) #37

@jody.albritton said nothing is being taken away… that’s fairly clear to me so I’m less concerned now.


(Joel W) #38

It might be clear, but you can’t improve your home system by sitting stagnate, as Smartapps get better, New devices are found etc. Which means for many what they have is what they have, can’t move on without a server or maybe programming involved, am I correct?


(Jody) #39

It takes some faulty assumptions to arrive at this conclusion, and the reason those assumptions exist is our fault.

  1. We don’t have a good distribution model - This causes you to either put someones’s github repo in the IDE or copy and paste some code. I don’t think anyone would say this is an ideal model. If we make it easier for developers to “publish” their SmartApps, regardless of location of hosting, it will be easier for you the non-developer to install said solutions.

  2. Being self hosted does not mean that “you” the consumer of the app would need to have servers or hosting. It just means that the SmartApp developer could host their solution externally on whatever equipment makes sense to them. ActionTiles does this, SharpTools does this, as do many other existing solutions that a lot of folks enjoy today. There are already solutions that do not run within the confines of the groovy sandbox.

Copy and Pasting of code is not a great User Experience. Full Stop.

For 99.9% of our customers, it’s not something they want or care to do. The end goal is to get those apps that are only shared via code on the community in front of the millions of users who wouldn’t ever see it otherwise. That means some sort of marketplace or discovery.


(Carl) #40

To be honest about this, it was one of the “turn-off” adopting the platform when I choosed SmartThings. Not paying for it means I’m totally dependant on what Samsung is doing with it. It’s a kind of Ponzi scheme… I mean somebody has to pay or the service can be closed. I’m totally ok paying an annual fee for SmartThings. It could also be something like first XX devices are free. Anyway… that’s totally another subject :-).