Web support (not a priority yet)

[stackotter]

This is the tracking issue for web support in SwiftCrossUI. I currently don't really have any plans but figured it'd be good to have a place to dump ideas. I'll come back and edit this later, but here are my main thoughts;

• SwiftCrossUI's core pretty much compiled to WASM with no issues last time I checked
• We could either do WASM or an elixir-style separate backend/frontend approach with websockets used to stream data back and forth
• What design language would we follow by default? Would we choose a popular web component library and use that? Or would we try to follow a specific backend's design language? Or would we make our own? (I'm leaning towards choosing a popular web component library)
  • Maybe it'd be a good idea to make the underlying set of components easy to swap out so that people can integrate their own preferred design systems into SwiftCrossUI on the web?