Careful with the clipping of stuff you quote from me, Scott, please…
I said: [quote=“tgauchat, post:14, topic:29731”]
Many of the technical problems are complete jokes …
[/quote]
There’s a tremendous fundamental portion of SmartThings that is amazingly architected, engineered, and implemented. It is a complex problem overall, particularly in offering a public API.
It would be an interesting (and laborious!) exercise to review the entire system from various angles … conceptual architecture, operating environment, APIs, client platform, IDE, app design, etc., etc…
Some of these are very strong and still getting better. Other areas were perhaps not as strong a foundation as necessary for scaling and flexibility, and that legacy foundation has proved to be difficult to shore up – when those portions probably ought to be completely replaced.
That said, there are absolutely some parts of the system that are incomprehensibly awful (with apologies for being being terribly blunt here).
Most of these “bad parts” are really little things (I gave the Android picture scrolling as an example – not to pick on anyone) … but I’m not judging … I’m saying I cannot comprehend how that tiny but noticeable shortfall was not recognized nor fixable before release.
Picture Steve Jobs storming around a conference room asking why the font size on a certain page isn’t scaling with everything else. Apple fusses over the sound that a mouse makes rubbing against a table top when they changed the weight of the mouse for a new battery type! That’s post-Jobs … but it shows an attention to detail vastly different than SmartThings.
As for bigger issues like the instability of the scheduler and lack of migration tool upon Hub V2 launch… That’s what I refer to as lack of management commitment to resolution.