The state of the windows Desktop app

Support
1

Hi, what’s the plan for the Windows desktop app? 0.24.4 works but is outdated and unsecure. 0.24.6 has known bugs since feburary that prevents it launching, and the suggestion in that thread to just run the unstable client instead also is moot as that fails to launch aswell.

Why isn’t the backend/api just bundled with and started as part of that app as a self-contained, easy to use package? Why isn’t the CORS config setting handled when connecting to a localhost(ed) server?

I’ve spent an hour now between the slow downloads and complete mess of documentation for the desktop app install(that isn’t clear at all) and still ended up nowhere.

Is there any plans to improve that in the future?

Best Regards;

2

Which one do you mean?

Do you see an error?

Open for a PR :slight_smile: I’d say this comes from Vikunja being a web application first, and only later a desktop application.

I’ve just added an item for this to the backlog.

Sure! We can only fix what we know about, so you reporting this here is great.

I’ll also look into the download speed. From which location are you downloading?

3

Hi, thanks for the reply.

0.24.6 bug referring to this thread, same error as i saw:

unstable version error: (Vikunja Desktop-unstable.exe 04/15/2025 08:05:28 AM +00:00)

Vikunja_Desktop_2025-04-15_10-21-26
Vikunja_Desktop_2025-04-15_10-21-26585×466 8.35 KB

Wouldn’t a PR first be for if i wrote the code/logic to bundle it during the build process? :slight_smile:

Thanks for adding the CORS config change to the backlog.

I’m downloading from Europe/Denmark, but it seemed to vary from file to file. if you serve all files from the same CDN/server i’d probably just chalk it up to routing weirdness for now as i’m unable to reproduce it at the moment.

Best regards

4

This is… interesting. I’ll take a look.

Yes, you’d need to make the code changes and propose them.