- Good experience, fairly regular releases, stability increasing with each one.
- Stagnation in releases, but app is in a fairly good working state.
- Out of the blue, big update comes in, application changes completely. For the worse, as it loses a bunch of features and is sporting a far less polished look and finish. I believe the new version is now an OS X native application as opposed to a webview.
- Frantic releases over the following weeks, killing some bugs but introducing more.
- Stagnation in releases, in its fairly broken state.
- This announcement.
From the outside, it looks like a case of an engineering team that decided it would rewrite the application from scratch in the native stack. Widely regarded as a bad idea. [1]
After numerous months spent burning money in refactoring and rebuilding features that already existed and worked, management pressure builds up, and they decide to release their "good enough" native version. After torturous weeks of back to back frantic releases to fix all of the complaints coming in, some factor or another (developer churn possibly) caused them to cease development and decide to sack the project altogether.
This is of course just speculation, a narrative I made up. That's how it looks like from the outside to me, but I'd like to hear from the developers inside, since I know they must be reading this thread.
I loved this application and I'm saddened to have to move away from it.