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).
Product upvotes vs the next 3
Product comments vs the next 3
Product upvote speed vs the next 3
Product upvotes and comments
Product vs the next 3
Gates
Feature flags and staged rollouts for Expo apps
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.
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.
On the analytics side, Gates competes within Developer Tools, Tech and SDK — topics that collectively have 1.2M followers on Product Hunt. The dashboard above tracks how Gates performed against the three products that launched closest to it on the same day.
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.
For a complete overview of Gates including community comment highlights and product details, visit the product overview.
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?