You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Let's explore the possibility of developing a cross-platform client application. This application should run on the web and be compilable as a native app on Windows, Linux, MacOS and Android.
By doing so, we can gradually migrate features from the current GameVault Client to a cross-platform framework and web-based user interface. This approach will also address the following issues:
I find tauri really fine but there is some issue with the flatpak dependency isued ( it the main way to install app on some system like steam deck or fedora silverblue :/ )
changed the title [-]Crossplatform Web-Based Client Application that could also serve as a simple Web UI[/-][+]Proof of Concept for a Crossplatform Web-Based Client Application that could also serve as a simple Web UI[/+]on Sep 17, 2023
We've made progress in rendering elements and creating a login feature in the Avalonia WASM PoC. However, there's an issue with securely storing login credentials using web technologies right now. In the future, we'll likely need a more robust authentication flow that utilizes cookies. For now, we're planning to temporarily store credentials in the browser storage, but it's not a secure method.
Our current issue is figuring out how to use the browser storage from Avalonia, to cache and save stuff, and we're actively working on that. We'll keep you updated on how things are going.
Avalonia WASM does not seem mature enough to rewrite our entire client application in it at this point in time. We are taking a closer look at UNO right now.
changed the title [-]Proof of Concept for a Crossplatform Web-Based Client Application that could also serve as a simple Web UI[/-][+]Crossplatform Web-Based Client Application[/+]on Apr 4, 2024
Quick update:
We have now decided on Tauri + React as our tech stack, and we are currently developing a web interface that will be delivered directly with the GameVault server. Tauri will also make it possible to create a cross-platform client app out of it.
This should cover the basics for now, such as the library, community, and user management (Administration).
Migrated from Phalcode/gamevault-app (was #284) as part of the GameVault 2 release. GV1 is feature complete, so the remaining backlog moves here and gets re-checked against the new frontend.
Closing because this is what GV2 turned out to be. The client is a Tauri app with a shared web build (vite build to dist, served by nginx), and the old client's features are being rebuilt here.
Activity
yodatak commentedon Aug 8, 2023
I find tauri really fine but there is some issue with the flatpak dependency isued ( it the main way to install app on some system like steam deck or fedora silverblue :/ )
tauri-apps/tauri#4426
https://tauri.app/blog/2023/03/20/tauri-2-0-0-alpha-4
(now we are in alpha 6)
we should maybe start with tauri 2.0 because of these ^^ and tauri v2 will support android and IOS
some flutter app in flathub
https://flathub.org/apps/search?q=flutter
some that use tauri, Cinny and Pocket Sync
https://flathub.org/apps/io.github.vemonet.EmojiMart
some that use tallwing frontend
https://riftshare.app/
yodatak commentedon Aug 8, 2023
for tauri
https://github.com/tauri-apps/tauri-mobile
Alfagun74 commentedon Aug 9, 2023
We are currently also checking if .NET Blazor would be a possible Alternative as we could then at least reuse the code.
yodatak commentedon Aug 10, 2023
. Net Blazor don't seem to be Linux dotnet/maui#11738
mhrastegari commentedon Aug 11, 2023
Hey @Alfagun74
Have you checked BitPlatform's templates?
Alfagun74 commentedon Aug 11, 2023
I did. Also saw blazor electron as an option but then the app runs on bloated and resource hungry chromium
[-]Web UI[/-][+]Crossplatform Web-Based Client Application that could also serve as a simple Web UI[/+]Alfagun74 commentedon Sep 17, 2023
We're currently exploring Avalonia's fantastic new WebAssembly feature. You can check it out here: Avalonia WebAssembly Feature.
This can be developed as a web-based app and also as an on-premise app for various platforms:
Our primary focus will be on the following, in this order:
We will keep you updated here as soon as we have a simple Proof of Concept that this could work.
[-]Crossplatform Web-Based Client Application that could also serve as a simple Web UI[/-][+]Proof of Concept for a Crossplatform Web-Based Client Application that could also serve as a simple Web UI[/+]Alfagun74 commentedon Oct 9, 2023
We've made progress in rendering elements and creating a login feature in the Avalonia WASM PoC. However, there's an issue with securely storing login credentials using web technologies right now. In the future, we'll likely need a more robust authentication flow that utilizes cookies. For now, we're planning to temporarily store credentials in the browser storage, but it's not a secure method.
Our current issue is figuring out how to use the browser storage from Avalonia, to cache and save stuff, and we're actively working on that. We'll keep you updated on how things are going.
Alfagun74 commentedon Nov 20, 2023
Avalonia WASM does not seem mature enough to rewrite our entire client application in it at this point in time. We are taking a closer look at UNO right now.
7 remaining items
[-]Proof of Concept for a Crossplatform Web-Based Client Application that could also serve as a simple Web UI[/-][+]Crossplatform Web-Based Client Application[/+]Yelo420 commentedon Sep 16, 2025
Quick update:
We have now decided on Tauri + React as our tech stack, and we are currently developing a web interface that will be delivered directly with the GameVault server. Tauri will also make it possible to create a cross-platform client app out of it.
This should cover the basics for now, such as the library, community, and user management (Administration).
Alfagun74 commentedon Nov 6, 2026
Migrated from
Phalcode/gamevault-app(was #284) as part of the GameVault 2 release. GV1 is feature complete, so the remaining backlog moves here and gets re-checked against the new frontend.Closing because this is what GV2 turned out to be. The client is a Tauri app with a shared web build (
vite buildtodist, served by nginx), and the old client's features are being rebuilt here.