infinitered / infinitered/ignite
Allow for Different App Bundles (Development / Preview / Production) via ExpoConfig `app.config.ts`
- Dominant language
- TypeScript
- Stars
- 19.9k
- Forks
- 1.5k
- PR merge metrics
- No merged PRs in 30d
Description
I've always found it a little bit annoying to have to uninstall a development build on my phone when I am trying out a production build.
This Twitter Post is kind of neat, would be cool if it was a feature in Ignite:
https://x.com/appfr3d/status/1846618899389014287?s=46

Contributor guide
Research direction
Start by reviewing how Ignite uses ExpoConfig through app.config.ts and how development builds currently receive their bundle identifiers. The issue does not name implementation files or tests, so first map the existing configuration and build entry points. Done should mean development, preview, and production app bundles can be installed side by side without uninstalling one another.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native, typescript
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100