Dear Samsung, why?

[tshpub]

In browsing the threads here and the app store reviews for the SmartThings app, it is abundantly that the app is not ready for primetime, so why retire the Classic app now?

(Before you suggest that I give the app a try, know that the last time I gave the app a try I lost all Internet on my phone until I uninstalled it, so I’m in no hurry to give it another try now)

[ndavis82 (Nathan Davis)]

Get ready to make the switch!

Happy to tell. As we’ve said in a number of previous posts, we’re trying to support a dual app architecture which needs to evolve. Two main reasons it needs to change: syncing everything between two distinct architectures results in excessive failure points (talking to those of you who see a delay in some devices showing up in the new app or a new location being created) and it diverts development resources, which leads to slow fixes and feature launches. This is why we’re asking you all to work with us and transition to the new app. I understand that’s a tough ask for our users who have invested a lot in very customized setups. But we need your help in making this happen. A lot have asked about why we’re moving forward without being “at parity”. The answer is that we are at parity for …

[tshpub]

Thanks for explaining your situation, but with all due respect, you’re not at parity in my book.

Take my setup as an example. I have a door sensor that, in the old app, was configured to send me an alert if it was left open for too long.
Today was the first day since the migration that the alert triggered. I got the alert via the old app. The new app on two separate devices? Not a peep.
If you were “at parity,” shouldn’t a) the old alerts have been disabled automatically during the migration, and b) the new ones enabled automatically? This isn’t exactly a Rube Goldberg setup by any means, so I highly doubt that I’m in the 0.05% of the user pool that is doing something funky.