If you rewrite it in Swift or Kotlin then morphdom is not needed, because data will be handled outside the webview, or am I misunderstanding something?
Exadra37
derek-zhou
I am not familiar with mobile development enough to know; I just intuitively assumed that there is a need to manipulate whatever data structure that backs the webview. What does turbo-ios do?
0
yukster
FWIW, there are some folks working on a library to bring LiveView to JSON objects: GitHub - Miserlou/live_json: LiveJSON - LiveView for JSON · GitHub. Theoretically this would allow your native app to benefit from the dynamic data updates pushed by the server.
4
Exadra37
mmmrrr
turbo-ios is very much imperative and not reactive at all. So you simply have an API/bridge where you communicate between the web and the native part and other than that you basically have two separate applications.
So my initial idea was to do something similar: simply render hidden components that have a native counterpart and then parse the needed info out of the dom to update the native components. But in order to do that I’d need to hook into the live view lifecycle to know when an update is done. (Thinking about it, this could also be done via LiveJSON, as @yukster suggested)
I also think it is extremely important for such a companion framework to be as simple as possible.
Thanks for all the input 
2