I spend a good amount of time on this site reviewing native text editor apps and I do so for good reason; generally, they simply work better, are often more stable, and they allow you to save/edit your work in a more convenient fashion via key commands (command S is way quicker than hunting and clicking a save button on a web page’s UI, for instance).
That’s not to say there isn’t a place in my workflow for web apps. I do occasionally use the web-based counterparts to the native apps I have at my disposal, but that usually is only if I am not at my personal computer. In short, if given the choice between Evernote on the web or Evernote on the Mac/PC, or iWork’s Pages on iCloud.com versus Pages locally, I’ll always go the local/native install route.
Don’t get me wrong. I love the idea of web apps becoming the norm in the (probably very near) future, but up until this year, there really hasn’t been anything I’d have taken a chance with writing a post or short story in. I don’t think I’d ever trust long-form writing to a cloud-based service, but short form? Definitely, if something captured my fancy.
And it just so happened that an online editor did.
Editorially.com accomplishes so many things well that I am starting to wonder if they jacked into my brain specifically.
Editorially is a web-based text editor app for writing on and for the web (or offline too as it turns out, more on that below). Aside from a pleasing and intuitive UI, it’s feature set is what ultimately bowled me over. Here’s the laundry list of things that you get when you sign up for an account:
.markdown) and it’s even more robust in the export category allowing you to export to many file formats including .html, LaTeX (
.tex), Rich Text (
.rtf), Word (
.docx) and even ePub (!?!). I do wish there was a PDF option but, frankly, I’m shocked a web app can do all of this already. That all said, the developers at Editorially are cooking up even more export options in the future and I can always export locally and print to .pdf easily enough.
[gallery type=“thumbnails” link=“none” ids=“2221,2216,2225,2220,2223,2219,2224,2218,2217”]
As amazing as the above list of functionality is for me to recount, what caused me to pause and smile the most whilst using Editorially was it’s ability to make me pine for the functionality and usability found in a web app, to be in my native apps. If you write in Markdown, Editorially is a no-brainer. Hell, if you simply write for the web (or simply write), there is no reason why this couldn’t (and shouldn’t) be your go-to editor. My wife and colleagues and I use this to collaborate and edit each others work. Furthermore, I am not ashamed to say that I use it sometimes just because it’s a joy to use. It represents a paradigm shift in my eyes. I really do think it’s the future in many ways. In fact it wouldn’t surprise me at all if local installs of Office suites are extinct in a couple of years after using Editorially for a few months.
I wouldn’t have thought that a year ago, but I do now.
Clearly I’m smitten with Editorially and all they’ve accomplished. But don’t take my word for it. Go and sign up and give it a spin. At the very least I think it will change your stance on what web apps are capable of today, you sure can’t beat the price (spoiler alert: it’s free) and at best, it’ll give you a very capable alternative to mix things up in your writing workflow. I love it and I am willing to bet that you will too.