Note published on November 28
Note published on November 28
We’re trying to be balanced, and not overly particular as we want to get the application out as swiftly as possible, but it’s difficult for us to unveil our long-awaited release on Windows without it being as good as we can make it. For those occasional cries we hear stating that we do not care about our Windows users, reality couldn’t be further from the truth. We want to be proud of every application we release on any platform, which is why we’re taking so much time.
Current users of Scrivener 1 on Windows will probably be aware there have been activation issues since our transition to Paddle, that we’re hopefully getting to the bottom of. It would naturally be absurd to release Scrivener 3 on Windows with an activation issue. We’ll keep this update brief so we can get back to concentrating on the coding and preparing materials for the release. Users can download and use our Scrivener 3 beta any time they wish from thisforum webpage.
Sorry that our news isn’t stating an imminent release date, but our next related blog post will be providing such details. Wishing those partaking a happy Thanksgiving, Christmas and New Year thereafter. We’ll keep on coding.
I thought this was a well-crafted notice that should put both users and fans of the product at ease: it comes across that they’re trying to get out a high quality release as soon as possible and that they’re as frustrated as everyone by the delay.
Encouraging that a provider of software to make the writing process more effective is also an effective writer.
Keith Blount was a teacher and a writer who wanted a certain kind of composition tool and couldn't find what he wanted. He taught himself how to program in order to create a tool for his own writing use. One of the main reasons that it takes so long for a release to occur is because there isn't a large team of developers. Keith does the Mac version himself and he has two people who work on the Windows version. They don't work in the same physical location either. The iOS version took many years to be released and reached a the person who was working on it reached a roadblock that they were unable to overcome.
Keith took the project in hand and recoded the program completely from scratch. It was more than a year after the above article before the iOS version was released.
In 2016, Apple listed the iOS version in its best of 2016 category.
About 7 months later, an upgrade to the iOS version was released.
There are currently three versions of Scrivener and a companion tool named "Scapple."
There’s a certain craftsmanship to Blount’s work that comes across in your description. To pick up the iOS software project that had died and rebuild it from the ground up must’ve been an incredibly frustrating and challenging task. From beta testing of the Cake app, I also know that getting into the App Store is an achievement let alone ranking as one of the Best apps of 2016. I used Final Draft when I was writing (or attempting to write) screenplays but I don’t think I was a raving fan: the auto formatting to script standards was a better option than attempting it in Word, but I could’ve just as easily gone with a competitor’s scriptwriting software.
I'm not familiar with Scrivener's script writing features. I know there are nine script presets and that there is a menu of settings which are unique to the script writing feature but I have never played around with it. I know, also, that it is designed to optionally interact with Final Draft but I have never used that program either.
There is a short video (less than six minutes) which gives an overview of the script writing features: