With all due respect, we have no idea what that amount compares to L&L’s current revenue and sales. Making assumptions in absence of any data is not productive.
I don’t really mind how long this has all taken (though of course I wish it had gone by faster), and I understand the complexity involved in what the L&L team are doing. I don’t think they can be criticized for the time it takes them to complete such a big project, but I DO think they should be criticized for continually promising dates they don’t deliver on. It is unprofessional.
I doubt anything will make me stop using scrivener, it’s such an amazing tool and I’m sure I’m not the only one. who feels that way. There’s no point of me making threats about moving over to a different program, because I won’t (unless something else got released that had all the same functions with a more reliable team behind it), so I guess from the L&L standpoint, they don’t really need to do anything but what they’re doing. No one holds them accountable, and I doubt they’ll lose many clients over this. The only consequence of their continuous broken promises will be a poor reputation that will probably stop quite a few users from recommending their program (I know I used to rec it all the time, and I haven’t done so in a long while now–not that the 20 or so people I might have brought in would have made a lick of a difference), and new writers, or writers who are still using word and google docs (90% of my writing friends use these two programs) won’t be moving over to scrivener.
Complaining won’t do any good, but neither does blindly defending L&L and hating on those that are fed up with dates that never hold up. I don’t really know why I commented, as I basically never post on forums or anything, but something about this just bothered me.
Which is why I said L&L can use my feedback any way they see fit. It’s their decision based on their insight into their books and revenue. If my feedback is an outlier, ignore it. All I can do is offer my perspective and some numbers in a forum called “Feedback”. Others can do the same. As a business owner myself, I’d appreciate this kind of feedback. I’d rather have an early indication that customers will or won’t be returning instead of realizing too late that I won’t meet my targets.
Hello,
L&L head honcho (and sole macOS and iOS developer) here. There’s not much I can say in response to all of this really, other than “sorry”, which isn’t really going to cut it.
Fair enough, I can’t really disagree with that, or with your assessment that this batters our reputation, which is gutting. I’d also like to emphasise two things:
-
As long as it’s done as politely as possible given the circumstances, it is absolutely fine to post grievances and express frustrations here. At this point, it would be unreasonable of us to expect everyone just to “put up with it”. I don’t want people to think that the forum is only for praise (as much as we like that).
-
We do care. We’re not sitting around laughing like Skeletor at missing yet another self-imposed deadline.
It’s fair enough to suggest that we hire more developers and so on, but the reality is more complicated. As Astaff mentioned, we have tried this in the past with very little joy. We went through two different developers on the iOS version, each of whom spent a year or more on the project without being able to get it to completion. We then hired a company specialising in building iOS apps, and even they weren’t able to do it to an acceptable standard, so in the end I took the project on myself. I’m still trying to find another developer to come on board and help. (There’s also the logistical problem of how we have no offices and are scattered around the world, making it very difficult to train up new developers.)
As for someone taking responsibility, it is unfortunate that the blog post phrased things like that, because no, no one is getting fired. If we fired our Windows developer then there would be no Windows version at all.
What we should have learned from the iOS version is never to give a release date. But people don’t like that, either: people want at least a vague idea of when something will be ready, which is why we originally said Q2 of 2019 (actually at this point I can’t even remember if that was the first thing we said - I think we said some time in 208 first, argh). Honestly, we wouldn’t have made the update free for v1 users from late 2017 onwards if we thought we’d be giving away nearly two years of free licences - we really thought that it would be done by now. But it’s not. It’s just not in a state we can release, with whole parts of the UI in Compile not fully hooked up yet. Which is a horrible place to be for all of us.
So yes, there are certainly some hard lessons we need to learn from all of this. But sadly there is no short-term fix. All we can do right now is have the Windows team keep coding away like mad with the rest of us testing builds and cheering them along until it’s ready for release, and apologise like crazy to disappointed users in the meantime.
Let’s try to give a little more leeway and have a little more understanding on both sides, though. It would be great if those expressing their frustrations didn’t accuse those defending us of blind loyalty or zealotry, and those defending us (which we appreciate!) should make allowances for the genuine frustrations of those who were looking forward to having a completed product by now. Personally, I genuinely appreciate how much all of you care about Scrivener. Thank you.
All the best,
Keith
Thanks for the response KB. Appreciated. I do get there are struggles on the devs side. And I understand you appreciate Scriv users defending your team, but it does not help frustration levels to feel constantly delegitimized by their defenses, so I hope you at least understand that, and I’m assuming you do, given the nature of you’re response, which, again, I appreciate.
I understand there is not a short term fix, but there is the additional issue of the promise that Windows would catch up to Mac. It does exacerbate the issue quite a bit, and I understand that perhaps you don’t have a fix, but it would be nice if at the least devs and such stop assuring that Windows is as much of a priority as Mac, because no matter how much it’s said, it is the pure and simple fact that Windows is still years behind Mac and updates reach Windows users years later, so it’s said, but it sure doesn’t feel like that and that seems to sow discord.
Hope you can understand that.
Thanks.
No demands. Just the irony of “held responsible”. I don’t want the Win dev fired, but it is a pretty weak statement that doesn’t hold a lot of weight. I didn’t see it in the initial post but where we’re standing right now, it is a pretty meaningless thing to say.
As for “stop sulking and move on”. No. Not at your demand certainly. The more you say “stop sulking and move on” the more it fuels the annoyance. So really, if you want people to stop you should probably change your responses a bit.
Thank you for your post, KB.
Is that true: Is there one sole Mac developer - KB - and are there two Windows developers - Lee and Tiho?
@ForgottenGold: I definitely understand, and don’t want anybody to feel that their frustration is being legitimised. We have created the frustration ourselves, so have only ourselves to blame for users venting at us over this.
@Rubinstein and ForgottenGold: It is indeed true that there is only one Mac developer (myself), and two Windows developers (Lee and Tiho). I do most of the design (with some help from Ioa, our UI designer Janik and user suggestions) and all of the code for the macOS and iOS versions of Scrivener and the macOS version of Scapple; Lee and Tiho handle the Windows versions of Scrivener and Scapple. This, to an extent, is why we say (and mean) that we are just as serious about the Windows version - it has twice the number of coders as the macOS version. (They’ve had to build a lot of things from the ground up that macOS provides “for free”, though, I believe.)
We’ve put other resources into it too, though. Jennifer, who has an incredibly in-depth knowledge of Scrivener for Mac and who used to be one of our key support personnel, has for a long time now been moved over to working with the Windows team to test all features against the Mac version and to check nothing is missed. And Ioa, who writes the manuals, has been nearly full time working on the Windows manual and testing every feature against the Mac manual.
None of which has got us there anything like on time, of course, so at this point this is all academic.
All the best,
Keith
I understand the disappointment, but I think the reasons for not releasing by the deadline are pretty sound. If the product is not ready, is not up to standard, it is far better to delay than to release something that is half-finished or will require extensive patching and updates to fix bugs.
The beta is still usable in the interim and if that is an uncomfortable thought, Scrivener 1.x or is it 2.x is still a valid option. I for one am quite happy to wait as long as necessary for the final product because I know it will be up to standard. It is refreshing to see a company committed to their standards.
KB, thanks for that clear and helpful indication of who does what. Especially considering that Windows programmers have to create stuff (spell checker is the one I actually know about) that the Mac OS supplies, it’s really not surprising that such a massive update should take so long. Frankly, I’m in favor of small software developers seldom or never indicating release date goals. It only agitates the herd. 
(Speaking as one of the herd, but not an agitated one.)
Lest anyone forget, there was this same sort of distress about the release of iOS Scrivener (for 4 years, I think). And I saw mention of Scrivener 3 for Mac in the works at least three years before it was even in beta, too. And once Scriv3Mac was in beta, oh the pestering as to when the release was going to happen…
KB, I say this with the deepest respect—Please, please, don’t ever even hint as to when a targeted or projected or anything release might happen ever again. As DavidR said, “It agitates the herd.” Not even though I show up on your doorstep in Cornwall begging on my knees for the next version release date of Scrivener iOS. Ignore that crazy old American lady. Just step right over her and carry on with, “We don’t comment on release dates.”
“We don’t comment on release dates.”
Yeah, I gotta agree with this advice, but I’d add that in the future you might earmark a few of the bigger threads and say “if you want to know why we don’t comment on release dates, you can see what happens when we do and those dates are missed.” Something along those lines.
The only time to give a release date is when the whole project compiles successfully, has passed QA, and the code is locked. AND when documentation team can give you a completion date.
Every date sets an expectation. That does nothing but create stress for the developers. And if the date is missed (and it’s nearly always missed–ask any developer), the date set creates disappointment in the customer base. Everyone loses.
In fact, when Version 4 is under development (it is under development, right? ), long-time members here in the community should stand at the ready to calm down expectations all around and repeat the party line: “We do not comment on release dates.”
For myself, I’m going to remove the beta and continue using 1.9 (gotta keep 'em separated) and basically forget I ever even heard of version 3. Boy am I going to be surprised one day!
Here to register both that I understand, but am still disappointed. Unlike most of the gripers, I understand programming and being behind the 8-ball (I’ll be doing that all weekend 
and not writing or spending time with my family because deadlines others have failed to meet) The point is I get it. And as a developer/writer/user and all other things I ultimately do want a product that works.
But there’s a problem. Mac and Windows are drifting too much. The latest version of Mac won’t run (last I checked) Scrivener 2. And Windows won’t run Scrivener 3. That means I can’t work cross platform and haven’t been able to do it for some time. 6 months, I told myself, I could deal with.
Maybe a year, not so much.
I’d take a stable version that didn’t allow me to compile at this point, but that I could write in without having to install new betas every few months. I can compile on mac when/if I need to. But I need to be able to write on a windows machine, I just do.
Sigh. I know.
Goodluck/Godspeed/Thanks for what you’ve made so far.
We are all counting on your team.
You can write in the V3 Win Beta and compile safely on V3 Mac already.
You say you don’t want to constantly install new Betas, however the process can be no different to installing a point update that happens with 99% of programs from time to time. Help > Check For Updates
The few little hiccups on the beta have no impact on data integrity and the ability to write without concern other than normal prudent backups.
To the OP, seems not recommending Scrivener just because the Win V3 version is a bit late is case of cutting off nose to spite face and depriving others of the best tool for the job.
The current Win 1.9 is the best in class product currently available, works just fine, PLUS, it comes with a free update to V3 when released.
Isn’t it a bit spiteful to deprive those other writers you supposedly care about of the opportunity to use the best program out there, and get a free upgrade, just because you have a snotty over V3 being delayed a few more weeks?
Just thinking out loud…
I can’t describe how disappointed I was to learn yesterday of yet another missed deadline, another broken promise. And as for the developer accepting responsibility for this, what does that mean? Does it mean he won’t get paid, a loss of income? For me it does mean a loss of income, because as a professional writer I’ve delayed several projects because I wanted to do them in Scrivener—and now I’ll miss my deadlines and might not get paid. I teach creative writing, and now I no longer will be recommending Scrivener to my students.
Beobuck, I’m disappointed too. As far as I can tell “responsibility” in this case means only that we can all go out and buy voodoo dolls, name them Lee, and stick pins in them or run over them with our cars or dress them in unattractive clothing.
But did you read astaff’s post just before yours? Scrivener 1.9 works well and is stable; the only problem might be that its projects can’t be opened in the current Mac version, and vice versa. Also, many people are working successfully with the v. 3 beta. If you can get your projects done using v. 1.9, then you should be OK, eh? As for your students, much as we may be disappointed over the missed deadline (which should probably never have been publicly announced in the first place, but that’s another subject), why deprive them of a good tool that’s likely to get better by the end of the term? That’s my thought, but I’m not in your shoes.
No, it’s not spiteful. It’s prudent.
I think the OP is quite right to not recommend Scrivener to Windows users at this time. That buy-it-now-get-a-free-upgrade-later deal has become nothing more than a bait-and-switch. If v3 is truly released in only a few more weeks, then those new users have nothing to lose by not learning about Scrivener now.
And if, as is far more likely, v3 is not released for many, many, many, many, many more weeks, then they haven’t wasted their time by getting sucked into the morass of perpetual betas and missed commitments.
It seems to mean that he spent the day in hiding while Keith ran interference for him. Keith made several sincere apologies here and on the blog while Lee was conspicuous in his absence. Totally in keeping with making the announcement that they were missing another deadline in the Beta 22 release notes instead of in a more public space like the blog. He left that chore to Keith, too.
Lee always says he takes responsibility, but the ones who really will be paying the price are the customers, like me, whose writing deadlines will be missed because the Scrivener Windows V. 3 they had counted on for their projects is not available by the promised date.