“I will see you again in 25 years…”

Twin Peaks was by far the most formative TV show I have ever watched. So damn much of my young imagination was nurtured and grown in that beautifully dark and bizarre world. For me it was a gift, and now another mini series? Written by Frost and Lynch with all episodes directed by Lynch himself?

I honestly can’t wait for June, 2016. Can’t. Wait.

Non-techie post, I know, but I was so tickled to see this news today.

Tips: Planning a New Website With Scapple and Scrivener

Planning the content layout of a new website is a daunting task to say the least. You always want your content to be easy to find, logically laid out, and as clean as possible navigation-wise. A new site (or a redesign of an old one) is a great opportunity for you finally to wrangle your site’s content and make it more accessible for your readership.

To do this, you need a plan of course and, for me anyways, I tend to go the visual route.  Luckily, you don’t get much more visual than Literature and Latte’s mind-mapping software: Scapple.

It’s All in the Bubbles

There are a ton of different ways to visualize a site’s content layout in Scapple. I decided to keep mine as simple as possible, but you can certainly tweak it to fit your tastes.

For the title of the document, I simply put the name of the site. Below that, I put a bubble where the top banner is going to be, labeling it as such. Then directly below that, I place individual bubbles for each horizontal navigation tab, labeling them individually for what each tab was going to point to (“Home”, “About Me”, “Contact”, etc… ).

Next, I create a vertical line of square bubbles going down the right side of the content area, roughing out where a right column full of widgets would be. If you know what the widgets are going to be, feel free to label those as well. Otherwise, I just labeled mine “Widget 1, Widget 2, Widget 3…” – you get the idea.

After this, I place a big bubble in the middle of the layout that represents the main area where my content will be displayed.

Last but not least, I frame it all out with a bubble at the bottom that runs the width of the design for the site’s footer or colophon.

Here’s what I ended up with:

finished layout

KISS: Keep It Simple. Seriously.

Use your first draft of this document to quickly get your ideas out and in front of you. Once it’s roughed out, you can tweak it to be cleaner visually 1 or label everything differently so that it translates better for you at a glance. Above all though, the goal of this document should always be simplicity.

By keeping the document intentionally simple, it affords you the luxury to drag and drop these blocks around, resizing them to accommodate new ideas and layouts. I guarantee that once you get the basics fleshed out in this document – the core bits of content that you must have on your site – the process of manipulating the layout becomes WAY less of a chore and might even become a little fun (gasp)! So yeah, simple, simple, simple.

Now that you’ve got your layout nailed down, it’s time to fill out the content that is going to go in these bubbles.

This is where Scrivener comes in!

Old Hacks That Still Work

The approach I used in my post, blogging with Scrivener, can also work like a charm here! Now that you have your content blocks set up in Scapple, all you need to do is assign content to the sections that need it. Luckily, Scapple and Scrivener play so nice together!

I start with a blank project (or choose whatever template you like) in Scrivener, again, using the name of my site as its title. Then I immediately drag and drop my Scapple file into the “Research” folder in the left column in Scrivener renaming that folder “New Site Layout”. This way it’s always easy to reference moving forward.

With that all in place it’s time to wrangle your content.

folder-structure

Every Folder is a Section of Your Site Layout

sectionequalfolders

In my case, I had a “Header/Banner Area” section, a “Horizontal Navigation” section, a “Right Column” filled with widgets, a “Main Content Area” section for my content, and “Footer/Colophon” area for any information I wanted at the bottom of my site.

Since these are all definable areas of my site that will have content in them, I go ahead and create the following folders in my Scrivener project:

  • Banner
  • Horizontal Navigation
  • Right Column
  • Main Content Area
  • Footer/Colophon

These folders don’t need to be in any particular order at all, but I like starting from the top of my site and listing these sections out in the order of where my eyes naturally navigate across the site layout itself.

Now that’s in order, it’s time to fill those folders!

Every Page is a Block of Content

pageequalscontentblockFor my content I only use the text/Markdown that I want for each of these sections of my site. But you should feel free to drag whatever you want into these pages – pictures, PDF’s, etc… whatever you’d like. Just don’t make it confusing or cluttered. Again, keep it simple.

So for the “Banner” section I add the text and byline that will go in front of the banner image. If you don’t want text? Drag the top banner image into the page for reference.

For the “Horizontal Navigation” section, I add a page for each tab in my layout. In each of those pages I put in the text that I want the page to display. So the “About Me” page contains all of the text that I want to display on my “About Me” page. If the tab is a link to somewhere (as with the “Home” tab), I make sure that, that that information is written plainly in that page. If a tab links to something more form-like (as with the “Contact” tab), I list that info there as well, giving the fields that I’d like in the form along with what is required info when the visitor clicks the “Send” button.

I use the same methodology above for my “Right Column” section as well, giving each widget its own respective page. In those pages are descriptions of what each widget does along with formatting needs.

The “Main Content Area” section is more than likely going to be dynamic so there’s not much to add to this page other than its description. However, if your site is going to be filled with predominantly static content that rarely changes, than feel free to add whatever this page will contain. Tweak all of this to fit your site’s needs. It is important to remember that this is merely a guide/example of what you could do. Not what you should do. Do what makes sense for you and your project.

For the “Footer/Colophon” section I just add the blurb of text that I want showing up statically at the bottom of my site, regardless of where I navigate to.

Lastly, Don’t forget to save! Scrivener does a bang up job of backing up your work automatically, but when the thought flits across your brain – save your project.

corkboard

Why I Like This Approach

I’ve built a ton of sites for clients and myself over the years and I can’t tell you how many times I have finished a design, handed the client the keys, and the site laid dormant for months 2 while they gathered up the strength, time, and patience to tackle their own content.

Do you need Scapple and Scrivener to pull something like this off? Of course not. There are a lot of alternatives out there to choose from. I just chose them because they are powerful, intuitive, easy to use, and play well together. That and the idea of this nebulous task being collected, organized and bundled up into a single .scriv project file is tidy and easy to keep track of.

It also gives you a HUGE headstart on your new site design and since it is separate from your site’s file system, it is a very effective back up of the structure and content of where your site started. This is a huge win if you ever have a catastrophic failure and somehow loose your site and all of its content. With this, you’ll always have a copy of that gigantic “step one” to fall back on.

It’s also something you could easily hand to a designer who you’ve hired to build your site. Instead of saying “I think I would like this…” you’ve already taken the time to create the site that you need so you can say “I really appreciate your help. Here’s what I’d like you to build…”. 3

Trust me on this one. That developer you’ve hired? He/She just might openly weep tears of joy if you handed them something organized and fully realized like this.

I know I would.

  1. Quick Scapple tip: to align your bubbles in any way, highlight the bubbles you want to align, then right click them and go into the “align” menu.
  2. Even years in some cases!
  3. If you go this route, put in a bit of time to format the Scrivener file so that it lays out intuitively for the export to PDF or whatever format you choose.

Interesting Ideas: AirType

AirType concept image.

I have a hard time shooting these concepts down because I actually do think this where the future of interface is going.

When the soft keyboard debuted with the iPhone in 2007, it was met with extreme skepticism. But over time we all got used to it. There’s an entire generation now that looks at a phone with a physical keyboard much like my generation would look at a 14.4k modem.

How long before our kids’ kids look at a any physical interface at all and laugh?

I’m just about to leap into my 40’s and I imagine the days of buttons are going to be replaced by our fingers dancing through the air long before I head to a nursing home.

Still, while I love the portability and the idea of concepts like AirType, I do wonder how long it would take for my keystroke accuracy to catch up to how fast I can type on a physical keyboard.

We shall see! Probably sooner than we think too! I look forward to finding out.

Writing: Marked and Scrivener Revisited…

Hey all! This will be a short one. A few posts ago I had a write up about an Alfred workflow I wrote that opened your Scrivener .proj files in both Scrivener and Marked simultaneously.

After I published that post, many of you pointed out (including Marked’s very own Twitter account) that with the right preferences checked off, simply dragging and dropping your Scrivener project file into Marked should accomplish the same result. I totally agreed with this sentiment, but I apparently found a bug that was preventing me from doing so: dragging a Scrivener project file to Marked in the dock did in fact open both Scrivener and Marked but, for me anyways, Scrivener the app would open but the project wouldn’t. Long story short, I detailed the issue to the Marked account on Twitter and was assured that the bug would be fixed in a future release of Marked.

Well, today Brett Terpstra (Marked’s developer) announced the release of version 2.3 of his software and, true to his word, the issue has been resolved! So, if you own Marked and didn’t want to pony up for the Powerpack that Alfred offers, you once again can drag and drop Scrivener project files into Marked on your dock. Both apps will open simultaneously with your cursor blinking in Scrivener; waiting patiently for any Markdown you want to throw at it.

Scriv2Marked

Much, much gratitude for the fix and the prompt response when I brought it up!

If you create content in markdown in Scrivener and don’t use Marked? You are absolutely missing out. I whole-heartedly recommend it. It’s worth your hard-earned cash and I am not ashamed at all to admit that I don’t even come close to utilizing all that it can do. I use it daily and can’t imagine writing for the web without it. It’s grown with me and my ever-changing workflows .

I am betting it will do the same for you.

The Web: Easy Popover Footnotes in WordPress

I am an avid reader of The Magazine 1, and one of the first things you will notice when reading any issue is the clever handling of footnotes in their pieces. Commonly you will find these links to footnotes either inline or in the form of a tappable button with a symbol in it (in their case, a star) embedded throughout The Magazine’s thought-provoking paragraphs. Whenever you tapped one of these links, something kind of unique happened. Instead of being whisked away to the bottom of the page, the content of these footnotes would pop up instantly over the text in a modal window.

Read its contents. Tap anywhere outside of the modal. Done.

The popover disappears and you continue on with the article you were enjoying without having to tap a “scroll up” link or, worse, having to literally scroll back up to where you were previously.

I got used to this delightful bit of UI/UX rather quickly and instantly started searching for a way to implement the same effect into my own online prose.

Problem was, I couldn’t find anyone that was doing it. At least not at the time.

Fast Forward Six Months

Ironically where I ended up finding my answer was on the personal site of the original developer of The Magazine: Marco Arment’s Marco.org. He put up a post back in December stating how he too was searching for a way to implement these types footnotes into his site without having to develop his own javascript solution. Luckily, someone had already done it for him (and us).

Bigfoot.js site screenshot

Believing in Bigfoot

A fella by the name of Chris Sauve went ahead and created Bigfoot and that opened the door to exactly what Arment and a handful of us were looking for: more useful and powerful footnotes on our sites!

Still, after implementing it on thaddeushunt.com, I immediately thought that its implementation wasn’t terribly approachable for everyday users. Surely someone must have created a WordPress plugin for this.  Maybe with some sort of shortcode for ease of use?

Well, it turns out that someone did that too.

Enter WP-Bigfoot…

A dramatic slow clap is due for Roger Stringer who took the time to create the WordPress plugin “WP-Bigfoot”. Not only is it a breeze to install and activate, but it’s also super easy to add to your posts and pages in WordPress via some short code.

Screen Shot 2014-06-23 at 7.48.12 PM

And it doesn’t stop there either. Out of the box it looks pretty great, but if you have some chops with CSS you can even tweak the baked in style sheet to taste so that it better matches the aesthetic of your site! It’s also responsive, so it changes dynamically depending on what size screen it’s rendering on.2

Great Solutions Rarely Come Easy…

There’s almost always something that needs to be tweaked or edited to fit your site and its needs. This is one of those rare occasions though where something works perfectly out of the box. Once I found what I was looking for, I was up and running in under 5 minutes. Seriously.

So if you’ve been looking for a better, more elegant and helpful way to add footnotes to your web-based content, I hope this post saves you some searching.

  1. And a very proud contributor!
  2. Allowing your readership to enjoy these footnotes on the couch and on the go!

Tips: An Alfred Workflow for Launching .scriv Files in Marked and Scrivener Simultaneously

scrivmarked

A heads up: As the title implies, this post assumes (or, in a way, suggests) that you have purchased Scrivener, Marked and the Powerpack option in Alfred 2.

One of Scrivener’s shortcomings (yes, they do exist) as far as Markdown support is concerned, is its inability to give an HTML preview of your Markdown syntax while you write in it. There is no workflow for accomplishing this other than exporting your MD or MMD, opening it in another editor that reads MD (or the converted html) and checking it there before cutting and pasting the code into your blog’s editor.

In all fairness, that’s not what Scrivener was created to do and just because I’ve found some slightly unconventional uses for it, I can’t expect the good folks at Literature and Latte to change their software to accommodate lil ole me. We all know Scrivener is much, much bigger than blogging and writing in MD and MMD.

The good news is that even though Scrivener doesn’t have an in-app html preview function for your markdown, there is one program that you can use in tandem with it that can.

That Program is Marked.

You can read about Brett Terpstra’s “Marked” in a slew of different places (including its recommendation in the comments on this site ) so I won’t write a review of it here (maybe another time). In a nutshell though, Marked is a realtime markdown converter that works with any text editor you throw at it. Open a text file in its respective editor, open Marked, then drag the same file into Marked and go back to the text editor to continue writing/editing. As you save your markdown document, you’ll see it update in Marked, displaying the converted HTML instantly.

Cool right? It’s also a game-changer.

Marked and Scrivener

Integrating Marked has made my blogging workflow in Scrivener much more streamlined because of Marked’s handling of MD/MMD as well as its plethora of options and amazing tools for authors. But, that all said, getting a file into each application is clunky at best and almost immediately after doing that a couple of times, I wanted/needed to automate that initial step so that it was smoother.

Enter Alfred

Alfred is another popular tool out there whose sole function is to streamline everyday tasks like launching multiple apps at once, finding files quickly on your computer, searching the web, quitting apps, shutting down or restarting your computer… you get the idea. It does all of this from your keyboard and once you get used to its commands, you’ll get addicted to not touching a mouse or track pad. In truth, it’s one of the first apps I install when I get a new computer.

But aside from these baked-in options that you get for free, you can also pay for the Powerpack option and unlock a slew of very powerful tools that give you immense control over your Mac. One of these tools is the ability to easily create custom workflows. Once I encountered the dilemma above, I dove in and immediately came up with a solution.

Now, one caveat. I am not much of a programmer, so I made my workflow out of the built-in modules that Alfred gives you out of the box. I am sure that with some custom scripting this workflow could be made even nicer (if you have suggestions for improvements leave them in the comments below please). That all said, I was really happy with how this workflow came out. To save you (and I) some time I’ve included a link to the workflow below, so that you can download it and add it to your own personal workflows in Alfred. Just download it, double-click and add it to Alfred. Easy.

The way the workflow works is you bring up your Alfred prompt. Type in the keyword, which in my case is “scrivmarked”, that then allows you to browse your “Documents” directory right in Alfred. Once you find the .scriv file you want to open, arrow down to highlight it and hit the right arrow key where you’ll find a file action to open the file in both Scrivener and Marked, arrow down to that action and hit enter.

AlfredFileAction

Make it Your Own

One of the best things about workflows In Alfred is that you can tweak them to suit your needs relatively easily. Hate my keyword? Choose a different one. Have your Scrivener project files in a different location outside of the Documents directory in OS X? No problem, tweak the search scope. These, and many other aspects of workflows, can be tweaked easily in Alfred without knowing a single line of code.

But, again, if you do know a way to make this better, I’d love it if you posted your modifications in the comments below! I am sure there are many ways to make this workflow even more useful to us all!

Useful links:

Writing: My Writing System Revisited

If you’ve been coming to this site for a while, you may have noticed one of my earlier posts about a writing system I was using at the time. Well, two years have gone by and after years of faithful use, one of the main ingredients of that system, a Dropbox editor by the name of Elements, has finally been sunset.

Change is good.

So with that sad fact come and gone, I’ve been faced with task of finding a new Dropbox editor to fill the iOS void that was wonderfully filled beforehand. If you haven’t read the post that I linked to above in the first paragraph, I invite you to do so. Much of that writing system still exists today and if you write on the go like I do, you may find it useful. Also, I don’t plan on rehashing it here so if you are looking for context, definitely give it a quick spin, it’s not too long.

Back? Excellent!

So after some research I’ve found two beautifully developed and highly capable Dropbox editors that have been out for a good bit, so I guarantee that you’ve heard of them. That old adage “Change is good” definitely has its place in this tale and, truth be told, the ending of Elements might’ve been the best thing that’s happened to my workflow in a good bit.

Bridging the Gap.

The fun thing about workflows is that no matter how much you love a process, it can always be tweaked into something lighter and more efficient. Even though I loved how versatile my last writing workflow was, there were places where it was quite clunky process-wise or hampered by the limitations of iOS at the time. I dealt with it all because those things were mere quibbles and they didn’t slow me down that much. But with Elements out of the picture, it was an invitation to see if I could refine everything a bit, maybe get rid of a few things and, hopefully, add functionality that could make writing anywhere that much more efficient and enjoyable.

So without further ado, here are the editors I settled on.

Writer Pro by the development firm Information Architects Inc and Editorial by the one-man shop OMZ Software headed by Ole Zorn. Both of these text editors fulfilled all of the current needs I had and then some. Without a doubt, the three main stipulations I had were:

  • Markdown support
  • Instant sync across platforms, or robust export options
  • The ability to save my flat text files to Dropbox

Of course there were others on the list, but these were the main ones.

One thing to note, these two apps are still somewhat new and are constantly being developed to accommodate much-requested user features. If you don’t see something in this post that you like, I highly recommend that you go out to their respective sites and have a look a the complete list of features, as well as look at what’s in the pipeline for the future.

None of these editors are perfect, arguably they never will be, but they are a joy to use and are well on the way to being even more feature-rich with the raw talent behind them. I mention this because writers are a finicky bunch. We like our writing experiences to be just so.

So I write this post knowing full well that these editors won’t be for everyone, but maybe for a few. Let’s hit Writer Pro first and then Editorial.

Writer Pro for iPad and iPhone icon

Writer Pro.

Writer Pro was a bit of a tough sell for me. I already owned its older sibling iA Writer (which is still just as awesome now as it was then) and was curious how they were building off of the stark minimalism that they’d strived and gotten so many accolades for in the past. Would it now be cluttered? Not as easy to use? Or worse, would the extra UI/UX come off as unnecessary?

Luckily, the answer to these and all of my concerns were “no”. I can say this, if you are an iA Writer fan and can’t think of a single thing that it could do better, stay put. There is no reason to jump ship to Writer Pro. But, if you’ve loved the experience of writing in iA Writer but wished it had a more robust feature set above Writer’s wonderfully implemented “just open it and write” aesthetic, than Writer Pro is more than likely your answer.

Here’s my short-list of Writer Pro’s strengths and weakness.

Strengths:

  1. Fully supports MD (with inline preview support).
  2. Dropbox sync. I can already hear it now. “Well hold up Tad, I just went to the site and Writer Pro doesn’t sync with Dropbox at all!!” Calm down. You’re right. Writer Pro does not sync with DropBox… yet. But it will. Soon.
  3. A built in workflow that is natural and develops habits conducive to good writing. Admittedly, I didn’t like it at first, but having written a few pieces in it, it is a nice systematic flow that makes sense to me. You can completely ignore it too, but I recommend giving it a spin a few times. You may warm up to it.
  4. Syncs via iCloud to your Mac and your iOS device instantly. Truly. I know there is a lot info out there about how much of a pain in the ass creating adequate sync can be on iCloud, but iA nailed with Writer Pro. There is barely any lag at all. Write on your iPhone, and it immediately shows up on your iPad or Mac.
  5. iA Writer’s spartan layout is here in spades. Not cluttered at all and easily read. Even the sidebar they added on the right is minimalist and can easily be hidden if it bothers you.
    1. Incredible syntax filtering to keep you in check with exactly what you are writing. It’s hard to describe just how useful this is, or how amazing it is to watch it in action. I highly recommend checking it out. It’s truly a game changer for me and the general clean up I do while editing.
  6. Saves as flat .md but exports to pdf, clean html, .docx, or .rtf. More than enough for my mobile writing needs (but some may want more).
  7. Full markdown html preview. Command-R and a pop up comes up instantly, showing you your Markdown, rendered in clean html.
  8. Night mode theme. If you write at night as I often do, this will save your poor eyes from a lot of undue strain. It’s a small thing but I really appreciated it.
  9. Feature parity across platforms. I’m used to losing features when I move to my iPhone or iPad. So it’s an incredible development feat to see a writing experience expressed so completely across my laptop and iOS devices. Nothing (that I can see) has been lost when I move between environments and form factors. Everything you need is there and easy to find.
  10. Has a very talented development house behind it. iA has some big plans ahead for Writer Pro. If there is something missing now, chances are it’ll be added in moving forward. They are meticulous folks, almost to a fault.

Speaking of faults! Here are Writer Pro’s weaknesses:

  1. No Dropbox support currently. Like I said though, it is on the way. iA has already mentioned explicitly that it will be in the next update.
  2. As much as I appreciate the current export options, I wish there were more. I’d love to write a message to someone and export the html straight into an email app for instance. Currently to do that I have to highlight all text, copy, open mail, start a new message, and then paste. It’s clunky and it doesn’t need to be. Adding more options would make Writer Pro a bit more versatile. Though I somehow doubt that’s what they are aiming for.
  3. The structure of the workflow may be a bit rigid for some. Note, Write, Edit, Read is fine for my needs but it may not work at all for others. Want to edit it or add another stage to the process? You’re out of luck.
  4. It’s definitely (and admittedly) a work in progress. The good news is that iA is definitely listening to its user-base. So if you need anything, go on and ask for it. If enough do, they’ll listen.
  5. Not many options to tweak the writing experience. By design, just like iA Writer before it, Writer Pro is a very stark and flat experience. What you see is what you get. Want a different font or just change the font size? Too bad. If this tact isn’t your cup of tea, then chances are you should keep looking elsewhere.
  6. Cost. Getting the iOS and Mac versions will set you back just shy of forty dollars. In a five dollar app world, this may be a tough sell. To me it was worth it though.

mzl.kavtkfpa

Editorial.

Editorial made major waves when it dropped and it’s been years since I saw such a rabid fan-base grow around an iOS text editor. Having used it a good bit now I definitely see what all of the fuss is about. I also see that I have only just barely scratched the surface of what this incredibly powerful editor can do! If you are looking for a humongous deep-dive on everything Editorial click this link right now,  and read Federico Viticci’s review on macstories.net. It’s so long he created a damn e-book out of it. Don’t let that deter you though, it’s brilliant and well worth your time.

If it sounds like Editorial is a sledgehammer to use against a tack nail, well, it can be. In truth, it’s the biggest reason why I didn’t download it initially. I just couldn’t bring myself to use an editor that necessitated another learning curve. Turns out I was absolutely wrong on that count and developer, Ole Zorn, created a text editor that is yours to use however you’d like. Everything you can do (and there’s a lot that you can do) waits patiently, out-of-the-way, allowing you to just get in there and write.

That all said, like Writer Pro it has its strengths and weaknesses too. Here they are.

Strengths:

  1. Super clean layout. The first thing you’ll notice is just how inviting Editorial is when you open it. It’s even more incredible once you start discovering what it’s capable of.
  2. Inline preview support for .md and .mmd. Writer Pro does this as well but I like Editorial’s presentation better. It’s not as stark and it is more readable.
  3. Full markdown HTML preview. A quick swipe left immediately displays how your markdown will render on the web.
  4. Dropbox support front and center. Out of the box, you can assign to a folder in your Dropbox account. I plan to link this to a synced Scrivener project folder at some point, but I haven’t gotten around to it yet.
  5. Utilizes Dropbox versioning. Need something from a previous version? Deleted something you need back? No worries. Editorial has you covered. Super easy to use and some nice piece of mind.
  6. In-app browser for research. This seemed a little kitschy at first until I used it. Now I dearly wish all of my editors had a fully functional browser built-in. Not having to leave my editor in iOS to look up a link or research a topic gets addictive fast.
  7. A huge amount of options to tweak your writing experience. Head on into the settings after you get comfortable. If there is anything you’d like to change about writing in Editorial? Chances are it’s in there. Fonts, sizes, line-height, font-spacing, whew… the list goes on.
  8. Support for text snippets baked in. Got chunks of text or maybe a markdown page layout that you reuse over and over again? Create a text snippet and watch it immediately fill your document with a few taps. Very handy.
  9. Contains a custom workflow framework that allows you to perform a myriad of automated tasks. With these tasks you can do just about anything – like post your text into your blog on WordPress for instance – I’ve only just begun to play with these, but it’s mind-blowing what you can accomplish. Don’t have an interest in creating workflows? No problem. You don’t have to.
  10. Export Options. Because of the workflows above, export options in Editorial are almost limitless.
  11. Has full console-based Python support. Not a Python developer at all but if you are? You’re in for a big treat!
  12. Has a night mode theme. Like Writer Pro, if you write at night, your eyes will thank you.
  13. Custom top keyboard row in iOS. A beautiful custom keyboard row at the top awaits you! Streamlining workflows, snippets, as well as a very novel approach to moving your cursor around your document with swipes – it’s all about one thing, empowering your writing in iOS and saving you time.
  14. Has very talented developer behind it. Like iA, only with one guy behind the curtain. It’s incredible to me what he accomplished in Editorial. The app been called a “game-changer” by many a seasoned iOS veteran and it’s absolutely deserved.
  15. Cost. At $4.99, this app is a steal for all that it does.

That all said, it does have a few weaknesses. Some of them big ones. Here they are.

Weaknesses:

  1. Editorial can do so much that it is truly overwhelming at times. If you are curious like I am, you can easily (and often involuntarily) start geeking out on creating workflows when you originally came there to write. Luckily, as I mentioned above, most of it stays out of the way. But it is there. All those possibilities…
  2. On the flip-side, using it to its fullest potential does necessitate a learning curve. That may turn people off.
  3. iPad only. No Mac or iPhone version. This is a huge point to be aware of. If you don’t write in iOS on an iPad, Editorial is useless to you. On the one hand this is infuriating. On the other, I can’t imagine this app working well on an iPhone. On the Mac though? Definitely. Until then, you’ll have to snag your flat text files from Dropbox and open them in whatever OS X editor you love.

The choice is yours.

So that’s how I filled the recent gap in my workflow. It is not perfect, but I have confidence that it will get close to that quickly. Writer Pro will continue to be my bridge for when I need to sync my words across platforms and Editorial will more than fill my writing needs for when I am just carrying around my iPad. Two apps, loaded with functionality, fully mobile, facilitating my writing from wherever I may be, at any time.

It’s a beautiful thing.

Helpful Links:

Writer Pro: OS X download | iOS (universal) download
Editorial: iOS download (iPad only)

Version 3.0