Callstack

How do you build a full-stack testing strategy for a production React Native TV app? Michał Pierzchała connects all the dots in this article ➡️ https://clstk.com/4n9zZMj He walks through the entire process, from the ground up: ➡️ Unit & integration tests: Creating custom helpers to simulate remote control navigation in React Native Testing Library. ➡️ E2E tests: Configuring Appium and WebdriverIO to run automated tests across native (tvOS, Android TV) and web-based platforms. ➡️ Real-device validation: Integrating your test suite with device farms like AWS and BrowserStack to ensure true production readiness. This article provides the code, configurations, and strategy you need to ship high-quality TV applications with confidence. And there are even more tips coming in the 2026 edition of the TV Guide we’re writing with Amazon Developer, so sign up for the waiting list on the article’s page now 👀

With teams looking to scale React Native in real-world apps, brownfield setups are becoming the default. At Zalando, that means embedding React Native into a large production codebase while combining it with their internal Rendering Engine and aiming for cross-platform reuse across app and web. On November 5 at 5PM CET, we’re hosting a live session with their team. They’ll share how they approached: ➡️ Running React Native as a package ➡️ Structuring for interop with native ➡️ Solving DX challenges across platforms ➡️ What’s working and what still needs work You'll hear from: René Eichhorn & Ghasem Bakhtiari from Zalando and Mike Grabowski, Maciej Jastrzebski and Jakub Stadniczuk from Callstack. Sign up below to join the session and ask questions live ⬇️

As AI provider APIs for multimodality and tool-calling diverged, a simple incremental update wasn't enough. In the talk from our AI Meetup, 🧑🏻💻 Lars Grammel (Vercel) explains the why behind the major rewrite of AI SDK 5. He explores the three core pillars: the new provider spec, the fully type-safe UI layer, and the new controls for agentic loops. If you've ever wondered how to manage multi-step tool calls or get end-to-end type safety between your model's output and your UI, this one is for you ➡️ https://lnkd.in/dKgQgBHC

As Meta continues to invest in Meta Horizon OS, many React Native teams are asking about the developer experience. How easy is it to really get started? What are the practical steps and hidden "gotchas"? 👹 Jan Jaworski 🐸 wrote a getting-started guide to answer exactly that. It details how to use Expo to build for Meta Quest, focusing on leveraging your team's existing mobile stack. We walk through the two essential workflows: ➡️ Expo Go: For rapid setup, live-reloading, and quick UI iteration. ➡️ Development Build: For full native access, ADB debugging, and production-ready apps. This confirms that the Expo and React Native ecosystem provides a clear, accessible path for building immersive experiences. It makes your team's current expertise its biggest asset for entering the VR space. Get the full guide on our blog ⬇️

When mobile apps scale quickly, performance often falls behind. For one of our fintech clients, fragmented analytics made it difficult to detect incidents, track regressions, or trust test results. We helped unify their observability and improve delivery confidence by: ➡️ Consolidating three analytics systems into one. ➡️ Adding custom performance instrumentation for startup and interaction timing. ➡️ Migrating to a faster, more reliable test and CI setup. Now their team can spot issues earlier, release with confidence, and see performance trends evolve across every release. Full case study in the comments ⬇️

Moving a React app to TV introduces a host of engineering challenges, from managing focus with a D-pad to re-thinking interactions for the 10-foot UI. In this talk, Amazon Developer's Eric Fahsl showcases Kiro.dev, an AI assistant built to solve these problems predictably. He covers its spec-driven process and "Steering Documents" that enforce project architecture, turning a complex TV adaptation into a series of actionable, AI-generated tasks. Check out the full talk ➡️ https://clstk.com/3LicyTA

For companies already building with React Native, expanding to television is less than a leap, and more of a step sideways, as they can reuse 60-80% of their existing codebase, from business logic to UI components. Łukasz Chludziński’s article explores how your team can leverage its existing knowledge of Metro, TypeScript, and React DevTools to conquer the fragmented TV market ⬇️ https://clstk.com/46RIOWc This piece is the first exclusive excerpt from the upcoming TV Guide 2026 co-authored with Amazon Developer.

Running LLMs on-device offers privacy and offline access, but integrating models into a mobile app can be a challenge. In this talk from our AI Meetup, Szymon Rybczak breaks down React Native AI, our approach to simplifying on-device inference. He covers how to build custom providers for the AI SDK to support the MLC LLM Engine and Apple's foundation models. Watch Szymon's full presentation here ➡️ https://clstk.com/4ol0385

React Native Harness helps developers test native modules in a real React Native environment. Built for library authors and teams working close to native code, it simplifies testing while ensuring real execution across platforms. Congrats Szymon Chmal on the release! 🔥

🎧 Understanding the anatomy of audio APIs in React Native In our latest blog post, we take a closer look at how audio APIs work under the hood, from raw PCM buffers to the structure of WAV headers, and how to handle them efficiently using JSI and in-memory data flow. If you've ever wondered what happens between "generate sound" and "play sound", this one is for you!