Why was 1P8 released in a seemingly unfinished state?

williakz I remember reading that blog post, it was a great post! Alas, that post is from nearly a year ago and 1P8 is still a mess of feature regressions, feature omissions and bugs. I don't think people (myself included) would be so upset if AgileBits had just held off on releasing 1P8 until it was truly ready for prime time (which it is absolutely not ready for). Furthermore, I don't think people would be as upset if only the developers would actively acknowledge the plethora of issues and promise they will get fixed vs. the current non-answers of not wanting to talk about future plans (or giving really vague and frustrating answers such as when asked about 1P8 being released on the Mac App Store getting the answer "the future is a long time!")

1P8 for the desktop has been out for months now, and issues going back to the early beta still haven't been fixed. Only now is substring search available in a nightly build of the desktop (and not for mobile - which begs the question of how unified the underlying code base really is...), and that only solves one part of the larger search issue.

As it stands, AgileBits is basically using its paid users base for mass beta testing, and that is simply not okay. I would love to believe that everything outlined in the blog post will come to pass, but actions speak louder than words, and AB's actions over the past year have burned a lot of bridges and destroyed a lot of trust. I am no longer willing to give the developers a pass. Promise to fix the plethora of well documented issues, or there will be a mass exodus of users.