atk VS fyne

You might want to look at github.com/visualfc/atk. Tk is a toolkit traditionally considered unsexy but it is 1) rock solid 2) cross platform, while using native Win32 API to render its widgets.

I think interp layer of atk is a good entry point for minimal API. Then you can reuse higher level API of atk and check by demo.

For creating simple desktop apps for (mostly) my own use, the ones I found working best for me where two binding to existing ui toolkits: - Tk: https://github.com/visualfc/atk - and a small custom wrapper around fltk I've written Both have some issues, but e.g. fyne and some of the immediate mode ui's I've looked at where lacking some features, and I couldn't build therecipe/qt (I don't event know if it's still maintained).

If you want to look at something a bit bigger I can also suggest looking at Fyne (the toolkit that I’m working on and using to build the app): https://github.com/fyne-io/fyne

Tauri is definitely a hot SEO keyword!

I had not heard of https://wails.io before for Golang GUIs, only https://fyne.io which renders its own controls.

And this is how https://github.com/go-gst/go-gst, https://github.com/go-gl/glfw, and even https://fyne.io/ are using system libraries to propose a lot of functionalities.

It would be great if we could add support for Flatpak portals in https://github.com/fyne-io/fyne but I find the portal documentation complicated (especially if preferring to use D-Bus instead of accessing libportal using C). Does anyone have code examples for using portals from Go code?

If you fancy Go, there's Fyne. I don't work in the space so I cannot judge it.

https://github.com/fyne-io/fyne