Scriveners future?

Hello! Participated in the survey last year and came back to find some news in the forums. Did L&L ever comment about the future of Scrivener?

Daniel :slight_smile:

1 Like

They regularly remind users that it is their policy to not comment on future plans or roadmaps.

1 Like

From the developer: Big Scrivener Survey Results - #2 by KB

1 Like

But nothing since December last year?
(Wondering not criticizing.)

1 Like

Yes, they’ve been focussed on getting V3 Win out and ongoing development work. Keith has commented that he’s hard at work.

I’d rather he do that than waste time ‘chewing the fat’. I don’t need L&L to keep reassuring me that they have future plans every month or so.

1 Like

Not that I’m aware of, but as they had 25,000+ responses to the survey I’m sure it will have some impact on Scrivener’s future development. That said, I’d hate to try and distil all those responses into a blog post!

Now, I’m back off to work instead of wasting my time here chewing the fat :roll_eyes:

2 Likes

The future of Scrivener: we hope to have one.

Beyond that, no, we do not comment on future plans.

6 Likes

My expectation is that Scrivener will evolve over the next six years beyond writing software into a full operating system for laptops and mobile devices.

ScrivOS, with its strong lineage in data integrity, will save everything every two seconds and create regular whole system backups, which will lead to its blossoming in all creative and security conscious work settings, although the early versions inclusion of internet browsing history in these backups will lead to a dramatic increase in divorce rates.

9 Likes

And it will be a boon to hard drive, NAS manufacturers and cloud services as those backups drive a need for large storage. :upside_down_face:

Finally, something to replace the tyranny of emacs.

2 Likes

What’s taking them so long to get this update out? Everyone has been talking about it forever, yet we see no results. What’s with that? Will it be a free upgrade, or will I be forced to pay? Is it going to be compatible with other versions?

2 Likes

:grinning: ScrivOS will be ready next week. Or next year. Or in five years. (Too soon?)

In response to @DanielHenriksen, though, I’ve been meaning to write a blog post about that survey for months - thank you for reminding me. I’ve been reviewing some of the data again ready to put the blog post together over the next couple of weeks.

It was a hugely helpful survey (thank you to everyone who took part) but - who knew? - it turns out that writers love to write, and we had well over two million words of text-entry replies.

As for the future of Scrivener itself, I can’t comment on that just yet - we still have a lot of internal discussions ahead of us, and Scrivener 3 for Windows has only been out for a few months. Which isn’t to say that I haven’t been very busy these past couple of years.

All the best,
Keith

9 Likes

From a UI/UX view, I think it’s great design. Version 3 seems stable and amazing. I think I spend more time analyzing the product and its internals than writing. I should be writing, though. Great product!

However, I bet the QT licenses are killer. Visual Studio 2022 is on the way out and .NET has come a long way for cross-platform development. That may be a little cheaper than the QT route. :slight_smile:

As far as future, I think some of the items like cloud sync integration would be nice. I do have Scrivener hooked up to OneDrive and it works amazing. I previously used Perforce to source control my work, but with OneDrive, I can “sync and write”

Good job, Scrivener Development Team!

1 Like

Yeah, that. Also, Visual Studio Community edition is free. There’s nothing cheaper than that :joy:
(Please, anxious nerds, refrain from pointing out all the missing features in the Community edition vs Professional/Enterprise. None of them are a show-stopper to build an app like Scrivener.)

Also, I would suggest Scrivener’s team, if they have some knowledge of C#, to take a look to .NET MAUI (still preview, yeah yeah). That framework could make Qt useless, if you are proficient in C#, of course.

Maybe it’s worth it to take it into consideration for the next Scrivener iteration (One VS solution, one code base, cross-platform, Android app, etc…). Or maybe not, your choice.

Wait, you want the Windows team to start again from scratch and rewrite the whole thing? That might take some time. :slight_smile:

We’re definitely not interested in a cross-platform codebase for macOS and Windows. That does mean that the Windows version will always trail a little behind (because I do all the design and prototyping on the Mac), but I’m not a fan of cross-platform apps at all - they never look at home on any platform to me. I love the Mac frameworks and wouldn’t want to give them up. (And just look at the furore caused among Mac users recently by 1Password moving to Electron.)

All the best,
Keith

5 Likes

I don’t. Just giving my humble opinion as a seasoned dev. I thought it’s worth considering on the long run.

Everytime this very sentence is spoken/written, a dev out there dies. No offence, just some random sarcasm. :smile:

Whatever floats your boat and guarantees Windows users like me updates for years to come, sounds fine to me.

Anyway, no Android app seems a huge missed opportunity to me, but I understand why there isn’t any. Without cross-platform, would be a pain to develop and maintain three/four different apps

True, most of the times, due to devs lazyness, usually.

To be clear, I love Scrivener. I’m not criticising anything.

Cheers,
Matt

1 Like

Hi Matt,

I haven’t been a dev for decades, so I’m going to stay out of this, except to say that apparently the QT framework can be reused on Android, and L&L plan to leverage Win Scriv on their Android build.

From a 2019 blog post by one of L&L’s Windows Devs:

"Finally, something that’s not visible to users is that we have the Scrivener for Android backend completely abstracted and built into the Scrivener Windows desktop, so once 3 is out we can focus on the Android interface only as all the heavy lifting on the complex backend has been done and dusted. "

Then again, it’s possible I’ve misunderstood what’s being discussed here. :man_shrugging:

Best,
Jim

1 Like

Second that!

As for 1Password I have a free licence from my old job that does expire in the future. Given their move to Electron I am actively researching alternatives and don’t intend to hang around for the expiry. There is a free lifetime licence I have from from same job with a competitor, and I use Nord VPN and see they have their own Locker though haven’t investigated. The 1Password competitor doesn’t look quite as polished as 1Password did, and the fact the company approved 1Password for internal use was the deciding factor. Now that I’ve retired, I have no systems that connect to company VPN so can ditch company approved software as needed.

Nothing in Keith’s response said there wouldn’t be an Android app. QT can be used for Android development and there is a post referred to above.

I’ll reserve judgment on the ‘missed opportunity’ as it depends entirely on whether there is a sufficient body of Scrivener users prepared to actually pay for an Android app. I seem to remember over the past couple of years on the forum something like 5-10 people actually saying they would pay for such a version. There were several who openly said they expected it for free to ‘stimulate PC/Mac Scrivener sales’. I think more potential mobile users already have it for PC/Mac.

Unless you understand the reasons why Qt was chosen to begin with, this suggestion is probably not nearly as helpful as you think.

That would be great, Jim :blush:
I really hope there’s one, some day. I really do.

Nobody said will never be an Android app, but it’s a fact there is none since years.

And you are proving my point. Without sharing code bases, dedicated apps for specific platforms are expensive to develop and If they are expensive, they are not worth it without a solid user base willing to pay.

But again, @KB already stated his point, so there’s no need to further argue on that.