How does it work?

Three simple steps to visualize it:

1. Manage your Featurevisor project in a Git repository
2. Build and upload datafiles (static JSON files) to your CDN or custom server
3. Fetch the datafile in your application, and evaluate features using SDKs

What do I need to bring to use Featurevisor?

• A Git repository for managing your project declaratively
• A CI/CD pipeline (like GitHub Actions) for building and uploading datafiles
• A CDN or custom server for serving the generated datafiles

Featurevisor SDKs will take care of the rest for you.

Understanding the building blocks

Three core building blocks of a Featurevisor project are:

• Attributes: building block for conditions
• Segments: reusable conditions for targeting users
• Features: features with flag, variation, and variable definitions

SDKs are used in your application(s) to evaluate three different types of values belonging to your defined features against your provided context in the runtime:

• Flags: on/off values against rules
• Variations: string values for A/B tests
• Variables: key/value pairs for remote configuration

Where can I use Featurevisor?

Supported SDKs include:

• JavaScript (both Node.js and browser environments)
• React
• React Native
• Go
• Python
• PHP
• Ruby
• Java
• Swift
• Next.js
• Vue.js

Why should I use Featurevisor?

Several use cases include:

• Decoupling application deployments from feature releases
• Progressive delivery with gradual rollout of features
• Testing in production
• Experiment with A/B and Multivariate tests
• Role-based feature gating
• Remote configuration with advanced variables
• Establishing feature ownership and governance
• Trunk based development
• Aligning multiple teams in a microfrontends architecture
• Feature depdendencies management
• Deprecating features safely

License

MIT © Fahad Heylaal