Result comparison with EAS Build #5
Replies: 4 comments
-
Nice!! DM-ed 😀 |
Beta Was this translation helpful? Give feedback.
-
Just released 2.0.1 (Build 13) on TestFlight 👉 https://testflight.apple.com/join/PHcLooxC Universal binary download size reduced by 19X and install size reduced by 13X, compared to last production 2.0.0 build. Comparison tables below for 2.0.0 (Build 9, Expo 40), 2.0.1 (Build 11, Expo 41) and 2.0.1 (Build 13, Expo 41, EAS). 2.0.0 (Build 9) Production
2.0.1 (Build 11) Staging
2.0.1 (Build 13) Staging
|
Beta Was this translation helpful? Give feedback.
-
2.0.2 (Build 24) Production
|
Beta Was this translation helpful? Give feedback.
-
Hi there!
I saw your post on Reddit and the concern about app size. I thought I'd use this as an example to try out the new EAS Build preview and the early support it has for managed workflow.
The app worked with EAS Build without any changes required (beyond creating
eas.json
when runningeas build
), and the install size was reduced to ~6.7mb on my iPhone 11 Pro, down from 52.6mb reported from the App Store for the expo build version of the app.Here's a screenshot of the build info in App Store Connect, and a video of the result (mostly indistinguishable from the source, I just renamed the app and you'll notice in the settings there is no Expo SDK version present in the build).
RPReplay_Final1608663895.mp4
Basically what EAS Build does for managed projects is "eject" the project, configure everything based on your app config and installed packages, then set up the credentials and run a build with
fastlane gym
.This took about 11 minutes (after brief queuing):
If you want free early access to this so you can try it out and give feedback, just DM me on Twitter @notbrent and let me know what your Expo username is and I can add you :)
(we'll have a free tier that should be more than enough for hobby/open source apps like this when we launch General Availability)
Beta Was this translation helpful? Give feedback.
All reactions