Doesn't work for Tiger. There was no warning or notice from developers that this would happen. Considering that this is marketed to people who rely on it for calendaring in a corporate environment, this is unacceptable. I just started missing meetings when it silently failed.

Before this had persistent problems with too many threads and memory being used which at some point would also cause it to silently stop working. Despite detailed bug reports and offers to spend extra time debugging this myself (I'm a developer too) this bug was never fixed.

And I have asked them repeatedly to keep us customers up on what is happening, such as when important bugs are detected and new features are released.

While not spending the effort to fix known bugs, they did have the time to add a different (and obtrusive) licensing system.

So there is no choice at this point other than to consign them to the category of incompetent and inconsiderate.

Note their last note "I estimate that we'll have something more to tell you in a week or so" was more than 5 weeks ago.