desktop VS turbo-ios

Exciting work is happening in all of these areas...

> desktop

Elixir Desktop: https://github.com/elixir-desktop/desktop

> mobile development

LiveView Native: https://www.youtube.com/watch?v=dnDGh_Jmw-s

> front end web

LiveView?

> command line tools

Mix.Install: https://thinkingelixir.com/elixir-1-12-and-your-first-mix-in...

How about numerical computing / machine learning: https://github.com/elixir-nx/nx/tree/main/nx

Embedded: "yes there's Nerves". Exactly?

I think you may be looking for this neat library: https://github.com/elixir-desktop/desktop

Although to be honest it boggles my that it's possible to accomplish this on iOS.

One option might be to use something like this - https://github.com/elixir-desktop/desktop - and create an executable that can be downloaded and would work offline (the Phoenix server would run inside the application itself, but would not require an internet connection).

We are trying to see what elixir deskop has to offer in terms of mobile application.. we heard that with elixir desktop you can build mobile apps for both android and ios.. so basically iam just trying to gain some information on how it works.. what are the possibilities or limitations.. otherwise Primarily I build mobile apps using native kotlin or flutter sometimes..

But if your goal is to develop a purely client side app with elixir, I'm afraid that the only option may be to wait for [elixir-desktop](https://github.com/elixir-desktop/desktop) to mature.

There is this new project https://github.com/elixir-desktop/desktop

If you're a SwiftUI developer, I've had an issue open at https://github.com/hotwired/turbo-ios/issues/8 to get Turbo SwiftUI off the ground.

I've talked to a few folks about it and have heard responses ranging from "it's a bad idea/can't be done" (mainly because of SwiftUI bugs) to "why would you want to do that?". I think it would be amazing to have a declarative of building out a Hotwire Rails application inside of iOS. Bonus if the Turbo SwiftUI component could run on macOS.

For the mobile side, start with each platform's respective Turbo package: https://github.com/hotwired/turbo-ios and https://github.com/hotwired/turbo-android. Each has a demo app you can run in XCode/Android studio. To get a basic app building, follow each one's "Getting Started" guide. It's actually pretty easy to get a basic native app building, the hard part comes in integrating native components and services, as well as release management.

turbo-ios and turbo-android are the shell/wrapper apps handling native navigation, written for native iOS and Android. They are provided for you, and works out-of-the-box, but you risk having to fiddle with iOS and Android development for maintenance/debugging later on.

Ruby on Rails, Hotwire, Postgres, Redis

Does anyone have experience with https://github.com/hotwired/turbo-ios or https://github.com/hotwired/turbo-android ?

1. Turbo Native

I use Turbo Native on iOS to do exactly this.

You render your mobile web view like normal, wire up a JavaScript handler (formerly known as Turbolinks), and push native screens on iOS. It works really well for CRUD and "boring" SAAS apps with little interaction outside of forms. And when you need higher fidelity dropping down to SwiftUI or UIKit is straightforward.

https://github.com/hotwired/turbo-ios

To make things even simpler, I built Jumpstart iOS, which takes care of all of the Swift boilerplate. Navigation, authentication, and push notifications all work out of the box after adding a few endpoints to your server.

https://jumpstartrails.com/ios

Adding to the already mentioned solutions, another alternative may be to develop your app with Phoenix and [Hotwire](https://hotwired.dev/), using Turbo on the backend and [Turbo-ios](https://github.com/hotwired/turbo-ios) for your app.

turbo-ios and turbo-android are small wrappers around your web views. You write native Swift and Kotlin wrappers but the frameworks display your web content. They also handle navigation and data transmission between the views and native code.

I’d like to see this integrate more tightly with Rails Turbo framework. Ideally it would understand Visitables and plug into SwiftUI. I took a swing at that at https://github.com/hotwired/turbo-ios/issues/8 but have struggled to get it working … that and Strada hasn’t come out yet, which I assume is the equiv of the native plugins within Portals.