masilotti.com VS hyperview

If your like this approach to building hybrid native mobile apps, I highly recommend following Joe Masilotti at https://masilotti.com/

I only read three emails newsletters, and Joe’s is one of them because it’s roughly once per month and it keeps me current on all the things happening with Hotwire and Turbo Native apps.

And you're not wrong - there are very few resources available on Turbo Native development. My blog, workshop, and YouTube videos are practically the only things out there. And William Kennedy is sharing his process learning Android, which is helping fill that gap.

add contact links as well (LinkedIn, Github) (ex. https://masilotti.com/ )

update your website - make the site clean and direct about who you are, what you do, what you're looking for, and where you are (ex. https://masilotti.com/ )

be specific in your title & intro - "Junior Python/React Fullstack Dev" and "Locacted in Tulsa, Ok" mean more than "I thrive on challenges". What's the most important info about what you do and who you are? Make that first and prominent. (ex. https://masilotti.com/ )

add your photo in place of sonar. This site is selling your services and it gives more trust to have your face on your website. ex. https://masilotti.com/ ) You can move a block of text with skills below your "Hi, I'm Patrick" text.

Turbo Native in its current form requires a fair amount of iOS knowledge (and code!) to get working. I'm trying to fill that gap with my blog, workshops, and live streaming sessions. [1]

But it's no excuse for what this library could be if we invest more time into it. In an ideal world the library handles 90% of the boilerplate required to make an iOS app work. I'm talking authentication, pushing/presenting controllers, sensible defaults for Path Configuration, etc. All the stuff that I have to add to every single Turbo Native app I work with. (12+ since I last counted.)

Then devs can focus on differentiation and exciting features like push notifications, native integrations, fancy animations... while the core of the logic remains on the Rails app.

I'm hoping that getting more maintainers (like me!) on the repo will help kickstart this. And I'm excited to see more interest on both HN and Twitter in the framework.

[1] https://masilotti.com

I blog about Turbo Native and run the monthly ⚡️ Hotwire dev newsletter!

Is english your first language? I feel like many of your objections, insofar as I can make sense of them, fall into language & semantic debates.

The term HDA, which I coined and, therefore, feel like I have some ability to define, was created to contrast with the familiar SPA/Single Page Application acronym, which is a term used in web development. This is why I focus on the web with that article.

As I have repeated incessantly with you, I included HXML, a mobile hypermedia from the https://hyperview.org project, in my book on hypermedia systems, and I hope this indicates to a fair minded 3rd person (I have given up on you acknowledging my plain language here) that I do not believe that HTML is the only hypermedia in the world.

I've really enjoyed using Hyperview (https://hyperview.org/) recently, which uses React Native as a base. I used to think PWA/Ionic/Capacitor apps were better, but have really fallen in love with the simplicity of Hyperview and tools like HTMX.

there already is!

https://hyperview.org/

Adam Stepinski, the creator of Hypreview, built it after his experience with intercooler.js, the predecessor to htmx. It is a very interesting piece of technology and, through the magic of HATEOAS, allows you to update your mobile app instantly for all your users, without dealing with the mobile store!

There is an entire section on Hyperview, written by Adam, in part three of our book:

https://hypermedia.systems/book/contents/

it's about hypermedia, https://htmx.org/, and https://hyperview.org/ , which have a focus on removing complexity

[1] There is Hyperview but it's super new.

i am the creator of htmx, this is a great article that touches on a lot of the advantages of the hypermedia approach (two big ones: simplicity & it eliminates the two-codebase problem, which puts pressure on teams to adopt js on the backend even if it isn't the best server side option)

hypermedia isn't ideal for everything[1], but it is an interesting & useful technology and libraries like htmx make it much more relevant for modern development

we have a free book on practical hypermedia (a review of concepts, old web 1.0 style apps, modernized htmx-based apps, and mobile hypermedia based on hyperview[2]) available here:

https://hypermedia.systems

[1] - https://htmx.org/essays/when-to-use-hypermedia/

[2] - https://hyperview.org/