The single most important thing.

I’m seeing a whole bunch of relative features which I bet if you take in toto, add up to all of the Scrivener Desktop functionality plus a whole bunch more. :neutral_face:

From my perspective, the single most important thing is that it’s better to implement 10% of the features 90% right than 90% of the features 10% right. In other words, what it does not do is more important. Please remember to leave features out! Oh, they will wail and gnash their teeth and probably me too. But it’s far better that Scrivener on iOS does a limited set of things really well, than it have every possible feature.

I read the blog post so ultimately it seems that the 5 things listed there is a good place to start but even then I reckon you could drop one or two for later (i.e. eliminate scope and reduce cycle time or improve quality) and still deliver a great application.

Just my $0.02

I think you’ll find that we agree with you on these points. There are certain things that are just not possible for memory or platform reasons, and so it is better to snip these things out and focus on the stuff that can be done, and do that well. If you saw our internal debates and scores of pages written on how to best do task X, you’d know that’s exactly how we are approaching this. :slight_smile:

There’s going to be a mystery “Task X” function? That wasn’t mentioned in the blog post.

Otherwise known as the Close button.

In that case, that’s some SERIOUS attention to detail.