Feature flags
Feature flags are a powerful tool in modern software development. They let teams separate deployment from release, making rollouts smoother, experimentation safer, and iterations faster.
The story behind Atono feature flags
In many systems, feature flags exist in a separate application, requiring teams to cross-reference them with the functionality they control. With Atono, feature flags are embedded directly into user stories, cutting out this extra step.
Key benefits
- Streamlined workflow: By integrating feature flags into user stories, we reduce cognitive overload, simplify project management, and centralize all relevant information. This makes it easier for teams to track progress and control feature rollouts.
- User-friendly implementation: Implementing feature flags in Atono is intuitive. Each story comes with built-in documentation and code snippets, so even if you’re new to feature flagging, you can set them up with ease.
- Comprehensive tracking: Atono’s reporting system provides a clear view of all stories under flag control, allowing product owners to monitor ongoing releases and identify opportunities to retire flags for fully-released features.
How it works
For MVP, we’ve prioritized keeping feature flags simple yet effective. You can set flags ON or OFF for any story and slice them by common dimensions like environment, customer, and location.
A foundation built on standards
Atono feature flags are based on openfeature.dev, the emerging standard for feature flagging. This means you can easily switch to a different feature flag provider in the future if needed.
What’s next?
We believe our current approach covers 80% of customer use cases without adding unnecessary complexity. As we gather user feedback, we plan to expand these capabilities to meet specific customer needs.