---
title: "Building v0 iOS and Fixing React Native Along the Way"
description: "A technical look at building v0 mobile with React Native and Expo, covering iOS-first decisions, native modules, and fixes pushed to React Native core. Featuring Fernando Rojo, Szymon Rybczak, and Oskar Kwaśniewski."
url: https://www.callstack.com/podcasts/building-v0-ios-and-fixing-react-native-along-the-way
updated: 2026-10-24T08:39:42.019Z
---

# Building v0 iOS and Fixing React Native Along the Way

A technical look at building v0 mobile with React Native and Expo, covering iOS-first decisions, native modules, and fixes pushed to React Native core. Featuring Fernando Rojo, Szymon Rybczak, and Oskar Kwaśniewski.

_Guests: Fernando Rojo, Head of Mobile @ Vercel; Szymon Rybczak, Software Developer @ Callstack; Oskar Kwaśniewski, Software Developer @ Callstack · Host: Aleksandra Desmurs-Linczewska, Software Engineer @ Callstack · Published 2026-01-12 · Duration 51:04 · Category: AI_

Listen: [YouTube](https://youtu.be/rhLBFKlEXPM) · [Spotify](https://open.spotify.com/episode/5OihWVEBlmuPdKTKs3kW4O?si=sflcDwi1T1--kL1zLSQlyg) · [Apple Podcasts](https://podcasts.apple.com/us/podcast/building-v0-ios-and-fixing-react-native-along-the/id1525543072?i=1000745129601) · [SoundCloud](https://soundcloud.com/user-985069846/building-v0-ios-and-fixing-react-native-along-the-way-with-fernando-rojo-szymon-rybczak-oskar-kwasniewski)

Vercel's v0 iOS app is built with React Native, yet delivers the look and feel of a native iOS product. In this episode, the team behind it walks through the technical decisions, trade-offs, and low-level fixes required to ship a polished, production-ready app under real deadlines.

## Episode summary

Ola Desmurs-Linczewska is joined by Fernando Rojo, Head of Mobile at Vercel, and Callstack engineers Oskar Kwaśniewski and Szymon Rybczak. Together, they break down how v0 mobile was built using React Native and Expo, why the team went iOS-first, and how deep dives into Yoga, gesture handling, and WebView internals shaped the final product.

## Iterating to greatness

At Vercel, [shipping early and iterating constantly](#yt-time=00:04:14) is a core principle. For v0 iOS, this meant prioritizing release momentum while avoiding blocking issues that didn’t affect core experience. The team focused on shipping a solid foundation, then refining UI, interactions, and performance through frequent iterations rather than waiting for perfection.

### Expo as the foundation

Expo was the [default choice](#yt-time=00:06:37) for starting the project, providing fast iteration, EAS builds, and Expo Modules for custom native integrations. As the app matured, the team leaned heavily on Expo’s extensibility, writing native modules when needed and patching libraries directly to keep development moving.

### Going iOS-first

The team [deliberately focused on iOS](#yt-time=00:16:58), targeting the latest system versions early. This allowed them to fully embrace platform-specific APIs such as scroll view insets and advanced keyboard handling without compromising for cross-platform parity. [Android is planned](#yt-time=00:15:41), but only after the iOS experience feels complete.

### Fixing React Native at the source

While building v0 iOS, the team frequently uncovered opportunities for improvement within the React Native core, such as modal flickering caused by asynchronous Yoga layout updates. Rather than working around them, they [patched React Native directly and upstreamed fixes](#yt-time=00:25:24), some of which landed in later React Native releases.

### Open source as a byproduct

Several components built specifically for v0 were open-sourced, including [liquid glass UI effects](https://github.com/callstack/liquid-glass) and a rewritten [pager view](https://github.com/callstack/react-native-pager-view/) implemented in SwiftUI. Other work, such as improved keyboard handling and gesture coordination, is planned for release once it is decoupled from v0-specific logic.

What made this possible was the team’s habit of pushing complexity downward: whenever a solution felt too low-level, fragile, or app-specific to live comfortably in product code, it became a candidate for extraction. The result was a steady stream of libraries, forks, and upstream contributions shaped by real production constraints, rather than abstract examples, turning v0 iOS into a proving ground for tools the wider React Native community can now build on.

## Resources

- Ola Desmurs-Linczewska on [X](https://x.com/p_syche_) and [Bluesky](https://bsky.app/profile/psyche.social)
- Fernando Rojo on [X](https://x.com/fernandorojo) and [GitHub](https://github.com/nandorojo)
- Szymon Rybczak on [X](https://x.com/SzymonRybczak) and [GitHub](https://github.com/szymonrybczak)
- Oskar Kwaśniewski on [X](https://x.com/o_kwasniewski) and [GitHub](https://github.com/okwasniewski)
- [Vercel’s v0 app](https://v0.app/)
- [v0 iOS app](https://v0.app/ios)
- [How we built the v0 iOS app article](https://vercel.com/blog/how-we-built-the-v0-ios-app) by Fernando Rojo

Insights

## Learn more about AI

Here's everything we published recently on this topic.

[View all](https://www.callstack.com/insights)

- [Efficient On-Device LLMs in React Native Done Right](https://www.callstack.com/events/efficient-on-device-llms-in-react-native-done-right) (Nov 17 · Talk): Artur Morys-Magiera will cover efficient on-device LLMs in React Native, including runtimes, model selection, quantization, and platform constraints.
- [On-Device AI After WWDC: What Changed for React Native](https://www.callstack.com/events/on-device-ai-after-wwdc-what-changed-for-react-native) (Nov 17 · Talk): Mike Grabowski will explain what changed for system-provided on-device AI after WWDC and what React Native developers can build with it.
- [Beyond Coding Agents: Making ADLC Work Across Platforms](https://www.callstack.com/events/beyond-coding-agents-making-adlc-work-across-platforms) (Nov 16 · Talk): Mike Grabowski will explain how to close the full agentic development lifecycle across mobile, web, and native platforms.
- [Building the React Native Software Factory](https://www.callstack.com/events/building-the-react-native-software-factory) (Nov 11 · Talk): Join us at React Foundation Meetup London on November 11 to explore how AI agents build and debug React Native apps, from one terminal to the cloud.
- [Building a Software Factory: Write Specs an Agent Can Build From](https://www.callstack.com/blog/building-a-software-factory-write-specs-an-agent-can-build-from) (Nov 6 · Article): Learn how to research requirements, resolve open decisions, and write testable specs that AI coding agents can implement without the planning conversation.
- [ Large-Scale Migrations With Coding Agents: Planning, Verification, and Rollback](https://www.callstack.com/blog/large-scale-migrations-with-coding-agents-planning-verification-and-rollback) (Nov 4 · Article): Plan codebase migrations with coding agents using reviewable requirements, verification checks, staged rollouts, and defined rollback criteria.
- [Quantization Impact on LLM Quality: A Case Study of Apex](https://www.callstack.com/events/quantization-impact-on-llm-quality-a-case-study-of-apex-a-gemma-based-model) (Nov 4 · Talk): Artur Morys-Magiera and Lech Kalinowski share findings from 344 benchmark runs with Apex, our Gemma-based LLM, examining the trade-offs between model size, decode speed, and quality.
- [Conversational Banking: From Customer Questions to Authorized Actions](https://www.callstack.com/blog/conversational-banking-from-customer-questions-to-authorized-actions) (Nov 2 · Article): Explore conversational banking architecture through a card-dispute example, covering tool access, authorization, execution, observability, and human handoff.
- [Building a Software Factory: The Night My Agents Waited for Me](https://www.callstack.com/blog/building-a-software-factory-the-night-my-agents-waited-for-me) (Oct 28 · Article): Learn how permissions, review limits, and missing product decisions stalled two overnight coding agent runs, and how their maintainer revised the workflow.