EAS Build (Expo) in React Native - Build, Publish & Deploy

Build & Publish - EAS Build (Expo)

Performance Impact of EAS Build (Expo)

EAS Build helps create optimized app binaries for iOS and Android. It produces native builds that run smoothly at 60fps or higher, matching native app performance. Using EAS Build avoids the overhead of development servers, improving app startup speed and reducing memory use compared to running in Expo Go during development.

Because EAS Build compiles your app with native code, it can better manage battery use and system resources, leading to a more efficient app experience.

💻

How to Optimize EAS Build for 60fps Rendering

To keep your app smooth at 60fps, use EAS Build with these tips:

• Enable Hermes engine for faster JavaScript execution on Android.
• Use production mode builds by setting releaseChannel or channel properly.
• Minimize heavy JavaScript work on the main thread.
• Use EAS Build's managed or bare workflow to include only needed native modules.
• Test builds on real devices to catch performance issues early.

Impact on App Bundle Size and Startup Time

EAS Build creates standalone app binaries, which are larger than development builds but optimized for release. Typical bundle sizes range from 10MB to 50MB depending on included assets and native modules.

Startup time improves because the app runs natively without the Expo Go wrapper. You can reduce bundle size by:

• Removing unused dependencies.
• Using asset compression.
• Enabling code splitting and lazy loading where possible.

iOS vs Android Differences with EAS Build

On iOS, EAS Build produces an IPA file signed with your Apple Developer credentials. The build process requires a Mac or cloud service and proper provisioning profiles.

On Android, EAS Build creates an APK or AAB file signed with your keystore. It supports automatic signing or manual keystore upload.

Build times may differ: iOS builds often take longer due to Apple's infrastructure and code signing.

Both platforms benefit from EAS Build's cloud infrastructure, but you must configure platform-specific settings like permissions and icons separately.

Relevant Store Review Guidelines and Requirements

• Apple App Store: Ensure your app complies with Apple's Human Interface Guidelines, including privacy policies and user data handling.
• Use correct provisioning profiles and certificates for code signing.
• Include proper app icons and launch screens as required by Apple.
• Test for crashes and performance issues before submission.
• Google Play Store: Follow Google Play's policies on content, permissions, and user data.
• Sign your app with a valid keystore; EAS Build can manage this automatically.
• Optimize your app bundle size to meet Google Play limits.

Self-Check: Your App Takes 5 Seconds to Load This Screen. What's Likely Wrong?

Possible issues include:

• Large unoptimized assets or images delaying startup.
• Heavy JavaScript code running on the main thread blocking UI rendering.
• Incorrect EAS Build configuration causing debug builds instead of release builds.
• Missing Hermes engine on Android causing slower JS execution.
• Too many native modules increasing app initialization time.

Check your build profile, optimize assets, enable Hermes, and test production builds to fix slow startup.

Key Result

EAS Build creates optimized native app binaries for iOS and Android, improving performance and startup time. Proper configuration and asset optimization ensure smooth 60fps UI and smaller bundle sizes. Platform-specific signing and store guidelines must be followed for successful publishing.

Practice

1. What is the main purpose of eas build in Expo?

easy

A. To publish the app directly to app stores

B. To run the app on a local simulator

C. To build app files for Android and iOS in the cloud

D. To create a new Expo project

Solution

1. Step 1: Understand the role of eas build

   The eas build command is used to create app binaries for Android and iOS using cloud services.

2. Step 2: Differentiate from other commands

   It does not run the app locally, publish directly, or create projects; it only builds app files.

3. Final Answer:

   To build app files for Android and iOS in the cloud -> Option C

4. Quick Check:

   EAS Build = cloud app file creation [OK]

Hint: Remember: eas build creates app files remotely [OK]

Common Mistakes:

• Confusing build with running the app locally
• Thinking it publishes directly to stores
• Assuming it creates new projects

2. Which of the following is the correct syntax to start a build for Android using EAS?

easy

A. eas build --device android

B. eas build android --platform

C. eas build -p ios

D. eas build --platform android

Solution

1. Step 1: Identify the correct command format

   The correct syntax uses eas build --platform android to specify the platform.

2. Step 2: Check other options for errors

   eas build --device android uses invalid flag, eas build android --platform has wrong syntax order, eas build -p ios targets iOS.

3. Final Answer:

   eas build --platform android -> Option D

4. Quick Check:

   Correct flag for platform is --platform [OK]

Hint: Use --platform flag followed by platform name [OK]

Common Mistakes:

• Mixing up flag order
• Using wrong flags like --device
• Confusing platform names

3. What will happen if you run eas build --platform ios --profile production?

medium

A. It builds an iOS app using the production profile in the cloud

B. It builds an Android app using the production profile

C. It runs the app on an iOS simulator locally

D. It creates a new production profile

Solution

1. Step 1: Analyze the command flags

   The command specifies --platform ios and --profile production, meaning it builds for iOS using the production profile.

2. Step 2: Understand the build behavior

   EAS Build runs in the cloud and does not run simulators or create profiles with this command.

3. Final Answer:

   It builds an iOS app using the production profile in the cloud -> Option A

4. Quick Check:

   Platform + profile flags define build target [OK]

Hint: Platform and profile flags control build target and config [OK]

Common Mistakes:

• Assuming it runs locally
• Confusing platform with Android
• Thinking it creates profiles

4. You run eas build --platform android --profile staging but get an error saying the profile is missing. What is the likely cause?

medium

A. You used the wrong platform flag

B. The staging profile is not defined in eas.json

C. You need to run expo start first

D. Your internet connection is off

Solution

1. Step 1: Understand profile usage in EAS Build

   Profiles like staging must be defined in the eas.json file to be used.

2. Step 2: Check other options for relevance

   Platform flag is correct, expo start is unrelated, and internet issues cause different errors.

3. Final Answer:

   The staging profile is not defined in eas.json -> Option B

4. Quick Check:

   Missing profile in config causes build error [OK]

Hint: Check eas.json for profile definitions before building [OK]

Common Mistakes:

• Ignoring eas.json profiles
• Confusing build with running app
• Assuming network error

5. You want to share your app with testers before publishing. Which EAS Build feature helps you do this easily?

hard

A. Using eas build to create app files and share build URLs

B. Running expo publish to update the app instantly

C. Using expo start to open the app on testers' devices

D. Creating a new Expo project with expo init

Solution

1. Step 1: Identify how EAS Build supports sharing

   EAS Build creates app binaries and provides URLs to share with testers easily.

2. Step 2: Differentiate from other Expo commands

   expo publish updates JS bundles but not native builds; expo start is for development; expo init creates projects.

3. Final Answer:

   Using eas build to create app files and share build URLs -> Option A

4. Quick Check:

   EAS Build creates shareable app files [OK]

Hint: Build app files and share URLs with testers using EAS Build [OK]

Common Mistakes:

• Confusing publishing with building
• Thinking expo start shares apps
• Assuming new project creation helps sharing