Skip to content

Feature Management for Mobile #1042

Description

@MichaelLHerman

We are using Feature Management for both web and mobile.

It would be helpful if we could segment wether a feature is enabled based on user OS (Android vs iOS) and based on application version (to turn on a feature only after a specific version). We are already using groups to segment users by client organization, so we can't reuse groups as far as I know, unless a user could be in multiple groups ("ClientX", "Android", "1.0.2")? Also support for version ranges would be good, as there'd be no way to do that in the current UI

Activity

  1. zhiyuanliang-ms commented on Apr 10, 2025

    @zhiyuanliang-ms
    Member

    Hi, MichaelLHerman Thanks for reaching out.

    May I know the programing language of the Feature Management library you are using? Are you using targeting feature filter?

    It would be helpful if we could segment wether a feature is enabled based on user OS (Android vs iOS) and based on application version (to turn on a feature only after a specific version). We are already using groups to segment users by client organization, so we can't reuse groups as far as I know, unless a user could be in multiple groups ("ClientX", "Android", "1.0.2")

    Currently, you can use a custom feature filter to do this. A .NET example of custom feature filter which enables feature flag based on the browser type can be found here.

    Another workaround is that you can give all users a version tag(group) and exclude all the versions before the specific version in the targeting filter settings.

  2. MichaelLHerman commented on Apr 11, 2025

    @MichaelLHerman
    Author

    Zhiyuan Liang (@zhiyuanliang-ms)
    Using ASP.NET backend which uses Microsoft.FeatureManagement, passing along a list of enabled features to the user in an API call upon login.

    Thanks, will look into a custom feature filter that parses a custom User-Agent string that will include app version and platform

    Can you confirm that custom feature filters use an AND condition? If I have multiple custom feature filters on a feature flag, they must all evaluate to true for the feature to be on?

    Edit: I see that a "Require all above feature filters to be enabled" checkbox appears when I add more than one, seems like the default is OR and checked represents AND. I think this could be added to the feature filter documentation you shared.

  3. juniwang commented on Apr 13, 2025

    @juniwang
    Member

    Hi MichaelLHerman you are correct it is OR by default. Checking the checkbox enables AND evaluation. You can check this document for more information: https://learn.microsoft.com/en-us/azure/azure-app-configuration/feature-management-dotnet-reference#requirement-type

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions