Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

elixir-desktop vs live view native #54

Open
zoedsoupe opened this issue Dec 22, 2024 · 2 comments
Open

elixir-desktop vs live view native #54

zoedsoupe opened this issue Dec 22, 2024 · 2 comments
Labels
question Further information is requested

Comments

@zoedsoupe
Copy link

how does this project differs from live view native?

i know live view native doesn't support desktop yet but i think maybe we can kinda put the effort on the same path?

@zoedsoupe
Copy link
Author

awesome project though!

@dominicletz
Copy link
Collaborator

dominicletz commented Dec 27, 2024

Hey @zoedsoupe thanks for your question!

This is a misunderstanding that is coming up quite commonly. Let me try to clarify and please raise any additional questions you have on this:

Elixir Desktop goal is to build Local-First applications using Elixir and specifically LiveView. A typical example of a local-first applications is a note taking that works offline.

  • "Thick client" Local-First app
  • Ships BEAM compiled for iOS and Android
  • Runs beam locally (no server)

Elixir Native goal is to use LiveView strength to build native look and feel apps for iOS + Android

  • "Thin client" uses http connection to a server
  • Ships translation layer that converts liveview generated xml to native swift ui or android ui components
  • Requires a central server

So these projects are actually very different, and in fact you could use them both together theoretically. E.g. if you want to create a local-first application with a native look and feel you can use Elixir Desktop to bundle and ship an app that runs locally with no internet connection and use Elixir Native to render locally the native UI. This would be an amazing combination and I would be happily accepting any PRs making this easier.

Cheers!

@dominicletz dominicletz added the question Further information is requested label Dec 27, 2024
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants