> From the name of the class I knew I was looking at Strada — the, yet unreleased, framework from Hotwired.

That's a slightly unusual statement to make in the middle of a reverse-engineering-ish piece like this. After reading it, I checked the author's bio and sure enough, it seems like he works on the Strada framework itself, or at least very closely with the authors.

In other words, he most likely didn't actually "stumble" on anything, and the preamble discussing how he started looking at the Hey app due to curiosity is probably just guff. This seems just to be a content marketing piece for Strada.

Now... that's okay, I like content marketing and often read it. However, when the content is fabricated in the way it appears to be here, I end up feeling a little cheated.

This _really_ feels like a marketing piece disguised as something else.

This kind of behaviour (bridging js and native) is very common in apps in Asia - especially China. A lot of apps use html to render a lot of pages in their app to keep almost everything dynamic, but they also need to be able to use things like FaceID and sharing buttons from the native side on those html pages. They use a bridge similar to this to achieve this.

This is common enough in China that the term "H5" is used to refer to in-app html rendered pages via a webview which behave similar to a native screen through the use of these bridges.

What is the novelty of Strada's approach being discovered here? I'm sure it's gonna be a great framework, but patching in JavaScript functions or message handlers so that your webkit frontend can call native functions is just the way webkit based mobile app frameworks work in general. Am I missing something more subtle?