I would love having a mobile companion to keep on writing on the go. I was so expecting a solution from the Scrivener editor that I passed by real alternatives although I did search.
I stumbled upon Textilus for iOS a few days ago while browsing iTunes Store for other reasons. Sudden was my surprise when I saw the page title mentioning a possible interaction with Scrivener as shown in the snapshot below. They might have changed the title because I hadn’t noticed that.
The silly thing of this story is that I already had Textilus in my iPad but I largely underestimated it because lost among other text editors.
Thrilled by this (new) discovery I started considering the tool from a different perspective and investigating its sync feature with third-party applications through cloud-based repositories.
Needless to say that text sharing is possible only through cloud solutions. Several blogs point out Dropbox as the sole synchronization vector. Version 5.0.2 installed in my iPad also proposes Google Drive and Box.com. This integration is effective since V4.0. The Google Drive option is an appropriate and timely choice for me as I currently migrate my online content from Dropbox to Google Drive.
Further readings on the web revealed tutorials to set up both apps to establish the interface. There’s a tighter interaction between Scrivener Mac and Textilus we don’t have with Scrivener PC. It does however not limit the field of possibilities on PC.
The configuration with Google Drive was seamless and straight forward for me. It works like a charm and will definitely change my habits using Scrivener.
An additional point worth noticing about Textilus synchronization and exportation features is that Textilus interfaces to Scrivener through a true synchronization i.e., any change made in either application is reflected in the the other because the text is first saved in the configured cloud-based repository. It does not apply to all other apps like Evernote; when we export a text from Textilus to Evernote it’s saved in the declared default notebook. Textilus does not see the notebook hierarchy. It means that once your text has been exported into Evernote, any subsequent update won’t be pushed back to Textilus. It’s not a limitation but a bold difference between synchronization and exportation we have to be aware of.
This very point will prevent me discarding Evernote companions such as SwiftKey for the benefit of Textilus. This later will thus be for Scrivener what Swiftkey is for Evernote, some outstanding companion tools complementing the scopes of features.
As a conclusion to this awesome discover, I can update my Resource page and my Hall of Fame of best productivity tools with this new entry.
Question: For all writer fellows, do you use Scrivener to pursue your writing or editing activities on the go?
Photo credit: Creative Commons, Oliver Quinlan.