Expo UI Atlas
Expo UI Atlas support
Expo UI Atlas is an independent interactive reference for Expo UI, maintained by Andrew Bierman through Bierman Collective LLC. It is not affiliated with or endorsed by Expo or Apple.
Get help or report a problem
Email [email protected]. You do not need an app account or a GitHub account to contact support.
- Include the app version and build number, if available.
- Tell us your device model and operating system version.
- Name the collection and example, and describe the steps to reproduce the problem.
- Describe what you expected and what happened. Screenshots can help; remove personal information first.
Do not send passwords or sensitive sample inputs. See the Expo UI Atlas privacy policy for how support messages and app experiments are handled.
Common questions
Do I need Expo Go or a development server?
No. The standalone App Store or TestFlight build runs independently. Expo Go is used when developing from source.
Which collections can I explore?
The catalog shows shared controls and direct native components supported on your device. Search, filters and Guide follow the same availability.
Why does an effect look different on my device?
Native controls follow the operating system. Some effects and variants require newer OS versions. The app leaves native defaults in place unless you explicitly customize them.
Are experiments saved?
Playground settings and sample inputs stay locally in memory. Reset restores the example’s starting state; restarting the app can discard changes.
Does the app work offline?
The catalog, examples, selected inline reference text, privacy policy, support information and notices work offline. Full official references, external links and remotely referenced media need connectivity.
Can I suggest an example or contribute?
Email the support address with your suggestion. Please discuss substantial API or architecture changes before implementing them.