The tool that you are most comfortable with is likely the best option. If you are vested in the MS ecosystem, I've found Blazor the fastest way to get simple UI results out through web assembly, but I happen to think Rust is better suited for actual production code. If you have Rust experience, this should be evident.

I've used both with great success, though there are various caveats with the MS suite of solutions - generally application size is the big one (downloading parts of the .NET framework make for slow load times on sluggish connections). However, the benefits of using Blazor (if you are already familiar with Razor) may outweigh the speed issues - which may simply also be audience dependent. If you are building internally, Blazor server apps are really easy to write quickly - and can be rapidly ported to Blazor webassembly apps - I've actually written a few apps that run under Blazor Server/ Blazor Web Assembly and on device with only very minimal configuration code differentiating the projects - ie, code re-use is pretty complete.

Speaking of on-device, Blazor also has the added benefit of writing "pseudo-native" apps (Blazor on Android/iOS, with access to native mobile features like GPS, etc, etc) . Perhaps outside of the scope of your project, based on the description, though!

I'd also say that Blazor Hot Reload makes brings web assembly into the leagues of other first class development tools that allow changes on the fly - node/react, etc, etc...

Note that I don't write much in Python, but included it as an option, since it's possible, and my primary recommendation is to use the tool that you know the best. You could also look to C/C++, Go, and various other languages that support rust - see here for more: https://www.fermyon.com/wasm-languages/webassembly-language-support

Brendon Paul

Tools Used

Most Used

By Layer

Application & Data

Utilities

DevOps

Business Tools