State of React Native 2025: Build and publish
Skip to content

Build and publish

How do you build and submit your app for the App Store, Google Play or other stores?

Build and publish ratios over time

Bitrise
EAS Build
EAS Submit
Fastlane
GitHub Actions
Manually with Android Studio
Manually with Xcode
EAS Workflows

Mode:

View:

0%
20%
40%
60%
80%
100%
2022
2023
2024
2025
0%
20%
40%
60%
80%
100%

Build and publish experience & sentiment

Group by:

Sort by:

68.2%
27.6%
3.9%
929
61.9%
35.4%
916
60.3%
32.8%
6.6%
897
55.9%
34.8%
8.7%
893
54%
38.4%
7.3%
921
47.1%
35.6%
16.5%
907
25.3%
59.9%
14.9%
899
18.7%
30.1%
50.9%
911
Experience
  • Used it: Respondents who have used an item.
  • Heard of it: Respondents who have heard about an item, but haven't used it.
  • Never heard of it: Respondents who have never heard about an item.
Sentiment
  • Positive: Respondents who are interested in learning more about a technology; or are willing to use it again.
  • Neutral: Responents who did not indicate any sentiment about a technology.
  • Negative: Respondents who are not interested in learning more about a technology; or have used it and had a negative experience.

As React Native continues to mature, so does the community's approach to building and publishing apps. EAS Build continues to lead the pack at 68% usage, cementing its position as the go-to build solution for React Native developers. Alongside it, EAS Submit holds steady at 54%, showing that Expo Application Services (EAS) has become the default pipeline for a majority of the community.

The biggest newcomer is GitHub Actions, kicking off at 62% and immediately claiming the second spot. CI/CD is no longer a nice-to-have but an important part of how React Native apps get launched. Developers aren't just building, they're automating the annoying parts of app development. On that same note, EAS Workflows is the fastest-growing tool in this section, nearly tripling from 9% to 25% usage. With almost 60% of respondents having heard of it but not yet tried it, a massive wave of adoption still lies ahead.

Where Fastlane once dominated build automation, the community has clearly moved toward more integrated, end-to-end solutions. The pain points confirm this direction; GitHub Actions addresses the top concerns around CI/CD workflows and configuration complexity. But the requirements get more complex with environment management, code signing, store submission, and build failures still being significant hurdles. This is where the EAS shines, tackling nearly every pain point on the list under one umbrella.

Developers want seamless automation from code to store, and React Native now has more options than ever, from fully managed solutions like EAS to do-it-yourself pipelines with GitHub Actions. Looking ahead to 2026, AI could take this even further. Imagine build failures being automatically analyzed and fixed, turning one of the most frustrating parts of mobile development into a solved problem.

Cedric van Putten
Software developer at Expo
We asked members of the React Native community to share their opinions about the results

Other solutions

Other ways to build app and publish to the stores
Freeform
What other solutions not mentioned above have you used for your React Native apps?
0%
14%
29%
43%
58%
72%
1

Local/Manual building and publishing

2

Codemagic

3

Other Answers

Answers matching “Other Answers” 26
0%
14%
29%
43%
58%
72%
% of question respondents

Building and publishing pain points

Building and publishing pain points
Freeform
What pain points have you encountered with deployment in your React Native projects? If applicable, point out the specific solution and its problems.
0%
8%
15%
23%
31%
38%
1

CI/CD & Workflows

2

Configuration

3

Environment management

4

Stores

5

Build time

6

Failures

7

Signing

8

Submitting

9

Error handling

10

Other Answers

Answers matching “Other Answers” 20
0%
8%
15%
23%
31%
38%
% of question respondents