It would all depend if you allow running Javascript besides that HTML or not, and if so, how well sandboxed that Javascript engine is (and will be)
A signer like Amber is not web based
Discussion
And ideas on what could work well for max sandboxing a javascript engine in Flutter apps?
The webview_flutter package should be good in terms of security but it's not as performant as native. Would warrant some testing and tweaking
nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s how would you go about nostr UI widgets for embedding across a variety of clients? The universal answer seems to be HTML/JS but it comes with challenges in native apps
Perhaps we could come up with a custom nostr HTML templating based on mustache or similar, no JS
Mustache = https://mustache.github.io/mustache.5.html ?
I'm more and more attracted to that last option. #nostache 🥸
I like the simplicity of something like mustache and it seems relatively easy to built various types of Nostr functionality on top of it. Both in terms of:
1. Fetching Nostr events/media to fill the mustaches with
2. Defining types of "links" that, when clicked, signal specific events to be opened/signed by the native app