Live data from Hacker News

Strada – Create fully native controls, driven by your web app

strada.hotwired.dev

31–34 of 34 posts

Re: Strada – Create fully native controls, driven by your web app

#31

After waiting for what feels like forever, I’m excited to finally explore the last missing piece of Hotwire. Strada is an optional add-on for Turbo Native apps that enables native components driven by the web. It unlocks progressive enhancement of individual controls without converting entire screens to native. For example, converting a to a UIBarButtonItem on iOS or rendering a HTML modal with ModalBottomSheetLayout…

I'm not sure I fully understand how it works. The intention is to start out with a WebView app, but slowly replacing the components that might need it with native components, right? This isn't a React Native Web like approach where you try to cover the same surface area, but rather an individual implementation of each screen, so you could tweak and modify it for the given platform if needed? Is it possible to embed n…

Turbo Native's goal is to reuse all your existing mobile web screens in your native apps. Strada helps progressively enhance them by slapping on a native component here and there.

You get baseline HTML coverage for free – Strada makes it easier to make things a bit more native.

Re: Strada – Create fully native controls, driven by your web app

#32

Earlier quoted context omitted.

Oh hey, that's me! Thanks for the shout out, Brad. I'm writing up my thoughts on the Strada launch right now. It will hit my newsletter, blog, and RSS feed tomorrow morning. tl;dr - Strada alone doesn’t unlock new features for Turbo Native apps. Everything you can do with the framework you could already do before. Albeit with much, much more code. Strada provides structure and organization to the tangled mess that is…

subscribed because I saw your comment about newsletter tomorrow. Looking forward to it

Thank you!

Re: Strada – Create fully native controls, driven by your web app

#33
What bothers me a bit, while it's still open source with permissive license, the direction is dictated by 37signals. Which is known for its questionable decisions. Related both to software and community side of things.

I am quite hesitant to use 37signals tools for now. Partially because they pretty much didn't ask anyone dropping TypeScript. But also because in general open source software owned by one single company sometimes goes to the direction community of engineers don't want them to go.

For example, Tensorflow dropped Windows support. While it's Apache License 2.0, and alternatives, there are dependencies.

Do I want to introduce dependency that I will regret in the future? With 37signals the answer is most likely yes. The same for Unity, for example. Or Unreal engine -- even though they didn't do anything wrong... yet.

37signals do not value their reputation too much as well. After mass exodus I expected them too be a bit nicer. But TypeScript situation just tells me it's ongoing issue, there is element of surprise.

I will be happy to know I am wrong, since the tool itself looks like I want to use it.

Post reply on HN