The new minimal text editor Writer Pro is a worthwhile upgrade over its predecessor, iA Writer. It’s a very polished product with useful features like multiple writing modes that each have their own custom font. There’s also Syntax Control, a tool that highlights select parts of your document for easier revisions and edits.
Admittedly I didn’t expect to have such a positive experience; Writer Pro launched in a crowded field of already well made, minimal text editors. There’s Information Architects’ own iA Writer, which already shares the core Writer Pro feature set. And Byword is an editor with exceptional Markdown support, keyboard shortcuts and exporting options.
Details matter
Yet Writer Pro distinguishes itself over the competition with subtle yet important design details:
The program fades out the standard Mac toolbar at the document’s top when you begin to type. It’s a small touch that removes another distraction from your writing.
You can enable Syntax Control to highlight just the sentence you’re on. When you scroll through your document, the fade out effect is lifted for easier navigation.
Most competing text editors only enable line or paragraph focus. Line focus feels too constrained on longer sentences while paragraph focus is too loose. Writer Pro’s Syntax Control set to sentence mode is a happy compromise; it highlights the sentence you’re on, regardless of length.
Writer Pro’s formats select Markdown symbols so paragraphs, list items and headlines line up vertically. It makes scanning through and organizing a larger document much easier.
Writer Pro’s font mix of Nitti, Nitti Grotesk and Tiempos is arguably better optimized for writing than options available on competing editors (more on this below.)
Writing modes
Writer Pro doubles down on its existing design strengths with its new writing modes: Note, Write, Edit and Read. You can jump between modes at any time; switching from one writing mode to another changes the font and cursor color to optimize for the task at hand. Content remains unchanged.
Because content is static, Writer Pro’s mode switching can feel superfluous at first; negative reviews on the Mac App Store harp on this a lot. However, after switching between modes for several weeks, the feature has a positive effect on my writing. Note mode utilizes a thin, ultra clean sans serif that pairs well, to quote iA, with the “clean and pristine” nature that notes tend to have. The typography here pushed me in the direction of shorter bullet points over long, rambling sentences.
Write mode retains the monospaced Nitti font from iA Writer. It’s blockier and inherently easier to flow from sentence to sentence, better for uninterrupted writing. Edit and Read modes use Tiempos, a higher contrast serif. This font corrects one of my complaints about the original iA Writer; Nitti was awesome for actual writing, but for editing long form pieces, Nitti’s fluid structure wasn’t ideal (there’s a reason you rarely see idiosyncratic sans-serifs like Nitti used for long reads.) Tiempos is a far better reading and editing choice.
Just to make sure I wasn’t buying into empty typographic fluff, I used Writer Pro’s modes against their suggested intentions for several days. To the program’s credit, writing was more difficult: long form pieces in Note node were written decidedly slower than average. And editing paragraphs in Write node felt awkward with too much space between characters.
Syntax Control
Writer Pro’s other significant new feature is Syntax Control. With a click or keyboard shortcut, most of the document fades out, highlighting only the sentence you’re on or just a document’s adjectives, nouns, adverbs, verbs, prepositions or conjunctions. It’s effectively iA Writer’s “focus mode” on steroids.
Unlike writing modes that I use throughout the writing process, I only found Syntax Control useful for final edits and draft revisions on longer pieces. That slightly dulls this feature’s impact but it’s still useful to cut down on verbiage. Those who need absolute focus on what they are writing will likely appreciate Syntax Control on the current sentence (identical to iA Writer’s focus mode.) I rarely use Syntax Control this way but it’s helpful when you’re having trouble putting together a troublesome sentence.
Shortcomings
While overall Writer Pro is impressive, there’s a few small issues that need work. The Markdown preview window has poor styling with a font size that’s too small and lines that stretch out as far as you resize the window; it feels like an afterthought feature. It’s also odd iA doesn’t automatically covert Markdown syntax (e.g. headlines, bold text, links) when you switch to Writer Pro’s Read mode. Given that iA already went far enough to make this the one mode with a change in functionality (you can’t edit, the cursor and misspelling highlights are removed) they should go all the way to maximize the reading experience. And, unfortunately, this lack of Markdown syntax conversion extends to PDF exports too. It makes PDF exports useless for Markdown writers; get a copy of Brett Terpstra’s excellent Marked 2 as a workaround for now. Additionally, as a writer who’s often typing away emails and blog posts late at night, Writer Pro could really use a “night mode” with light text on a dark background. It would violate Writer Pro’s general lack of customization, but adding the feature would enhance readability and lower eye strain in dark environments, two big wins.
I’m also seeing performance problems with Writer Pro every so often; the CPU usage suddenly spikes and you’re left with an unresponsive, sluggish program, usually after I have the program active for an extended period. It’s rare but annoying when it happens.
Conclusions
Over the past year I’ve written mostly in Byword on both on iOS and the Mac, with occasional forays into iA Writer when I’m in the right mood. Now, after weeks of heavy Writer Pro usage, it’s my main writing choice on the Mac going forward. That said, with its strict minimalism and higher cost, Writer Pro isn’t for everyone. If it’s your first look at a plain text writer, Byword is a more well rounded, cheaper alternative. Nonetheless, if Writer Pro’s visual mode changes and Syntax Control sound compelling, or if you’re a typographic geek like me, give Writer Pro a try.
Federico Viticci over at MacStories knows his iOS apps very well. The guy oversees and has written hundreds of posts for MacStories, so we shouldn’t be surprised given the high quality of writing over there that he’s very well qualified in his opinions.
If you’re looking for some fresh apps to start the new year I can’t think of a better list to start from.
Native mobile apps are a temporary solution. We’re just over 4 years into the Appstore era and this has already become apparent. Open web technologies are catching up to the point that the vast majority of web apps no longer need a native counterpart.
Don’t try to tell me native apps are faster or allude to them having a “better experience.” That simply is no longer true.
Jim’s argument might be a tad simplistic, but I agree with his points. We’re getting glutted with so many unnecessary native apps that should just be well thought out, responsive web apps.
Apple’s iOS hardware business model – currently its largest revenue stream – is based on making a large margin from a premium hardware product. Their trick is hiding this fact from customers, and selling the iPhone and iPad not on their hardware specification, but on what you can do with them. And that, in every Apple advert, is all about the apps…
…This business model means that it is in Apple’s interest for the hardware to be as expensive as possible, and for the apps to be as cheap as possible.
True, and Dave has a lot of smart suggestions. But I don’t expect Apple to offer much of anything in terms of change, especially when iOS is still the considered the premier platform for third party developers. The numbers of the tech savvy begging for paid upgrades and trial periods are dwarfed by those that rarely make big purchases on the App Store.
Having shot hundreds of shots via Instagram, I’ve gotten burned out on their strong 60s and 70s esque filters. Results are fast but crude – it often feels like applying a sledgehammer to a job that requires a scalpel. In response I tried a lot of alternatives but settled on VSCO Cam has been my new “go to” choice for post processing my iPhone shots. It’s not as fast as other processing alternatives, but I love the app’s much subtler filter effects, especially the three options in black and white.
For many VSCO Cam can be an all in one photo solution – it loads to take a shot in less than half the time of Camera+ or Camera Awesome. I still found the actual shooting options pretty bare bones, so I tend to shoot in Camera Awesome, and when I have the time later import shots directly into VSCO. Recommended for 99 cents in the App Store.
Developers have clamored for a paid upgrade system since the App Store’s inception, but I’m worried Apple won’t offer this feature anytime soon. I’m far from alone – Instapaper developer Marco Arment also predicted Apple’s non-action on his latest podcast. Yet Marco and many others don’t think this is a problem, that the current à la carte system is “the future” of software publishing. They’re completely wrong.
Apple drags its feet on paid upgrades because Apple wants simplicity for their customers. A choice between a full product and paid upgrade muddles this philosophy. For now, all users get all app upgrades automatically. If you introduce optional, paid upgrades, certain updates only apply to select customers. This adds complexity for consumers and developers having to juggle and maintain multiple app versions on the store.
In addition, the lack of paid upgrades keep app purchase prices lower. This is simple economics: on the App Store, developers have to force a repurchase between major versions in the form of a new app. App prices will be driven lower to offset the much larger sticker shock between versions and to account for boosts in upgrade revenue (100% of the product cost instead of some smaller fraction.)
I don’t think this is a good economic model, especially for more expensive, professional level software, such as Omnifocus and Photoshop. But remember, Apple is not, at its core, a software company; they make money from selling iPhone and iPads. The cheaper the software, the greater the incentive we have to keep on buying Apple’s hardware.
Also it’s professionals and power users – both niche Apple consumers – that demand paid upgrades, not the core audience. Given how rarely Apple updates its pro products (e.g. Mac Pros, Aperture, Final Cut) in the last few years, we’re in for a serious wait before Apple takes any action here.
Marco defended Apple’s inaction on this week’s Build and Analyze podcast; I disagree with him. A lack of paid upgrades causes two main problems:
The absence of an incremental purchase kills a huge source of revenue for developers and publishers. Without both new software and upgrade streams, many publishers, from high end publishers like Adobe to independent studios like Delicious Monster and Panic have a hard time staying afloat. In economic terms, a lack of price discrimination between more receptive, existing customers and newcomers is a major problem.
Customers get angry and frustrated when they can’t upgrade. Naturally for apps under a few dollars, this issue doesn’t apply, given the small investment. Yet if you’re considering $40, $80, or hundreds more for a purchase, an upgrade by way of repurchasing the software is costly. It’s especially aggravating if the next big upgrade is launched soon after you buy the old version. This keeps potential buyers on the sidelines between major releases, exactly the time when many developers need revenue to keep going.
Apple needs a change in course here. A lack of paid upgrades is killing both developer revenue and consumer interest in a lot of great apps. It’s also watering down app quality, especially in the iPhone and iPad markets where there’s no App Store alternative.
The Interate podcast gets some big names in the app design world to pop on their show. This week was exceptionally big with Tweetie creator Loren Bricher. The episode touches on a lot of interesting subjects: the conservatism of Apple’s iPhone UI, Bricher’s preferred design tools, Blackberry 10 and more.
I read this article and found myself nodding along to much of what Nick Thompson had to say. It was a genuine surprise, given that the Condé Nast iPad and web apps are so poor. Then I read this:
The Verge: Magazine apps are often slammed for being slow, large, and kind of kludgy. Why is it so difficult to do properly? Who’s doing the best job?
Nick Thompson: New York has an excellent app, as does Wired. I’ve also been very impressed with Esquire and Vanity Fair.
TV: Why do you think The New Yorker has been so successful on the iPad, relative to other magazines?
NT: The main reason is that people genuinely like the magazine, and they like to read it. Also, we’ve, very deliberately, kept our iPad app very clean. There isn’t much clutter; it’s really just the stories, with some added slideshows, videos, and infographics.
Naturally, the guy singles out other Condé brands. Ironically, with potentially the exception of Wired, where the extra media content fits well, it’s a disaster everywhere else he mentions, especially Vanity Fair. Slow load times, gigantic downloads and extraneous videos that slow the experience.
And I’m sorry Nick, but when there’s a 200 plus MB download for each “clean” iPad New Yorker, I’m looking elsewhere. Love the content, and I read it every week…on my Kindle, which downloads in about 20 seconds.
Technology Review’s Jason Pontin, in a frank assessment of publishing and tablet apps:
A recent Nielsen study reported that while 33 percent of tablet and smart-phone users had downloaded news apps in the previous 30 days, just 19 percent of users had paid for any of them. The paid, expensively developed publishers’ app, with its extravagantly produced digital replica, is dead…
…I hated every moment of our experiment with apps, because it tried to impose something closed, old, and printlike on something open, new, and digital.
Last fall, we moved all the editorial in our apps, including the magazine, into a simple RSS feed in a river of news. We dumped the digital replica. Now we’re redesigning Technologyreview.com, which we made entirely free for use, and we’ll follow the Financial Times in using HTML5.
Many argue that native apps are our future. Some industries where processor speed is key (e.g. gaming) will stay native for quite a while. However, as this article illustrates, the first wave of tablet apps for publishing are a failure. I expect Newsstand to be a failure. Publishing understands the openness and fluidity of the web is the way to go and I think many more industries will follow suit to HTML as well.
In the iOS and Mac app stores, newcomer generalist apps are dead. Long live the new wave of hyperfocused apps.
This point was inevitable given both stores have reached a saturation point. There are so many calendars, text editors, todo lists, weather forecasts and photo editors – to name just a few categories – that it’s increasingly rare for any newcomer to stand out. Several success stories emerge early (e.g. Omnifocus and Todo for todo lists, Camera+ in the photo department) receive positive coverage, gain a user base and iterate. Meanwhile most competitors flounder and struggle.
Yet developers are opting out of this Darwinian cycle by going very deep, singular and focused with their app functionality. I wouldn’t use the term “minimal” because some are loaded with options and customization for power users. “Hyperfocused” fits better as each app’s direction is simple and straightforward. Where a generalist app might have ten features, a hyperfocused app has one, but executes that one feature with depth, polish, and well thought out design.
Not every app of this style can be a winner – their very focus makes them divisive – but a few have clicked well with my workflow: Drafts and Dark Sky for iOS and Take Five for the Mac.
Drafts
Unlike other more generalist text editors that expect a setup process for new documents, Drafts presents you with a blank document and keyboard on every launch. There’s no required taps for a new document location or file type; open the app and you’re ready to type with little lag. Drafts at its core feels like the default Notes app with a serious speed and UI upgrade and that alone should appeal to many.
But speed is only a fraction of Drafts full functionality. A tap of an icon below the document reveals a full action list. You can copy to the clipboard, email, send to a Dropbox folder, tweet the content and send the text to other iOS apps. I use it almost every day for ideas capture, drafting Tweets, sending interesting links to Dropbox and writing extended emails.
Dark Sky
For weather I’ve had the My-Cast app on my home screen for over a year. Its got plenty of information and accurate, but generally a bit sluggish and the visuals need serious work. Also before heading outside I have to tap through several screens just to determine if there’s rain in the immediate future.
Enter Dark Sky, an app that’s singular purpose is to tell you if it’s going to rain in the next hour. After starting the app you get a graph and text description that measures the severity and chance of rain. The app excels in its detail – the graph can convey at a glance when an incoming storm will peak or when short gaps in the rain will emerge. Text descriptions are highly descriptive (e.g. “light rain for 14 min”). If you want something more visual, a great looking radar is a tap away. The whole package is fast, accurate and reliable. It’s found a nice home on my second iPhone screen.
Take Five
I’m a heavy iTunes and Spotify user on my Mac, yet the UI of each app is cumbersome and bulky. The row based, options everywhere design works well for heavy lifting but 95% of the time I just want to know the details on what’s currently playing.
To address this UI bloat, several iTunes and Spotify mini player apps have popped up. I tried both Simplify and Bowtie, two popular options. Yet while both did the job, I wasn’t crazy about their memory footprint and occasionally rough visuals.
That led me to Take Five, an option by Iconfactory, the design shop responsible for Twitterrific, xScope, and Flare. It’s a now playing visualizer pared down to the essentials: album art, song, album, and artist. Yet in targeting such a simple feature set, IconFactory delivers a really well thought out experience. Its got best in class visuals with a cool blue and black color palette. Keyboard support extends to a show/hide hotkey for the music app you’re using, be it iTunes, Spotify, Rdio, or five other players. You can turn on a Growl-like auto notification that pops up the mini player briefly when the track changes (with Spotify’s often shoddy Growl integration this is an especially useful feature.) Take Five’s main ‘hook’ is in its pause functionality; with a keyboard shortcut or icon click you can pause your music and have it auto fade in after a set period (hence ‘Take Five’). It’s a cool perk for quick breaks.