From 2ec26dca75743f019ca32bac9e4230241d84dad3 Mon Sep 17 00:00:00 2001 From: Dan Zeitman Date: Wed, 15 Dec 2021 08:11:40 -0800 Subject: [PATCH] Update 0004-cocoapods-support-improvements.md --- proposals/0004-cocoapods-support-improvements.md | 1 + 1 file changed, 1 insertion(+) diff --git a/proposals/0004-cocoapods-support-improvements.md b/proposals/0004-cocoapods-support-improvements.md index ec52894d..3e04df7a 100644 --- a/proposals/0004-cocoapods-support-improvements.md +++ b/proposals/0004-cocoapods-support-improvements.md @@ -98,6 +98,7 @@ Why should we _not_ do this? Please consider: ## Alternatives - CocoaPods support could be handled by [shipping binaries](https://github.com/react-native-community/discussions-and-proposals/issues/15) of React Native to clients. Personally, I prefer to be working with the source code for ease of forkability and debugging. +- CocoaPods adds unnecessary overhead adoption friction for new developers wanting to simply try out React Native. Swift Package Manager bypasses this friction. Suggest making React Native available as a Swift Package. ## Adoption strategy