This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
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.
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.
No comment highlights available yet. Please check back later!
About Gates on Product Hunt
“Feature flags and staged rollouts for Expo apps”
Gates was submitted on Product Hunt and earned 0 upvotes and 1 comments, placing #209 on the daily leaderboard. 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.
Gates was featured in Developer Tools (522.6k followers), Tech (636.2k followers) and SDK (871 followers) on Product Hunt. Together, these topics include over 265.3k products, making this a competitive space to launch in.
Who hunted Gates?
Gates was hunted by Bruno Kiafuka. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Gates stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Bruno Kiafuka
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?