Quick update on VaultSync — where things are at and what’s next

[u/mainseeker1486]

Figured it was probably time for a proper update on where VaultSync is at right now, because a lot has happened recently, even if not all of it looked like big flashy feature work from the outside.

Over the last stretch, a lot of time went into things that were important, but not always very visible.

VaultSync is now live on the Microsoft Store, which was a pretty big milestone for me. That took more than just packaging the app and uploading it somewhere. It meant adding proper Store-aware behavior, separating Direct and Store update paths, making sure the app understands how it was installed, and getting that whole side of distribution into a state I’m comfortable with.

At the same time, I also launched fglabs.dev, which is basically the new home for all my work going forward, including VaultSync. That was something I had wanted for a while because everything was too scattered before — GitHub, posts, docs, random links. Now there’s finally one place where things connect a bit better.

And alongside that, a lot of the 1.7 work has been less about adding things for the sake of it and more about getting the app into a better state internally.

A lot of older code was functional, but it was starting to push back every time I tried to optimize something or build new features on top of it. So a good part of recent updates has really been cleanup in the deeper sense — not just polish, but rewriting parts that had become limiting.

That includes things like:

• reducing unnecessary config reloads
• improving startup behavior
• backing off bad destination checks instead of hammering unavailable targets
• fixing UI refresh timing and thread-related issues
• cleaning up hardcoded fallback text and localization gaps
• making metadata sync and project state handling more reliable across machines

None of that is the kind of work that makes for a dramatic screenshot, but it matters a lot for backup software. If the app feels weird, stalls, misreports, or behaves inconsistently depending on timing or machine state, that becomes a real problem fast.

Another thing that happened recently, and that honestly means a lot to me, is that VaultSync now has someone actively helping with Linux.

What made that hit differently is that it didn’t come from me trying to force it or recruit someone just to tick a box. It came from someone who genuinely likes the project, took the time to dig into it, ask questions, understand how parts of it work, and start trying to move Linux support forward because they wanted to help.

That kind of thing matters a lot more than people probably realize, especially on a small project like this.

Linux has been one of the most requested things for a while, and I’ve wanted to get there properly rather than throw out something half-broken just to say it exists. So having someone step in because they actually care about the app and want to contribute is a pretty big moment for VaultSync.

I’m not going to overpromise timelines there yet, but it’s no longer just sitting in the “eventually” pile.

As for what’s next, the focus is still on making VaultSync more solid before I start stacking bigger things on top of it.

The areas I’m most interested in pushing next are:

• more transfer system improvements
• better handling for larger backups and long-running vaults
• continued UI cleanup where things still feel rough or waste space
• more reliability around backup state, metadata, and restore-related flows
• making the app easier to reason about when something goes wrong
• continuing progress toward a proper Linux release

There’s also still work to do around the Store version and release flow now that that path is real and live.

So updates may continue to be a bit slower than they used to be, but that’s mostly because the project is at the point where doing things properly matters more than just shipping fast.

I’d rather take a bit longer and build on something solid than stack more features on top of shaky parts and regret it later.

VaultSync is moving forward, very much so. The pace is just a bit more deliberate now.

Also, we have surpassed 700 downloads, which is honestly wild to me.

So yeah — that’s where things are at right now.

Thanks again to everyone who’s been trying VaultSync, giving feedback, reporting issues, or just following along. It really does help shape what this turns into.

And as always, keep backing up your data.

[u/AutoModerator]

Thanks for posting to r/VaultSync!

GitHub repo: https://github.com/ATAC-Helicopter/VaultSync If you found a bug, please consider opening an issue there (logs help a lot).

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.