Research: Explore building and hosting native binary using Expo EAS build

[Cal-L]

What is this about?

This task tracks researching and experimenting with a PoC of using Expo EAS build. The purpose of this is to provide an alternative for contributors to download and test apps without having to build the native binary locally. Ultimately, this is intended to reduce friction and improve contributor experience

Scenario

No response

Design

No response

Technical Details

• Install Expo SDK as basic dependency
• Research the feasibility of Expo EAS build
• Provide documentation of findings and how-to-run
• Setup Expo EAS account

Threat Modeling Framework

No response

Acceptance Criteria

• Documentation on research that has been done around Expo EAS Build. (Ex. Findings, README, etc)
• PoC of a working example using Expo EAS build (Ex. Testable branch)

Stakeholder review needed before the work gets merged

• [ ] Engineering (needed in most cases)
• [ ] Design
• [ ] Product
• [ ] QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
• [ ] Security
• [ ] Legal
• [ ] Marketing
• [ ] Management (please specify)
• [ ] Other (please specify)

References

• Expo ADR - https://github.com/MetaMask/decisions/pull/35

[cortisiko]

Note: We should consider running a single detox e2e test against the EAS build.