Yes, maybe - but how about choosing it for editing - using the Apple Pencil to make hand-written annotations of your Scrivener draft in pdf format (if Apple’s promises of precision for the Pencil turn out to be true), that you can then read in Scrivener split-screen and transfer to your master? (Ordinary iPads and styli are too imprecise for this, paper’s too user-unfriendly, and most other tablets lack one function or another that you might need.) Of course, it would be an expense just for editing, but as E.B. White almost said, writing is editing.
But but but… That’s what paper is for! I can’t imagine staring at another screen for editing. Printing it off and making notes on paper gives me a whole new feel for the text.
Like I say, you’re all stark raving mad. 
What?!? Do you want we kill trees!!!
(I admit I do a lot of editing work with GoodReader on an iPad; but this doesn’t contradict the idea that writing on a MacBook seems the most pleasant solution at the time).
Paolo
Most of those items you list in your third sentence are among the main things that make Scrivener great. And it works so great on my Mac, so again, what would iOS-only offer that would make me switch? All the workarounds and inconveniences just to get me back to where I’m already happy… I’m starting to lean toward your “starkers” theory.
That said, I spend more than half my time as an editor and teacher who marks up copy, and I am comfortable doing that in Pages and Google Docs, so a Scrivener iOS companion (rather than standalone iOS version) might actually work for me for the self-editing uses you’ve outlined.
Nevertheless, I accept (if don’t fully understand, Viticci notwithstanding) that others happily live almost entirely in iOS. Maybe someday, Apple will improve its text system as part of its great convergence (NOT merger) of iOS and MacOS, Scrivener will follow suit with more iOS features, and eventually, iOS whippersnappers will be able to enjoy the full benefits that we OS X luddites have been basking in for years now…
One of the nice things about working on the iPad version and being up against so much pressure with it being so overdue, and with me having to get it into a decent state myself now, is going back to the app I had in mind eleven or twelve years ago when I first started on this journey, and getting in the features that were most important to me back then in a UI that is as simple as other iOS UIs. The main things I wanted back then were a flexible source list of documents that I could structure how I wanted, with an editor that could open them, and the ability to add a synopsis and notes to each (and the ability to see the synopses in a list together). In that regard, I’m trying to build something that I could take away with me for a week without a laptop (even though in reality I’d probably never do that!) and still have all the core ingredients for writing.
The aim is certainly not - and never will be (and never was), unless iOS fundamentally changes - to build a complete Scrivener on iOS. It’s always been intended as a companion to Scrivener for desktop, although it is now a slightly simpler one than it once was.
Anyway, to show that I’m not spending all my time waffling on here and am actually coding away, here’s a screenshot of the rich text editor that I’ve just finished re-implementing from scratch.
(Ignore the tiny keyboard row at the bottom, that wasn’t optimised for the iPad when I took the screenshot.)
Thanks for this update and teaser. I hesitate to even bring this up now, given the immense workload and urgency of shipping iOScrivener, but… to the extent that one of the complaints about Scrivener for Mac is its complexity and steep learning curve (not for me, but I’ve been on the journey from nearly the beginning, too), might the advent of the iOS version ultimately bode a rethink/simplification of the Mac version? Are you learning any lessons about the Scrivener UI from your experience at making the iOS version?
I know, every feature removal would occasion a cascade of outrage, as happened when Apple iOSified Pages for Mac. There’ll always be a tension between feature comprehensiveness and usability/ simplicity/ elegance, so it’s a matter of which tradeoffs are acceptable to the broadest swath of users. Maybe it’s nothing so drastic as a Scrivener Lite but merely learning how to better hide the complexity to avoid distracting those who don’t need it, while still serving those who do? It sounds so easy to say, so fiendishly difficult to implement… Anyway, just curious about how Scrivener for iOS might positively affect future versions of Scrivener classic.
In a word: no. The next major update of Scrivener is 90% complete, and it is most certainly not a drastic rethink or pared-down version. For me, the old version of Pages was ten times better than the current version. If I were to strip down Scrivener, I’d remove footnotes, comments, script mode, collections, snapshots, maybe keywords, freeform corkboard mode, QuickRef panels, most of the Preferences, the scratch pad, page layout mode, and probably a bunch of other stuff, just because it’s stuff I don’t use an awful lot myself. Along with losing those features, I’d also lose a lot of users, though.
To be honest, I don’t like this recent mindset that says you shouldn’t have to learn software, that if you can’t pick something up in a few seconds, it’s “too hard”. I don’t really want users with that mindset, because I’m not building Scrivener for them: good tools are worth learnings, and I strongly believe that Scrivener is a good tool. That’s not to say we can’t reduce the learning curve a little, though. 2.x needs updating a fair bit, and that’s happening with the next update, but it’s certainly not getting stripped back (although we will try to clean up the UI further where possible).
I think the idea of Scrivener being “complex” or “difficult” is something that is overstated, though, and probably those flames are fanned a little by some of our competitors (not all - we like most of our competitors!). Despite not having had a major update for five years (I’ve been working on the next update for over half of that time!), despite our colossal tardiness in getting an iOS version out, and despite competitors coming out with big updates, simplified UIs and iOS versions, we are, very fortunately, still selling more than our competitors by all indicators (e.g. the Mac App Store charts - which accounts for not even a quarter of our sales, and which some competitors sell through exclusively - and NaNo threads etc). We’re also fortunate in that the vast majority of user reviews for Scrivener are overwhelmingly positive still. So I don’t think the claims that Scrivener is too difficult and that people flock to simpler software holds up to much scrutiny (it’s often used as a stick to beat us with over our late iOS version, though!).
What I do think is that we are not very good at getting across Scrivener’s core concepts in a concise manner, and we lead new users to think they need to master all these bells and whistles rather than just guide them through those core concepts and reassure them that they don’t need to use all of Scrivener’s features. All too often I see users on forums saying, “I only use a fraction of its features…” as though they feel guilty about it and should know it all. That’s something we’re working to improve next year. Because I think the biggest hurdle in coming to Scrivener is conceptual - realising that folders can be files, that the corkboard represents a folder’s subdocuments and so on. Removing those hurdles by simplifying the software would entail removing the very things I built it for; instead, we want to provide users with a smoother journey into understanding these concepts, and keep things out of their way until they need them.
In fact, right now, in fact, I’m working with our graphic designer to find ways of cleaning up 3.0’s interface to make it appear simpler even though all of the features are still right there under the hood. That’s the real challenge - it’s a bigger challenge than just tearing things out, for sure. But we’ve got plenty of time to think about it, seeing as coding on 3.0 has ground to a halt while I get on with this blasted iOS version.
I really don’t get the ‘too complex’ argument. I have been using Scrivener for years now and I probably use a tiny fraction of its features. And it’s fine! If I do need something more from it, I do a little research, and generally I find it quickly. Complexity is a problem only if you are obsessed with using all the features of the app you are using, rather than focusing on your work. If you focus on your work, you can only find apps ‘too simple’, that is, whenever you need a feature and you realize the app doesn’t support it 
And have a contract hit put out on you … 8)
Also agree regarding the complexity of software. I use Scrivener and DTPO extensively, but probably only use a small fraction of their capabilities. But the small fraction I use are perfect for my uses. When I need to use other capabilities, I learn them as I go.
No simplification please! Sounds like Scriv 3.0 will be worth waiting for. What on earth could be holding it up? 
I’m of two minds about getting an iPad Pro vs a retina Macbook. The IPP is a bit cheaper in Australia (though not once you add the pencil, cover, keyboard and AppleCare). The Macbook is obviously better for writing and it runs the more usable operating system (and naturally, desktop Scrivener).
And yet, I am fantasising about being able to sketch my fantasy maps directly on the IPP with the Pencil and then editing a scrivener project on the same device…
Truth is my head know’s an iPP is a waste of money for me. I love keyboards and trackpads and my ‘drawing skills’ actually rely on a mouse and a tonne of filters and selections because I can’t sketch to save myself.
I’ll probably buy the Macbook, though I’ll hold on to my money until the iOS version ships I’m pretty sure that the Macbook + my iPad mini will be lighter and easier to travel with than an iPP + gear anyway! If I can do light restructuring and edits on the Mini while standing on the train, I’ll be happy.
Good call!
Not too much time! As soon as you release the iOS version, we have to immediately start complaining for the delay in releasing Mac version 3.0!
I like where you are heading Scrivener to. Cleaner, multileveled, not less powerful.
Paolo
The iPad Pro is rather delicious - the deal was (in this house) that I got a 2015 Macbook (also gorgeous) for writing and my wife an iPad Pro for artwork. As art machines the new iPads are incredible. My bank account is empty.
I posted a couple of questions in the ios scrivener thread, and just happened past here when I noticed this comment from Keith:
‘you’ll still need the desktop version for editing styles, for serious restructuring, for the corkboard…’
Does this mean the corkboard… won’t be in the ios app??
That kind of kills the app for me (I mean just for me, good luck with it either way). The major point about working on an ipad pro, which is extremely light, is the touchscreen makes organising a joy - mindmaps… and corkboards. I assumed ios scrivener would prioritise the corkboard… what with this being the one aspect in which an ipad is far superior to any laptop as an interface (i mentioned in the other thread… i used to use an actual corkboard pretty much, and I think people are starting to forget what the words cork and board meant before they were ratcheted together in digital substitute).
I was happy to wait for the app but really that is it’s primary feature for me, coupled witha word processor so I’d be better off just using index card. Could I ask if there is any timeline or plan to support exporting scrivener projects to index card on the windows scriv? Or else I have to export as files and copy paste everything. Thanks.
I’m one of the crazy people who much prefers working on an ipad. Writing is easy… it’s just words, white space… and for me a corkboard to visually arrange things.
So, still no ETA on an app, and we’re down to one developer, who’s also the lead on the Mac version? Or am I missing some other place where there’s a more recent update? The blog post is over a year old now. Doesn’t bode well for a release anytime soon.
For me, KB’s posts in the Scrivener for iOS thread over the last few weeks are all I’ve needed to know. I’ve been encouraged by the news that Keith has taken over the development of the iOS app. It’s clearly a real challenge to create an iOS application which will meet the standards that we as Scrivener users will find worthwhile and that Keith himself has set. But having observed for nearly a decade the hugely successful development of Scrivener under his leadership, I’m absolutely confident that the iOS app when released will be the best it can be, as soon as it can be. An ETA, before the application is just about ready to go out of the door - much as I’m sure that many people would like one - would seem premature.
+1.
I saw the IOS version not as the one to do heavy WRITING but doing structural work, viewing all files including research and Maybe small edits. But primarily structure and being able to VIEW everything in the project. Structure work = coark board and index cards.
Well. We’ll see when it arrives.
Just curious as to how that primarily visual usage scenario would work on an iPhone - which Keith has said a number of times is his weapon of choice for the the iOS version. I assumed (and am looking forward to it being) an adjunct app for notes and inspired prose moments, and maybe light editing.
I just downloaded an app called Duet Display that turns my iPad Mini2 into an adjunct screen for my MacBook Pro. I’ve only used it to stream background videos and show stuff like email while I’m working on my Apple Cinema Display at home, but when I head off to visit the family for the holidays, I’ll try using the combo with Scrivener, maybe putting the Binder in the Mini and the Editor in the Mac, with a horizontal split showing my source document and the document I’m working on. Or perhaps I’ll put the source document in the Mini and reserve the MacBook screen just for what I’m writing. Seems like a useful way to maximize my Scrivener space by using both devices, if I happen to be traveling with both.
Reviews (available on the app site) have been really positive, and it’s been working flawlessly and laglessly for me for the last few days. Note that it’s currently on sale for $10, and that the newest version resolves just about all the issues raised in the initial clutch of reviews when the app came out a year ago.
Yes, an MBP + iPad mini is a bigger combo than an iPad Pro with keyboard case… but on a long trip, I tend to travel with both anyway, if only because if something happened to my Mac, I’d feel a fool for having left the mini at home, plus I use it for reading books and articles on the plane and at my destination. If only the little 12" MacBook worked with my display, I’d have one of those instead of the pro, and the combo of MacBook (or even 11" MacBook Air) + iPad mini IS pretty slim. Anyway, just an option for those traveling Scriveners, or those who use only a laptop at all times, who crave more screen space.
That actually sounds like a pretty solid idea. As much as the iPad Pro captivated me at first, I know that I’ll find it too limiting as a primary device and once you add peripherals I think it’s value as a portable device diminishes.