When we first started The Gnar Company I expected to spend a significant amount of time researching and implementing new technologies each year. What we've generally found is while new frameworks and stacks are constantly evolving, clients typically seek expertise and stability within a given tech ecosystem. In our 6 years of operating The Gnar we haven't witnessed any major new frameworks/platforms get released and subsequently dominate the marketplace. If anything, we've seen more fragmentation, particularly in the NodeJS ecosystem.
This post is for developers and engineering leaders who pick a stack. Each 2022 prediction below is followed by what happened to that tool next. It also answers a mobile question: Hotwire Native vs React Native. Hotwire Native shows your web app's server-rendered screens inside native iOS and Android apps. React Native builds the app's screens from native components that you write in React.
Below is a quick summary of the technologies our shop will focus on using in 2022:
React#
React will continue to remain the dominant JS library for UI in 2022. While there are a lot of promising contenders in the space (Svelte, Vue, Preact) there is simply too much momentum behind React for many larger organizations and consultancies to pursue other JS UI libs. Our entire team is proficient in React and we have extensive expertise building very complicated applications in React and we've been pleased with the continuous improvement in tooling.
Which React releases bear on this post's 2022 lines?#
React shipped React 18 on March 29, 2022 and React 19 on December 5, 2024. A stable compiler, a new owner and React 19.3 followed. In its predictions for 2022, this post said "React will continue to remain the dominant JS library for UI in 2022." The table below dates each step in the React team's own words.
| Date | Release | The React team's words |
|---|---|---|
| March 29, 2022 | React 18 | "automatic batching, new APIs like startTransition, and streaming server-side rendering with support for Suspense" |
| December 5, 2024 | React 19 | "By convention, functions that use async transitions are called “Actions”." |
| October 7, 2025 | React Compiler 1.0 | "We are releasing the compiler’s first stable release today." |
| February 24, 2026 | React Foundation | React and React Native "are now owned by the React Foundation, an independent foundation hosted by the Linux Foundation" |
| September 9, 2026 | React 19.3 | View Transitions and Fragment Refs: "both of these are now stable in React 19.3" |
React's docs moved as well. On March 16, 2023, the React team launched react.dev and wrote, "The old reactjs.org domain will now redirect here." The React link at the top of this post's React section points to reactjs.org. It lands on react.dev today.
React Native#
React Native (RN) will continue to be our go-to tool for building mobile apps. Given our team's strong proficiency in React, it allows us to build on that knowledge and produce some great apps that are indistinguishable from native mobile apps. We also understand its limitations and will select RN only when it makes sense and recommend native when it doesn't. Overall, mobile tooling is fickle and it changes even within the native ecosystems (ex: objective C > Swift, Java > Kotlin). Given those changes, I still don't see a contender to supplant RN in 2022 but we are excited about some newer tech on the horizon like Strada.
What happened to React Native and Strada after 2022?#
React Native moved to its New Architecture, and Strada became part of a new framework called Hotwire Native. React Native 0.76 shipped "with the New Architecture by default" on October 23, 2024. 37signals announced Hotwire Native on September 25, 2024. In its predictions for 2022, this post said "React Native (RN) will continue to be our go-to tool for building mobile apps."
| Date | React Native post | Its words |
|---|---|---|
| June 25, 2024 | Framework guidance | "Using React Native frameworks, such as Expo, is now the recommended approach to create new apps." |
| October 23, 2024 | React Native 0.76 | "React Native 0.76 with the New Architecture by default is now available on npm!" |
| October 8, 2025 | React Native 0.82 | "the first React Native that runs entirely on the New Architecture" |
The same 2022 paragraph says "we are excited about some newer tech on the horizon like Strada." Here is what became of Strada, in its makers' words:
- September 19, 2023: the Strada site gives this date for its "Current version: 1.0.0-beta1".
- September 25, 2024: 37signals wrote, "Hotwire Native is the consolidation of the Turbo Native and Strada libraries into a single framework for iOS and Android."
- Today, the Hotwire Native docs say, "Bridge Components were formerly called Strada components and work exactly as they did before."
The Hotwire Native home page describes the approach in one line: "It wraps a web view within a native shell and renders HTML from your server." A Gnar engineering post from August 6, 2025, Hotwire Native: Zero to Mobile Hero, says "Hotwire Native + Rails is a great combination for teams that want to build apps once and have them serve web and mobile."
Hotwire Native vs React Native: which fits your mobile app?#
Pick Hotwire Native when you already run a Hotwire web app, such as a Ruby on Rails app, and most of your mobile screens can be web screens. Pick React Native when most screens need native UI components, or when your team writes React every day. Both frameworks build apps for iOS and Android. They differ in where the screen comes from. The Hotwire Native home page says it "wraps a web view within a native shell and renders HTML from your server." The React Native docs say "At runtime, React Native creates the corresponding Android and iOS views for those components."
In 2022 this post called React Native "our go-to tool for building mobile apps" and was "excited about some newer tech on the horizon like Strada." Strada is now part of Hotwire Native, so the table below compares Hotwire Native with React Native.
| Question | Hotwire Native | React Native |
|---|---|---|
| Who made it, and when? | 37signals announced it on September 25, 2024. | Facebook. A Facebook engineering manager wrote about it on the React Native blog on March 26, 2015. Meta owned React Native until February 24, 2026, when it moved to the React Foundation. |
| Where does a screen come from? | Your server's HTML and CSS. The docs say "Content is all web. Navigation is all native." | React components. The docs call the platform-backed ones "Native Components". |
| What does the team write? | Web pages from your server, such as a Rails app, plus Swift and Kotlin for any part that goes native. | JavaScript and React. The docs say "you use JavaScript to access your platform’s APIs". |
| What if a screen needs more? | Bridge components or fully native screens in Swift and Kotlin. | You can also write your own native components for Android and iOS. |
| Gnar's own work | Two engineering posts that build a Rails demo app for iOS and Android. | Mobile apps for Ollie, Conformis and SystemOne. |
How does a Hotwire Native app work on iOS and Android?
By default, each screen is a page from your web app, shown inside native navigation. The how it works page says "Hotwire Native intercepts link taps and passes control off to a native adapter." The adapter then "screenshots the current page before pushing (or presenting) new screens on the native stack with a default, platform-specific animation." The page adds that "the core of Hotwire Native is still a web browser." So the UI is server driven: the server renders the HTML, and the native app shows it in a browser view.
That is how one set of screens serves both apps. For those web screens, you do not build a separate mobile front end for each platform. The home page says the framework "enables you to build your screens once, in HTML and CSS, and reuse them across every platform." It sets that against fully native apps, where "Each feature must be re-implemented across every platform." The screen work stays web development: HTML and CSS served by your Ruby on Rails or other Hotwire web app. Gnar’s Zero to Mobile Hero post builds this setup around a Rails demo app, with the Android app in Android Studio and the iOS app in Xcode.
That changes how updates ship. A change to a web screen goes live in both apps when you deploy your web server. The how it works page says "Your Android and iOS clients see updates as soon as you deploy." The home page says bug fixes can ship "without having to go through app store review." A change to a native screen still goes through each app store. The home page says "you have full access to underlying iOS and Android SDKs and APIs as soon as they are released."
When is a Hotwire Native app the right call?
It is the right call when the web app already exists and the mobile app is mostly the same screens. The Hotwire Native docs say its core "is still a web browser which makes adding new screens as straightforward as building new pages in your web app." They add: "All without new submissions to the app stores." Gnar's engineering post Hotwire Native: Zero to Mobile Hero says "Hotwire Native + Rails is a great combination for teams that want to build apps once and have them serve web and mobile." Its follow-up, Hotwire Native: Building Bridges, adds native controls to the same demo app. It calls the bridge component "the star of the show for Hotwire Native."
The Zero to Mobile Hero post sorts screens into three levels:
- Web screen. "Your server-rendered page in the native shell", for when "You want to ship the screen as web first".
- Bridge component. "A Stimulus controller plus a Swift or Kotlin counterpart", for when "A page needs a native control".
- Native screen. "A screen written in Swift and Kotlin", for the highest fidelity.
Gnar's two posts show the native work that sits around the web screens. The Zero to Mobile Hero post says "Hotwire Native uses a path-configuration.json file to manage everything from settings to custom behavior for our individual pages." It uses a rule in that file to turn on pull to refresh for Android. It also notes that the Android path configuration guide "recommends always bundling a copy, so the app has its rules when offline." The Building Bridges post adds native buttons. It says the bridge component "uses data attributes on HTML elements and snippets of JavaScript to create native components that enhance the look and feel of your apps." The Zero to Mobile Hero post builds the Android app in Android Studio and the iOS app in Xcode. That post also writes app setup code on both platforms, including an Application class in Kotlin and a SceneDelegate and AppDelegate in Swift.
Count the native screens before you choose. The native screens page says they are for "Times where you need maximum fidelity or interaction with native SDKs and APIs." It warns that fully native screens "will likely take specialized experience from iOS and Android developers." It adds that "You’ll need to write a version for every platform and go through the app store review process for any future changes." An app made mostly of native screens gives up what Hotwire Native saves.
When is React Native the better fit?
React Native fits when the team works in React or the app needs native UI components on most screens. Three Gnar client apps used React Native, and one of them also had to keep working without a connection:
- Conformis. Gnar built a React Native app so surgeons could review surgical plans on a phone. The case study says "By using React Native, one engineer can maintain two platforms."
- SystemOne. Gnar built a lab results app in React Native for Android. The case study says "It works in offline mode and syncs new results when it reaches WiFi."
- Ollie. The case study says "The Gnar Company embedded React Native engineers with Ollie's back-end team to build its mobile app for iOS and Android."
Is React Native still maintained in 2026?
Yes. React Native is still actively released. As of November 17, 2026, its versions page lists 0.88 as the "Latest version." React and React Native moved to the React Foundation on February 24, 2026, as the React releases table above shows. Since June 2024 the React Native team has said that "Using React Native frameworks, such as Expo, is now the recommended approach to create new apps." In 2022 this post chose React Native because it "allows us to build on that knowledge" of React.
Why did Airbnb stop using React Native?#
Airbnb said it fell short of its goals for React Native, and it moved its mobile work back to native code. Its engineering post Sunsetting React Native, from June 19, 2018, says "we will be sunsetting React Native and putting all of our efforts into making native amazing." One reason was code sharing. It says "only a small percentage of our app was React Native," and that "large amounts of bridging infrastructure were required." As a result, "we wound up supporting code on three platforms instead of two."
Airbnb has since added a note to the top of that post. It says the article "reflects the state of React Native at the end of 2017." It also says "Any technical points should be revalidated."
This post’s 2022 prediction went the other way for React Native: "I still don't see a contender to supplant RN in 2022 but we are excited about some newer tech on the horizon like Strada." The Airbnb note is a reminder to date any such call, since both stacks have changed since then.
Rails#
Rails continues to surprise and impress me. There still isn't another platform that we've found that can deliver the amount of features Rails provides out of the box while being easy to develop in and stable from an operations/maintenance perspective. We have projects that are well past the 5 year mark and they are rock solid, requiring very little maintenance aside from the occasional gem updates. Client demand for skilled Ruby/Rails developers has actually increased for us over the last few quarters. The Rails community and ecosystem is still very active so it will remain a tool our team reaches for.
Stimulus#
Stimulus is another technology that has surprised me. When it initially came out, its usefulness wasn't immediately apparent to me as we were heavily entrenched in React. What we've discovered is how well it integrates with both existing and new Rails projects. We've been able to completely overhaul UI on older Rails applications without retooling and we've found ourselves just using vanilla Rails + Stimulus vs immediately gravitating towards React, especially for relatively simple UI's that don't require a lot of complex state management. We've recently been coupling Stimulus with Turbo and are often able to deliver single-page application (SPA) level interactivity significantly faster and with fewer moving parts.
Which Rails, Stimulus and Turbo releases bear on this post's 2022 lines?#
Rails shipped 8.0 on November 7, 2024 and 8.1 on October 22, 2025. Stimulus released 3.2.0 on November 28, 2022, and Turbo released 8.0.0 on February 7, 2024. In 2022, this post said "Stimulus is another technology that has surprised me." The Rails 7.0 post, from December 15, 2021, says of Hotwire, "It’s the default choice for new Rails apps."
| Date | Release | What its notes say |
|---|---|---|
| November 28, 2022 | Stimulus 3.2.0 | Its release notes list "Outlets API". Its reference page says "Outlets let you reference Stimulus controller instances and their controller element from within another Stimulus Controller by using CSS selectors." |
| February 7, 2024 | Turbo 8.0.0 | Its release notes list "Page refreshes with morphing". Its handbook says page refreshes feel better "if only the changed contents get updated". |
| November 7, 2024 | Rails 8.0 | "Rails 8 comes preconfigured with Kamal 2 for deploying your application anywhere." The same post says "Kamal takes a fresh Linux box and turns it into an application or accessory server with just a single “kamal setup” command." |
| October 22, 2025 | Rails 8.1 | The release post's title: "Rails 8.1: Job continuations, structured events, local CI" |
In 2022 this post had been "coupling Stimulus with Turbo." A Gnar engineering post, Ruby on Rails vs. React: Hotwire + Turbo Change the Equation, updated November 10, 2026, covers both libraries. Where "additional interactivity is needed," it says Stimulus "can often bridge that gap without the need to add React in Rails." That post also covers what Turbo 8 added.
Typescript#
You can take Typescript out of our cold, dead hands. It has become an integral piece of React/Javascript projects and is our default lingua in the JS ecosystem. We appreciate all the work happening in the language and get excited by all the new tools that are getting released.
NextJS#
My outlook on NextJS is more opaque than the other stacks we use. We've used it on a few projects and overall had a favorable opinion of it but have yet to find its sweet spot. For purely front-end we default to create-react-app but have had some success with Next. On full-stack/back-end it lacks all the out-of-the box utilities and conventions Rails provides resulting in a lot of external dependencies and bike-shedding on how to structure complex back-end apps. I also think Vercel (maintainer of NextJS) is missing the bus by not having a database option tightly integrated within their stack, which makes it a non-starter for us on most projects. We've found DigitalOcean or Heroku to deliver the best out-of-the-box experience when deploying full-stack NextJS apps that require server-side data persistence.
Which TypeScript and Next.js releases bear on this post's 2022 lines?#
TypeScript released 6.0 on March 23, 2026 and 7.0 on July 8, 2026. Next.js 13.4, released May 4, 2023, says "Starting today, we recommend building new applications with the App Router."
| Tool | This post's line for 2022 | What its release posts say |
|---|---|---|
| TypeScript | "You can take Typescript out of our cold, dead hands." | TypeScript 6.0, March 23, 2026: "TypeScript 6.0 is a unique release in that we intend for it to be the last release based on the current JavaScript codebase." TypeScript 7.0, July 8, 2026: "The mission was a native port of TypeScript built in Go" |
| Next.js | "My outlook on NextJS is more opaque than the other stacks we use." | Next.js 13.4, May 4, 2023: "Starting today, we recommend building new applications with the App Router." |
The 6.0 post says why: "we are working on a new codebase for the TypeScript compiler and language service written in Go." The 7.0 post then announced that port.
Webpack#
On a personal note, I hope 2022 is the year we no longer need to use Webpack. In the Rails ecosystem, I'm quite excited about jsbundling/import-maps and the complete removal of Webpacker as a dependency. On the JS side, I hope recent advancements in build tooling with TypeScript further reduce the need and complexity of transpiling and webpacker.
Do Rails and JavaScript apps still need Webpack?#
Rails 7.0 and Next.js 16 both moved new apps off Webpack as the default. Both still let a team choose it. The Webpacker README says its v5 edition "was included by default with previous versions of Rails." Next.js 16 made Turbopack its default bundler in October 2025. In its predictions for 2022, this post said "On a personal note, I hope 2022 is the year we no longer need to use Webpack."
- A Rails app on Webpacker. The Rails 7.0 post, from December 15, 2021, says Rails 7 delivers "a no-Node default approach to the front end." The post names esbuild, rollup.js and Webpack, each usable "through the new jsbundling-rails integration." The Webpacker README now opens with "Webpacker has been retired." Its first recommendation is "to switch to jsbundling-rails with Webpack (or another bundler)." It calls import maps "the default setup for new Rails 7 applications."
- A Next.js app. The Next.js 16 post, from October 21, 2025, says Turbopack "is now the default bundler for all new Next.js projects." It adds, "For apps with custom webpack setups, you can continue using webpack by running:"
next dev --webpackandnext build --webpack.
Webpacker's place in Rails history comes up in another Gnar engineering post. Hotwire Native: Zero to Mobile Hero, from August 6, 2025, says "They did eventually come around to a solution with Webpacker that sought to bring Rails into the new era, but it didn’t feel very “Railsy”."
How do you choose between Rails with Hotwire and React today?#
Weigh your team's experience first, then how interactive the app has to be. A team strong in React but new to Rails and Hotwire may be better off with React, and a team of expert Rails engineers would probably do best to lean toward Rails with Hotwire. That is the advice of Gnar's engineering post Ruby on Rails vs. React: Hotwire + Turbo Change the Equation, updated November 10, 2026, which lists "Choose with your team's experience in mind." among its takeaways. It also says "As it stands, the most interactive types of applications still require React or similar JavaScript frameworks." The post adds that "the combination of Turbo Frames and Turbo Streams are more than adequate for the vast majority of applications."
In its first section, the same post asks a question about your team: "Who are your current and future developers?" Two of its sentences answer it:
- "If your current developers have extensive experience with React, but little with Rails and Hotwire/Turbo, then you may be better off going with a React solution."
- "On the other hand, if you're already working with expert Ruby on Rails engineers, it would probably be best to lean toward Rails/Hotwire over React."
Gnar's own practice is stated on its custom software development page: "The Gnar Company builds with Rails, Hotwire and React. It picks the tools for each project."
Summary#
I don't anticipate any bold technology projections or big changes happening at The Gnar Company in 2022. We are attracted to tools that produce quality results for our clients while still allowing us to innovate. I'm excited for the incremental improvements and enhancements we'll see within the core tech we use and will pay close attention to emerging trends in open source tech stacks.
Learn more about how The Gnar builds software.


