Goodbye pod install

Introduction For years, React Native developers working on iOS have relied on one command more than any other: cd ios && pod install This command has been a staple for managing native dependencies in iOS projects. But in 2025, React Native is moving away from it—and for good reasons. If you’ve recently seen a warning like: "Calling pod install directly is deprecated in React Native" ...you’re witnessing a significant shift in how React Native handles iOS builds. Why Is pod install Being Deprecated? React Native is undergoing a significant transformation, and part of that involves reducing reliance on iOS-specific tools like CocoaPods. Here’s why: 1. Less iOS-Specific Tooling CocoaPods is great for iOS, but React Native aims for true cross-platform development. The new architecture favors tools that work seamlessly across iOS, Android, and beyond. 2. Modern Build Systems (TurboModules & Fabric) The New Architecture (TurboModules, Fabric, JSI) requires a more streamlined build process. Manually running pod install adds unnecessary friction. 3. Fewer Setup Headaches CocoaPods has been a common source of issues (version conflicts, slow installations). Moving away from manual pod install reduces these pain points. What Should You Use Instead? The replacement depends on your setup: For Expo Users Expo already abstracts away native build complexities. Just run: npx expo run:ios This handles everything—no pod install needed. For React Native CLI Users Instead of manually running pod install, use: yarn ios # or npx react-native run-ios These commands automatically handle dependency installation when needed. When Might You Still Need pod install? Debugging Xcode/CocoaPods issues Working with custom or experimental native modules Maintaining legacy projects that haven't migrated to the new architecture The Bigger Picture: React Native in 2025 This change is part of a broader evolution in React Native: 1. TurboModules & Fabric Are the Future TurboModules improve native module performance. Fabric makes rendering more efficient. Both reduce the need for platform-specific setups. 2. Expo Is Becoming the Default Expo simplifies native builds, making CocoaPods invisible for most developers. Even bare React Native projects are adopting similar abstractions. 3. Cross-Platform Tooling Is the Standard React Native is pushing for less iOS/Android fragmentation. Future tools will likely replace CocoaPods with Swift Package Manager (SPM) or a universal solution. Conclusion What Should You Do Today? Expo users: Stick with npx expo run:ios—no changes needed. React Native CLI users: Use yarn ios or npx react-native run-ios instead of pod install. Advanced cases: Only use pod install when absolutely necessary. The Future Is Simpler React Native is moving toward a more unified, less platform-dependent workflow. While CocoaPods isn’t disappearing overnight, its role is shrinking—and that’s a good thing. Fewer Podfile conflicts, faster builds, and a smoother development experience await.

May 11, 2025 - 11:55

Introduction

For years, React Native developers working on iOS have relied on one command more than any other:

cd ios && pod install

This command has been a staple for managing native dependencies in iOS projects. But in 2025, React Native is moving away from it—and for good reasons.

If you’ve recently seen a warning like:

"Calling pod install directly is deprecated in React Native"

...you’re witnessing a significant shift in how React Native handles iOS builds.

Why Is pod install Being Deprecated?

React Native is undergoing a significant transformation, and part of that involves reducing reliance on iOS-specific tools like CocoaPods. Here’s why:

1. Less iOS-Specific Tooling

CocoaPods is great for iOS, but React Native aims for true cross-platform development.
The new architecture favors tools that work seamlessly across iOS, Android, and beyond.

2. Modern Build Systems (TurboModules & Fabric)

The New Architecture (TurboModules, Fabric, JSI) requires a more streamlined build process.
Manually running pod install adds unnecessary friction.

3. Fewer Setup Headaches

CocoaPods has been a common source of issues (version conflicts, slow installations).
Moving away from manual pod install reduces these pain points.

What Should You Use Instead?

The replacement depends on your setup:

For Expo Users

Expo already abstracts away native build complexities. Just run:

npx expo run:ios

This handles everything—no pod install needed.

For React Native CLI Users

Instead of manually running pod install, use:

yarn ios
# or
npx react-native run-ios

These commands automatically handle dependency installation when needed.

When Might You Still Need `pod install`?

Debugging Xcode/CocoaPods issues
Working with custom or experimental native modules
Maintaining legacy projects that haven't migrated to the new architecture

The Bigger Picture: React Native in 2025

This change is part of a broader evolution in React Native:

1. TurboModules & Fabric Are the Future

TurboModules improve native module performance.
Fabric makes rendering more efficient.
Both reduce the need for platform-specific setups.

2. Expo Is Becoming the Default

Expo simplifies native builds, making CocoaPods invisible for most developers.
Even bare React Native projects are adopting similar abstractions.

3. Cross-Platform Tooling Is the Standard

React Native is pushing for less iOS/Android fragmentation.
Future tools will likely replace CocoaPods with Swift Package Manager (SPM) or a universal solution.

Conclusion

What Should You Do Today?

Expo users: Stick with npx expo run:ios—no changes needed.
React Native CLI users: Use yarn ios or npx react-native run-ios instead of pod install.
Advanced cases: Only use pod install when absolutely necessary.

The Future Is Simpler

React Native is moving toward a more unified, less platform-dependent workflow. While CocoaPods isn’t disappearing overnight, its role is shrinking—and that’s a good thing.

Fewer Podfile conflicts, faster builds, and a smoother development experience await.