Evernote’s desktop apps get integrated reminders and a task list, no love for mobile yet

Evernote will be just fine, despite Google’s recent announcement of a new note-taking app called Google Keep, currently available for the web and Android. Keep allows for text, audio, and images to be added to a single notebook and synced between the web and Android devices. You can even add stuff via Google Now. It’s neat, but it’s no Evernote killer.

The two products cater to very different use cases, and Keep will not be able to replace Evernote for its core customers. Evernote had 1.5 million premium subscribers in November 2012. At 45$/year, that’s around $67 million annually, and the number of subscribers has been rising for years.

It doesn’t make them profitable, at least at the moment, but it helps. Coupled with Business accounts and other endeavors, Evernote isn’t worried. For those premium users, who pay because they make the most of Evernote’s vast feature set, Keep won’t be good enough. And I suspect that even if every user of Evernote’s free tier left the product, Evernote would hardly notice from an operational standpoint (if anything, operational costs would decrease).

Instead, makers of task management apps should be concerned. Google Tasks is as neglected as Google Reader was, and we all know what happened to Reader. Keep looks like an elegant upgrade to Google Tasks, and while Evernote has hinted at its own task management solution, I don’t think the future of their business will depend on it.

It’s worth remembering: there just aren’t as many zero-sum games in the apps and services spaces as many, especially in the tech press, would have us believe. Design, feature set nuance, and adaptability to users’ current workflow all allow for multiple apps to be successful in the same space. The Keep/Evernote dichotomy is no different.

This article was adapted from a comment I left on The Next Web’s post about Keep.

Whitson Gordon finally figured out Evernote

Evernote CEO hints at future task management integration

$85 million round by Evernote

IFTTT CEO Linden Tibbets, in an email to users today:

[ … ] on September 27th we will be removing all Twitter Triggers, disabling your ability to push tweets to places like email, Evernote and Facebook. All Personal and Shared Recipes using a Twitter Trigger will also be removed.

IFTTT is everything Yahoo Pipes could have been and I’ve been using several Twitter triggers for a long time, to do things like save my tweets to Evernote and add favorite tweets to Instapaper.

My “Twitter” tag is becoming so littered with the company’s user-hostile decisions and their unfortunate consequences that, soon, it will make more sense to post something when and if they ever put users first again.

Here’s the full email from IFTTT’s Linden:

Dear joeross,

In recent weeks, Twitter announced policy changes* that will affect how applications and users like yourself can interact with Twitter’s data. As a result of these changes, on September 27th we will be removing all Twitter Triggers, disabling your ability to push tweets to places like email, Evernote and Facebook. All Personal and Shared Recipes using a Twitter Trigger will also be removed. Recipes using Twitter Actions and your ability to post new tweets via IFTTT will continue to work just fine.

At IFTTT, first and foremost, we want to empower anyone to create connections between literally anything. We’ve still got a long way to go, and to get there we need to make sure that the types of connections that IFTTT enables are aligned with how the original creators want their tools and services to be used.

We at IFTTT are big Twitter fans and, like yourself, we’ve gotten a lot of value out of the Recipes that use Twitter Triggers. We’re sad to see them go, but remain excited to build features that work within Twitter’s new policy. Thank you for your support and for understanding these upcoming changes. If you have any questions or concerns, please contact us at support@ifttt.com.

Linden Tibbets IFTTT CEO

*These Twitter policy changes specifically disallow uploading Twitter Content to a “cloud based service” (Section 4A https://dev.twitter.com/terms/api-terms) and include stricter enforcement of the Developer Display Requirements (https://dev.twitter.com/terms/display-requirements).