76
Making GUIs, how do you pick?
(lemmy.world)
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Follow the wormhole through a path of communities !webdev@programming.dev
Blazor is incredibly versatile in terms of where and how you run it. The UI is in HTML and CSS, the generated runtime bindings in JavaScript, but you can code the backend as well as frontend logic in C# / .NET / Razor template files.
It can render on the server or client, even work offline with WebAssembly and Service Worker, and dynamically switch between or combine them.
You can also integrate it into Windows Forms, WPF, or multi-platform .NET MAUI with Webview2, which will render "as a website" while still binding and integrating into other platform UI and code.
Your goals of "neat little GUI" and "as portable as possible" may very well be opposing each other.
Main questions are what do you have (technologies); what are you constraints, and what do you need. Different tech has different UI tech. Overall, most GUI programming is a hassle or mess.
If you want to dip your toes, use the tech you like, and look for simple GUI techs first. Don't try to do everything/all platforms at once first.