We have a lot of people asking after the iOS version given that I haven't posted much about it on here recently (although I have been giving incremental updates over on the forums). The lack of updates isn't intended as a slight against our very valued users; it's just because we've had our heads buried in code and haven't been coming up much for air.
The good news is that our iOS version is (at last!) feature-complete and is currently in internal beta-testing. We're in the process of smoothing out the rough edges we find through use and fixing bugs before we make it available to our wider beta-testing group. Having taken so long to get to this stage (we know), we don't want to fall at the last hurdle and rush beta-testing. After all, the sync code is complex (it was a three-month job in itself) and we want to ensure it's never going to cause any data-loss in the real world (it is holding up well in testing so far, though). Once it's out with our wider beta-testing group, I'll start posting some screenshots and showing off the features. Given past debacles, I'm hesitant to talk about release dates, but we expect a summer release, though whether mid or late summer will depend on what is thrown up during beta-testing, of course.
To answer some common questions we've had about the iOS version:
- Version 1.0 will sync with the desktop version using Dropbox. The sync code has two components, the Dropbox-specific code, and the code that handles merging all the changed files between platforms and dealing with conflicts. This second part of the code has been designed for reuse with other sync clients, so we plan on adding support for sync solutions other than Dropbox post-1.0 (Cubby is one that has been requested several times, for instance).
- There is no iCloud syncing in 1.0 because iCloud does not work well with package-based file formats such as Scrivener's. We were hoping that iCloud Drive would provide a solution, and are still looking into it, but the APIs don't seem to provide the flexibility we need on the iOS side. (The reason syncing is more complex with Scrivener than for most apps is because .scriv files are really folders, which is how we can allow you to import any sort of research file and only load files into memory as they are viewed in the app.)
- You can also transfer projects simply using iTunes, of course.
- When the iOS version is released, there will be simultaneous updates for both Scrivener for Mac and Windows that provide sync features. So don't worry, Windows users, we have no plans of leaving you unable to sync!
- Version 1.0 will not have any dedicated screenwriting features, but scriptwriters will be able to sync their scripts using Fountain syntax for paragraphs.
- Scrivener for iOS is a full-featured writing environment - the binder, corkboard, outliner, full rich text editing (with comments, internal links and so on), import, export, reference to other documents (including images, PDFs, media files) - all the core features of the desktop version are there in the iOS version, but with a UI designed from the ground up for mobile devices.
- Scrivener will require iOS 7.0 or above.
It's been a long journey, but at last the light at the end of that proverbial tunnel is in sight. I can't wait to start showing you screenshots and talking about it properly.
It's not all about the iOS version, however: our heads have been buried deep in code working on serious and extensive (and exciting) updates for our existing platforms, too. But we're not yet ready to talk about those, and we want to get the iOS version out first.
EDIT: We've had a lot of users ask about how to get involved in beta-testing the iOS version (thank you!). In the past, the way we have always selected beta-testers has been to look out for users on the forums and social media pages who know their way around Scrivener, are good at reporting bugs or giving constructive feedback, or who post useful information on using Scrivener for fellow users. We continue to look out for new beta testers that way, and from that, we already have quite a large pool of testers for the Mac and Windows versions to whom we'll be sending out iOS beta invites to begin with. Once we've got a better idea of what the numbers are like, and when the time comes, I'll post more information here on how to apply to become a beta-tester for anyone else interested. Please note that it's not a good idea to apply to beta test if you just want early access, though - the beta-testing stage is where we find the most bugs, so you have to be prepared for crashes and even possible data-loss (obviously we hope to have ironed out data-loss bugs by the beta, but beta-testing is where users find the things we've missed and we cannot guarantee that there won't be hideous bugs lurking - beta-testers are guinea pigs). Beta-testers also have to be prepared to spend time trouble-shooting and providing us with detailed reports on every issue they find. We'll provide more details once we're nearing the end of internal testing.