If you could do it all with rules I wouldn’t have created the app. I also don’t agree that comparing ADT Tools to webcore makes any sense.
The only item i found that smartthings could trigger an event was the alarm changing states. That is actually how this who tool started as a enhanced method to send notifications when the alarm changes from one state to the next. Beyond that you can not create routines to do anything with the alarm.
The sensors are exposed, but to trigger a action with a sensor is allot different then doing something with sensors based on alarm state. I could easily create a routine to turn on a light if the front door is open, but telling it to do that and turn on a siren when the front door is opend and the alarm is in Armed/Stay mode is not possible.
You are right that my app doesn’t trigger ADT Alarm events to their call center, but that is never what it was intended to do. The Non ADT activity was always in my mind viewed as a stop gap for users as a migration method, or simply to full fill the need based on what they already had. The setup with non dual branded sensors with ADT Tools and the Alarm panel is likely still better then SHM with those same sensors.
Comparing WEBCORE to a smart app is a bit ridiculous. Webcore is a great tool for complex rules, but is too much for some people. It also creates another integration point that can fail. Plus you basically have to code your pistons. The coding may be done in a way that is easier for many users then actually writing in Groovy, but in many ways a piston is just a mini app running on another cloud. I also don’t know of anyone that has coded the functionality in ADT Tools into Pistons. I am fairly certain it could be done, but i have never tried it or have a need for it. I also don’t know if all of the values associated with the alarm are visible to Webcore.