Popular Post mackid1993 1,211 Posted May 10 Popular Post Share Posted May 10 I wrote the below to feedback@evernote.com, but I wanted to share it here to see how many agree with my sentiment. Hopefully if enough of us speak out something will change: ----------------------------- You guys are iterating way too quickly, releasing too many features at once and breaking workflows with the bugs that they bring because the new features haven't been tested enough prior to release. Evernote is productivity software that people use to organize their work and lives and therefore it needs to be reliable. Things were better when you were focused on reliability than adding new features. We need you to slow down, if you read your forums most posts are complaining about bugs, new features are nice but please let them bake longer in the oven and only release them when they have been thoroughly tested and are ready, not quickly to get them out the door. Please consider a true Early Access program that is opt in so those looking to try new features can and those looking for ultimate stability can stay on a stable track. Many software vendors have a beta program, in fact most do. Right now I feel like all of your paying customers are beta testers and that is not OK. You are selling the most expensive notetaking app on the market, please start to act like it. ----------------------------- If enough of us share this sentiment and pass this along to them, maybe they will listen to us. Strength in numbers. 18 1 Link to comment
Mike P 2,946 Posted May 10 Share Posted May 10 100% agree with this. I'm also really concerned that when new features are introduceed there is a "tick the box and move on" culture. Time is not spent improving the feature beyond the basics. So we get new features that are just about useable but not a pleasure to use. Tasks is a good example of this. Well over a year before some of the things people said at the time were needed were introduced. 3 1 Link to comment
MvdH 485 Posted May 10 Share Posted May 10 I'm happy with the iteration speed, but introduce a "stable" line and a "pioneer" line or something, so people can choose which they want to be on. I a nutshell, I cannot see anyone who really needs to rely on this second brain, not agreeing with your sentiments/suggestions. 3 Link to comment
MichaelvT 20 Posted May 10 Share Posted May 10 With many developers moving to agile with CI/CD approaches, you can expect with all parties to have their new versions released in more frequent pace. This is what I call progress. If you compare this to many complaints I noticed in the past about the low frequency on updates, I believe the Evernote team deserves to be praised for this. If the level of upgrades is too high (which is understandable because not everyone can simply install the latest version from the site or run in the app), then be advised that you do NOT have to always install the update. I noticed that the in-app update does not pass by too often, but I could be wrong ( I install the latest versions from the download page), but you can skip if needed. So not to worry. 2 Link to comment
anfang 38 Posted May 10 Share Posted May 10 They could introduce a beta-testers pricing tier. A Bleeding-Edge tier that's practically the same as the Personal Tier, but $2 cheaper per month. This is to warn subscribers that the service could be subpar or unstable, in exchange for paying less. Alternatively, they could also raise every tier (Teams and Professional, except Personal) by $2 - that would go into funding additional testing and support options, while ensuring the product is on a stable line and features are introduced after extensively testing with the folks in Personal Tier Link to comment
Mike P 2,946 Posted May 10 Share Posted May 10 22 minutes ago, MichaelvT said: you can expect with all parties to have their new versions released in more frequent pace. This is what I call progress. If you compare this to many complaints I noticed in the past about the low frequency on updates, I believe the Evernote team deserves to be praised for this. I don't think the issue is really the frequency of the releases per se, but the quality of the releases and the fact that releases often break things that were working perfectly well before. I think people were hoping that taking it a little slower would mean more opportunity to test and catch these things. This in turn would lead to fewer "emergency releases" to correct things. e.g the current release needed a fix release to get the keyboard shortcut to shortcuts working again. 8 Link to comment
kkarney 145 Posted May 10 Share Posted May 10 4 hours ago, MichaelvT said: With many developers moving to agile with CI/CD approaches, you can expect with all parties to have their new versions released in more frequent pace. This is what I call progress. If you compare this to many complaints I noticed in the past about the low frequency on updates, I believe the Evernote team deserves to be praised for this. Correct me if I'm wrong, but isn't testing prior to GA part of the agile framework? It'd be one thing, as some have mentioned here, if they had a willing cadre of alpha testers (and I'm sure some folks would be happy to do that). But they're using regular users who depend on this software on a daily basis as their testers, and I don't think that would be considered good development practice by anyone. 6 1 Link to comment
Thorz 108 Posted May 10 Share Posted May 10 Absolutely agree. At the moment it feels like BS is using all the user base as beta testers. I do like some of the new features that have been implemented lately, it is great to see the product evolving forward, but removing crucial functions that have been available in Evernote since its inception without first measuring the impact this will have on thousands of users is not ok. I don't know if the removal of some of these functions happened because of bugs introduced due to the fast development cycle or the result of completely arbitrary decisions taken by someone at BS. 4 Link to comment
mackid1993 1,211 Posted May 10 Author Share Posted May 10 I don't mean iterate slower, I should clarify... big changes should go out to beta testers before they hit all users. The current system of a major release every week is broken. There needs to be an Early Access track that is a build ahead of stable or something of that sort to catch any bugs before they hit general users. 4 2 Link to comment
Feitz 260 Posted May 15 Share Posted May 15 With the host of issues that pop up every week and the necessity to manually download the latest version since auto update is several iterations behind I find it hard to use V10 for anything productive. I don't know of any other software that causes so much trouble. I can't understand why they don't release a well-tested version and - if anything pops up - send automatic fixes before new features that also don't work properly are released. How do they keep track of the multiple issues if they constantly churn out new untested versions??? 1 Link to comment
Feitz 260 Posted May 15 Share Posted May 15 Just checked: 'Latest version': 10.87.6 current download: 10.88.4 Link to comment
Feitz 260 Posted May 15 Share Posted May 15 Just to confirm my point I got this a minute ago: Half an hour of work gone... I am this close to nuking V10 again and NOT reinstalling it. Repeat on every device and find peace... Link to comment
kkarney 145 Posted May 16 Share Posted May 16 18 hours ago, Feitz said: With the host of issues that pop up every week and the necessity to manually download the latest version since auto update is several iterations behind I find it hard to use V10 for anything productive. I don't know of any other software that causes so much trouble. I can't understand why they don't release a well-tested version and - if anything pops up - send automatic fixes before new features that also don't work properly are released. How do they keep track of the multiple issues if they constantly churn out new untested versions??? I'd like to see them stop adding new features for right now and concentrate on fixing the broken ones (such as the speed of everything). Maybe send half of the dev team over to support and start clearing out that backlog. Right now, the issues just snowball because they're adding to them rather than taking them away... 1 Link to comment
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now