React Native has been rebuilding, and with its latest release, Reactive Native 0.82, it will run entirely on its new architecture.
“This is a milestone release for React Native and we believe it’s the start of a new era,” the team wrote in the release announcement.
The React Native new architecture was introduced a year ago. It uses JavaScript Interface (JSI), which replaces the asynchronous bridge between JavaScript and native.
“JSI is an interface that allows JavaScript to hold a reference to a C++ object and vice versa,” the team stated. “With a memory reference, you can directly invoke methods without serialization costs.”
For example, it enables the camera library VisionCamera to process frames in real time.
“Typical frame buffers are [about] 30 MB, which amounts to roughly 2 GB of data per second, depending on the frame rate. In comparison with the serialization costs of the bridge, JSI handles that amount of interfacing data with ease,” the team wrote. “JSI can expose other complex instance-based types such as databases, images, audio samples, etc.”
That’s because JSI removes that class of serialization work from all native-JavaScript interop, the team explained, including initializing and re-rendering native core components like View and Text.
The release announcement described how to migrate to new architecture. It’s worth noting that React Native is not currently removing APIs of the legacy architecture, to ensure backward compatibility. However, the removal will start with the next version, the team stated, because doing so will significantly reduce the overall bundle size.
This release also introduces Hermes V1 as experimental. It features improvements in the compiler and in the virtual machine that boosts Hermes performance, the team announced. React Native has been using it internally with apps and believes it’s ready for the community to test out.
“From initial tests and benchmarks, Hermes V1 outperforms current Hermes in various scenarios,” the team wrote. “We have seen improvements in bundle loading and TTI (Time to Interactive).”
But the team cautioned that the improvements “strongly depend on the details of your apps.”
The release blog post explains more about the upgrades, as well as details about how to migrate to the new release and architecture.
API Devs: Kong Konnect AI Assistant Helps Govern, Debug APIs
API developers who use Kong Konnect now have a new agentic API platform co-pilot that’s designed to automate governance and assist with debugging.
Kong, an API and AI gateway company, released the assistant — called KAi — at its annual API Summit 2025 held in New York this month. It works within Kong Konnect, which is the company’s cloud native, unified API platform.
For more news from Kong’s API Summit, including a new open source offering for AI Agents, check out TNS’ recent coverage.
“KAi is an in-Konnect agent that takes care of all the needs that you think about when you think about the developer, infrastructure and platform owner concerns,” Reza Shafii, senior vice president of product, told the conference’s audience. “KAi is constantly looking at all of your configurations and detecting potential issues that could lead to downtimes and suggesting how to improve that.”
KAi embeds AI directly into Konnect to:
- Automate governance by proactively scanning for policy violations and suggesting automated remediations for compliance.
- Support advanced debugging and issue resolution by analyzing traffic patterns, identifying issues and recommending how to remediate the problem.
- Offering best practices suggestions in real time.
Eventually, KAi will be able to open the right pull request for developers with the right fix, as well as to initiate observability debugging sessions, according to Shafii. It will also be able to look across an organization’s API collection and detect potential API duplication by having a similarity index.
It’s available this week for Plus and enterprise users, but organizations must work with Kong to accept the terms and conditions before it will be enabled.
A New Open Source Option for Web, Edge Applications
Harper, a Node.js performance platform, is open sourcing its core technology: a composable full-stack web application platform. The company made the announcement Tuesday during the opening keynote at JSConf North America.
This is Harper’s core technology, according to the company, and it will be available under the Apache 2.0 license. Harper focuses on edge uses, providing ultra-low latency for applications, the press release stated.
“The highly extensible, distributed system fuses database, cache, messaging and Node.js runtime into a single server-side process — delivering unmatched performance for data-intensive, latency- sensitive applications,” the company said in a statement.
Harper noted that the platform already has “strong enterprise traction,” claiming it powers nearly 2% of global e-commerce purchases and other high-traffic web properties.
“Harper customers have reported dramatic performance gains – including server response times under one millisecond in scenarios where traditional stacks took over 100 milliseconds, and web pages loading up to 7x faster with Largest Contentful Paint metrics up to 30x faster than previous architectures,” the company stated.
The technology uses a cloud and edge-native unified architecture that Harper says collapses multiple layers of the web stack into one process. The platform keeps data at the edge, which cuts out network hops and serialization between separate database, cache and application tiers.
“By releasing our source, we’re putting Harper in the hands of skilled web architects and developers around the world, inviting them to help shape the future of high-speed, edge-native applications,” said Stephen Goldberg, CEO and co-founder of Harper, in the announcement.
One goal the company hopes to see is new use cases in edge computing and distributed web applications.
Harper will still offer enterprise-grade support and managed services for organizations that require production assistance.
The post React Native Rolls Out Its Latest Version on New Architecture appeared first on The New Stack.