If this is like react native except where most of the logic is server-side (but sends down some kind of native DOM that gets rendered natively), I'm sold.<p>This seems to be a more detailed link: <a href="https://dockyard.com/blog/2022/09/01/dockyard-r-d-build-elixir-web-native-apps-seamlessly-with-liveview-native" rel="nofollow">https://dockyard.com/blog/2022/09/01/dockyard-r-d-build-elix...</a>
I’m having a super hard time understanding why you’d want a <i>native</i> app require 100% connectivity.<p>When the app feels like (or is) a web app, then at least the user understands intuitively that nothing is going to survive connection loss. However with a native feel, seeing the app freeze and navigation become disabled is going to feel completely wrong..<p>Did i miss something ??
Have led multiple teams on Elixir projects across a few companies. And while I still love the projects, the community just isn't there anymore.<p>I hope this project sparks some renewed interest in Elixir!<p>(That said, the linked site has basically zero information or examples)
One thing that isn’t clear - does the elixir runtime (OTP) run on the iOS device?<p>It looks like a well integrated web view, but it’s not clear if it’s all running on device. Does apple support a web page not loaded from local?
Tangential, but where can I watch the talks from ElixirConf 2022? Youtube channel has not uploaded any yet, and the website doesn't seem to have any recordings either. All I see is 250$ to attend virtually.<p>Shouldn't their target be to spread word fast and wide? I get paid tickets for in-person attendance, but online talks should ideally be live streamed for free, no?
Is this the same?:
<a href="https://github.com/elixir-desktop/desktop" rel="nofollow">https://github.com/elixir-desktop/desktop</a>
Looks quite similar to me.
Is this what DHH and Rails did with Hotwire Turbo and their native iOS/Android libraries to allow you to use identical server rendered HTML content that you use for your web site in native mobile apps without needing to write native apps beyond a shell or whatever native controls you want to opt-into using?<p>They've been doing this with Turbolinks for years (I think it was first mentioned in a 2016 Railsconf keynote), seems like a good pattern. I'm so happy DHH came up with this pattern, especially the idea of leaning heavily on HTTP (not Websockets) and sending HTML over the wire for fast page updates.