Skip to main content

Evernote: a Landscape of Experiences



I’m going to take some time out of absolutely loving Evernote for keeping me on task and organized throughout the day to talk about what, I think, is absolutely the worse thing about it.
Evernote is a completely different application on every platform and device it supports.
For a product who’s main gimmick is keeping you organized and your data synced between all of your platforms and devices, that’s sort of a really hard knock against them. The Evernote for Windows application is great, but so is the Evernote for Mac application. These are quite different, and not just in the ways that usual differ between Windows and Mac to fit the platforms well. They are just fundamentally different applications which coincidentally happen to be sharing your data.
Beyond the two desktop Evernotes, the problem only gets worse. Evernote for Android is yet another experience, with yet other features different from the two Desktop versions.
The most jarring differences between these versions are differences in the editing of your notes themselves, something that (given the nature of the tool) seems like being consistent should have been priority number 1. How am I supposed to work on my notes everywhere if my notes may be different everywhere?
Perhaps the most frustrating part of all this comes down to what is definitely the most overlooked face of Evernote from their development team: Evernote for the Web. This version of the product has, by far, the most missing features found at least in some form in most of the other versions.
This Web version being so limited is especially troubling because, would it be better supported, the differences of all the other versions would barely scratch my notice. I’d just use the web version everywhere.
Moving forward, these discrepancies are killing my loyalty to Evernote and I can’t see there is anyway I’ll be able to continue as a user much longer. Honestly, I’ve gotten a lot out of it, and I’d hoped this situation would improve. That hope is what kept me around this long. As it continues to only appear more divergent over time, not less, it seems my hope was misplaced.
I’m still looking for the replacement, but I’m going to find it (or make it) and then it’ll be “so long” to Evernote, I’m afraid.

Comments

Popular posts from this blog

CARDIAC: The Cardboard Computer

I am just so excited about this. CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer.  One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC? It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operate on

Statement Functions

At a small suggestion in #python, I wrote up a simple module that allows the use of many python statements in places requiring statements. This post serves as the announcement and documentation. You can find the release here . The pattern is the statement's keyword appended with a single underscore, so the first, of course, is print_. The example writes 'some+text' to an IOString for a URL query string. This mostly follows what it seems the print function will be in py3k. print_("some", "text", outfile=query_iostring, sep="+", end="") An obvious second choice was to wrap if statements. They take a condition value, and expect a truth value or callback an an optional else value or callback. Values and callbacks are named if_true, cb_true, if_false, and cb_false. if_(raw_input("Continue?")=="Y", cb_true=play_game, cb_false=quit) Of course, often your else might be an error case, so raising an exception could be u

How To use Sphinx Autodoc on ReadTheDocs with a Django application

Sphinx is awesome for writing documentation. ReadTheDocs is awesome for hosting it. Autodocs are great for covering your entire API easily. Django is a great framework that makes my job easier. Between these four things is an interaction that only brought me pain, however. I'm here to help the next dev avoid this. Autodocs works by importing your modules and walking over the classes and functions to build documentation out of the existing docstrings. It can be used to generate complete API docs quickly and keep them in sync with the libraries existing docstrings, so you won't get conflicts between your docs and your code. Fantastic. This creates a problem when used with Django applications, where many things cannot be imported unless a valid settings module can be found. This can prevent a hurdle in some situations, and requires a little boilerplate to get working properly with Sphinx. It require a little extra to get working on ReadTheDocs. What makes this particularly h