4 ms·

Mostly I found Turbo Native is lacking a good minimal walkthrough from rails to shipping on android/ios. To me, looking at it from afar, it's entirely unclear t

Mostly I found Turbo Native is lacking a good minimal walkthrough from rails to shipping on android/ios. To me, looking at it from afar, it's entirely unclear the how much native dev is required to make it even walk.

rlawson 4y ago
Also I want it for Django
- joemasilotti 4y ago
  As long as your website is running Turbo 7, the JavaScript library, then you can interact with Turbo Native. You aren't limited to Ruby on Rails. https://github.com/hotwired/turbo https://github.com/hotwired/turbo
joemasilotti 4y ago
It's not official, but I have a series of blog posts on going from zero to App Store. [1] You are still required to write a fair amount of native boilerplate code to get an app working. The official Demo app [2] can get you pretty far but doesn't cover things like authentication. I've recently become an official maintainer of the Turbo Native libraries and hope to help clean up all of this over the next few months. [1] https://masilotti.com/turbo-ios/ https://masilotti.com/turbo-ios/ [2] https://github.com/hotwired/turbo-ios/tree/main/Demo https://github.com/hotwired/turbo-ios/tree/main/Demo
maxsilver 4y ago
Yeah, Turbo Native has a lot of Rails-style magic (which is great), but doesn't have a similar Rails-style level of good documentation yet (which is not so great -- discovery and troubleshooting is painful at the moment) I'm assuming once it's stable enough to leave beta, the community can polish up some proper documentation for it.
- joemasilotti 4y ago
  That's a great comparison. The code itself is powerful but it is still hard to use because it lacks documentation. That said, it is definitely stable enough to leave beta. Basecamp and HEY have been running it for years in production.
the_gastropod 4y ago
Agreed. There is a good amount of boilerplate needed to get a basic app setup. I hope it becomes a bit more "Railsy" with some Omakase-style conventions chosen. Right now, it's left up to you to implement multiple sessions, even though 95% of apps will want this. Auth feels like another area where there's a happy path that'd cover the 95% case, but it's currently left up to you to choose / implement using cookies vs tokens vs ???. That said, there is a decent amount of documentation around these things, and even as a relatively ignorant Swift programmer, I was able to copy/paste from the docs, and get an application working reasonably well.
- joemasilotti 4y ago
  That's awesome to hear you were able to get something working. And yes, 100% with you on this one. It's a very non-Rails like experience going to Turbo Native. You have to configure everything pretty much on your own and are left to figure it out by yourself for new things. One of my goals is to fix this in the near future!
  - heartbreak 4y ago
    Although in the case of authentication, Rails has dropped the ball for over a decade on providing an out-of-the-box solution. Practically everyone uses Devise.
    - joemasilotti 4y ago
      Even though the maintainers have pretty much said to use anything else! I'm guilty myself. I know how Devise works, including all of its quirks, so I refuse to learn something new. I don't think Rails will ever have a built-in authentication solution. But I would love to see more official support for something a bit "lighter" than Devise. And that works out of the box with Turbo.
    - airblade 4y ago
      I believe the maintainers regard authentication, rightly or wrongly, as a business-level feature. Not so much the mechanics of checking a user's credentials but how you want to steer the different authentication flows.
makk 4y ago
This book does that and more: https://railsandhotwirecodex.com/ https://railsandhotwirecodex.com/ (I have no affiliation.)
- joemasilotti 4y ago
  Ayush does a great job diving into both iOS and Android apps in this book. It's also a great resource for Hotwire in general. I learned a ton and agree with 95% of the Turbo Native content he wrote.

rlawson 4y ago

Also I want it for Django

joemasilotti 4y ago
As long as your website is running Turbo 7, the JavaScript library, then you can interact with Turbo Native. You aren't limited to Ruby on Rails. https://github.com/hotwired/turbo https://github.com/hotwired/turbo

joemasilotti 4y ago

It's not official, but I have a series of blog posts on going from zero to App Store. [1] You are still required to write a fair amount of native boilerplate code to get an app working. The official Demo app [2] can get you pretty far but doesn't cover things like authentication. I've recently become an official maintainer of the Turbo Native libraries and hope to help clean up all of this over the next few months. [1] https://masilotti.com/turbo-ios/ https://masilotti.com/turbo-ios/ [2] https://github.com/hotwired/turbo-ios/tree/main/Demo https://github.com/hotwired/turbo-ios/tree/main/Demo

maxsilver 4y ago

Yeah, Turbo Native has a lot of Rails-style magic (which is great), but doesn't have a similar Rails-style level of good documentation yet (which is not so great -- discovery and troubleshooting is painful at the moment) I'm assuming once it's stable enough to leave beta, the community can polish up some proper documentation for it.

joemasilotti 4y ago
That's a great comparison. The code itself is powerful but it is still hard to use because it lacks documentation. That said, it is definitely stable enough to leave beta. Basecamp and HEY have been running it for years in production.

the_gastropod 4y ago

Agreed. There is a good amount of boilerplate needed to get a basic app setup. I hope it becomes a bit more "Railsy" with some Omakase-style conventions chosen. Right now, it's left up to you to implement multiple sessions, even though 95% of apps will want this. Auth feels like another area where there's a happy path that'd cover the 95% case, but it's currently left up to you to choose / implement using cookies vs tokens vs ???. That said, there is a decent amount of documentation around these things, and even as a relatively ignorant Swift programmer, I was able to copy/paste from the docs, and get an application working reasonably well.

joemasilotti 4y ago
That's awesome to hear you were able to get something working. And yes, 100% with you on this one. It's a very non-Rails like experience going to Turbo Native. You have to configure everything pretty much on your own and are left to figure it out by yourself for new things. One of my goals is to fix this in the near future!
- heartbreak 4y ago
  Although in the case of authentication, Rails has dropped the ball for over a decade on providing an out-of-the-box solution. Practically everyone uses Devise.
  - joemasilotti 4y ago
    Even though the maintainers have pretty much said to use anything else! I'm guilty myself. I know how Devise works, including all of its quirks, so I refuse to learn something new. I don't think Rails will ever have a built-in authentication solution. But I would love to see more official support for something a bit "lighter" than Devise. And that works out of the box with Turbo.
  - airblade 4y ago
    I believe the maintainers regard authentication, rightly or wrongly, as a business-level feature. Not so much the mechanics of checking a user's credentials but how you want to steer the different authentication flows.

makk 4y ago

This book does that and more: https://railsandhotwirecodex.com/ https://railsandhotwirecodex.com/ (I have no affiliation.)

joemasilotti 4y ago
Ayush does a great job diving into both iOS and Android apps in this book. It's also a great resource for Hotwire in general. I learned a ton and agree with 95% of the Turbo Native content he wrote.