fyne VS shadcn/ui

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

Check out the beautiful UI crafted by ShadCN over at the deployed version of our app — sign in with Google and get some sweet cards! Plus, the entire project is open source. Grab the code from GitHub.

It’s Headless so you can use it with whatever UI components you have in your project and as with everything in TanStack it’s type-safe! In this example we'll use components from shadcn/ui to build the form but you can really make it work with any UI library.

Shadcn UI

You can access shadcn/UI using the following links. Official Site Github Repo

I build an Angular or React app or smart component that uses the store in an Nx monorepo. I use the Shadcn UI in React apps, and the Shadcn-based spartan/ui in Angular apps, so I can use almost the same app architecture both in Angular and React.

Finally, for our front end, we’re going to be pairing Next.js with the great combination of TailwindCSS and shadcn/ui so we can focus on building the functionality of the app and let them handle making it look awesome!

Shadcn/ui: I've never tried it before but have always wanted to switch from MaterialUI

Honestly the ergonomics of heavily customizable generic component libraries aren't great. Copy and pasting a simple component to make the specific customizations you want helps reduce JS ecosystem churn and dependency pain. Popularity of libraries like shadcn/ui [1] are good acknowledgements of that.

[1] https://ui.shadcn.com/

shadcn/ui