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.
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/ [2] https://github.com/hotwired/turbo-ios/tree/main/Demo
I'm assuming once it's stable enough to leave beta, the community can polish up some proper documentation for it.
That said, it is definitely stable enough to leave beta. Basecamp and HEY have been running it for years in production.
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.
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!
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.