Why should Windows users believe you? And if you do really release it, how many more years will it be?
Last August Lee said “a few more weeks, not months.” The one year anniversary of this whopper is less than two weeks away. It looks to me like finishing this upgrade is way beyond the abilities of the Windows developers.
I almost wish you would go to a subscription model. That would make it easy for me to totally ditch Scrivener.
So just ditch it. What are you waiting for?
My guess is they’re waiting for something to be created that currently does not exist: another Windows app with features and price equivalent to even Windows Scrivener v1. :mrgreen:
For the same reason that we should believe you when you keep saying you want to ditch Scrivener and yet you’re still here.
Oh dear. I wondered when the Windows fracas would start…
Oh dear, another ‘gonna take my bat and ball and go home and sulk/hold my breath until I turn blue/lie on the floor and kick and scream until I get my way…’
You’re number … with that threat, totally over it
The owner of the company has come out and and admitted they screwed up, taken responsibility and said they will work to ensure this does happen again.
Your response - act like an arrogant a… and heap more sh.t. The comparison says all.
Chiming in, I’m the exact opposite. I really dislike iCloud (or other) syncing for writing projects. Not for the data security aspect in relation to hacking, but just the friction and possibility for damage that can and does happen. I’m all for syncing simple stuff that I actively want to sync and have available on lots of devices (eg via Google Keep), but when it comes to things that brew over a long period of time, I actually want them ring-fenced from the cloud except for periodic backups. I’m pretty sure that was the intention, but just adding in my bit to say that if there is a Scrivener Lite one day I very much hope Scrivener Heavy will still be a priority.
Could revision to documentation/videos diminish simplicity concerns? I think the current documentation is excellent but could be improved by front-loading The Basics info (using text and images)––info such as “Save”, “Auto-Save”, “Save As”, “Backing Up”, “using Recents”, etc.
People have learnt from smart phones that they don’t need to understand anything. Most iOS and Android apps are fool proof. You can’t make fatal misstakes. When a Mac or PC is treated the same way things can go very wrong.
Hi Keith, and others.
Window user here. Started with 1.6 (I think) and moved across to the Beta with 9 (I think).
I hate subscriptions although I am now using a hell of a lot of them. As I also run a publishing house and 2 personal computers Adobe and Microsoft have locked me into their ecosystem. Luckily I can afford but that doesn’t mean I like it.
I started with the Microbee CPM desktop, and had an internal network in the home years before anyone at work started doing the same.
I haven’t spent a lot of time learning Scriveners rather unique layout. I much prefer to just write, and drag chapters around in the corkboard. A year ago I was still drafting a chapter in Word and copying/pasting it into Scrivener because I could just work on it in dropbox on any of my computers, or multiple android tablets. I’m now comfortable on editing the RTF file using OfficeSuite (one of the few Android RTF editors) and manually synching the file. I am SO waiting for the android version to become available.
I also run separate projects for my multiple trilogies, and more importantly a separate project(s) for research information. I have a number of large maps/photos in research and saving them in a project was taking too much time.
I’m happy(ish) with the progress on the Windows Release Candidate, but frustrated that I can’t give you some money for it - although if I get frustrated enough I guess I could just buy another copy. Hague Publishing has just acquired an intern so perhaps I could donate it to her.
All the best in your deliberations.
Thanks to everyone who gave their thought, and KB for sharing his decision space! The only option for potential simplification I haven’t seen mentioned is to step away from RTF and embrace plain text (visually styled in the editor). Apple’s text frameworks are not being updated as far as I can tell in macOS releases (as they keep their proprietary engine for Pages), but KB has invested a lot of effort in extending features and working round its bugs, so I understand it would be a big step to take. My feeling is that it would reduce a lot of complexity (compilation would rely more on other established tools thus saving more developer weight), but only KB really knows that for sure…
On the iCloud front, if that was the major factor to prompt redevelopment, I would argue against. I have the both the 2TB iCloud plan and Dropbox premium. There is no comparison IMO in terms of reliability. Some apps (Bookends) work well syncing their database via iCloud, but then things like PDFs (simply stored as files in an iCloud folder) or larger documents get stuck, don’t sync and are generally a pain (not every file, but sometimes it feels like 1 in 10 which is far too much). Dropbox syncs everything always, I have never had a sync failure in the many years I have used it — say what you will but technically it is utterly reliable. This is even in China, where Dropbox is forced to work through a VPN but iCloud servers connect without issue.
Back to subscriptions: iAWriter developer blogpost on their thought processes on subscriptions, for Android they are thinking about offering both models — ia.net/topics/subscription-or-no-subscription
Thank you for this! I went with Scrivener BECAUSE IT WASN’T a subscription based product. I prefer the “Like it, buy it, done” model over this ever-increasing model of “keep buying the same product over and over again” model.
My opinion? Major build upgrade, charge for it. Minor improvements on the same build? Update it for free.
Subscriptions are for magazines, not software.
There are other models as well that mix the two extremes. One piece of software I have used (in the ham radio world) uses a model I’m somewhat fond of – you purchase the software outright, which also gives you 12 months of feature upgrades and support. After your 12 months is passed, you can still download new updates, and you will receive the benefits of any bug-fixes that apply, but you will not be able to access new features (support for new radios, new modules and modes, etc.) unless you purchase a (smaller price) update, which resets your 12-month clock. So you can go for years getting free bugfixes if you have everything set up the way you like it, but if you decide you need a new feature, you pay for the update and get it.
It’s probably a lot more chaos to track on the software side of things – they’re Windows only and don’t go through an app store which helps reduce the complexity – but it’s a neat idea.
Hi Devin, W7CCE in Gilbert here.
I have the same contesting software. The difference is that you can go a long time - years - with the same software if you don’t need the extra features, and as you know a bunch of competitors pop up at every delay. On year I bought a new radio, the software didn’t exist, so I wrote my own. It was surprisingly easy but that was my job in those days.
So my vote would be continue present course. Once Version 3 is fully out and debugged on Windows and Apple there will be some time to think about this. My caution is that the schemes to wring every ounce of available funds from the user base have killed more companies than a COVID lockdown. The returns are often marginal, overhead grows, customer service expands, and it de-focuses the designers.
You may want to consider moving to the USA, but it sounds like you are doing just fine, and anything to slow or interfere with productivity should be avoided like the plague until move ahead a bit. Then you have to find a city that’s not burning, and learn how to shoot! Seriously I have one question, and that is are there many bugs appearing in the Windows 3.0 version that are found to exist in the Apple version too, or are they pretty much a consequence of the new code/environment?
On this end I dual boot a Mac so I hear “scaling” for Windows and start to sob. Regardless good luck to LL on this project. PS If you do need $$ you might consider asking for contributions. That can work.
/Len
I will support Scrivener whether it’s one-time pay, yearly pay like Agenda, or subscription.
Just please update the iOS app 
It’s got the potential to be so utterly glorious.
Please do not do so. I also have a Ulysses subscription. During the year, I got a new credit card. Late on a Sunday night, with no warning, Ulysses sent a renewal through, Since the credit card number was no longer valid, the renewal was declined. So they tried again.
And again.
And again.
Until the bank’s security protocols were activated. Now my Apple account is suspended. I am stranded overseas due the pandemic and the nearest branch is 8000 km away.
(I won’t go into the issue of how an Apple Store license is a ‘lesser’ license, but it is.)
Ulysses’ corporate couldn’t do anything, or so they claimed.
Bad store design! Best practice would be to let it decline once, maybe twice, then send the customer an email asking what they want to do. And when the failure can be anticipated – like the card is past its expiration date – send the email first.
Katherine
Oh, heck and more heck no! If they want to license collaboration or reasonably limit the number of synch documents or services or other premiums I’d certainly understand this, but if or when the basic application turns into YA subscription model, that is when I export my docs and just go somewhere else. I’m a hobbyist, not a superuser or dependent professional.
