Launching today
Gates
Feature flags and staged rollouts for Expo apps
1 follower
Feature flags and staged rollouts for Expo apps
1 follower
Control feature access after you deploy. Gates bring stable percentage rollouts, app-version and Expo rutime targeting, and on-device flag evaluation to Exp apps. Cached decisions keep working offline.
Free Options
Launch Team
Atlassian LoomHit record, hand off to AI
Promoted
Hi Product Hunt — I'm working on Gates, feature management for Expo apps.
Deploying a bundle and enabling a feature are separate decisions. Gates focuses on the second: choose a cohort, target the app versions or Expo runtimes that should get access, then expand the rollout when you're ready.
The gallery walks through a checkout feature: 10% to 25%, cached flag reads while offline, and a kill switch that takes effect on the device's next successful sync.
The implementation is deliberately straightforward: configuration sync happens separately from local flag evaluation. Before a usable snapshot loads, the configured fallback applies. Offline devices keep their last configuration.
EAS Update already handles update rollouts; Gates controls individual features in code that has shipped. Gates is independent of Expo and doesn't compute statistical experiment results.
Docs: https://usegates.app/docs/
I'd love to hear from Expo developers: which part of managing feature releases creates the most manual work for your team?