One builds an app by adding a selection of “Actions,” which are calls-to-action for either content or functions. Audience control lets one select the audience that will see an individual Action.
The Audience control icon for an Action will be highlighted green if selections have been made.
With the setting above the designated Action would be visible only to Android users who have installed the app. The value is that premium content can be used to incentivize users to install an app.
App owners can use the "Audience control" feature to create different user experiences for different categories of users.
For another common use case, if one adds an Action such as an “In-App” message promoting the user to install the app, one does not want that message to display to the users who have already installed the app. By setting the “Audience” to “Browser”, the in-app message will display to users viewing the app through their browser but not users who have installed the app.
Similarly, one can have an action that is visible only to desktop users. For example, if the goal is to get a user to download a native app, then a mobile user should see an Action with a link to the right app store, while a desktop user should see an Action with a visible QR code they can scan with their mobile device to get the app..
Another use case for audience control in a progressive web app is to deliver device-specific instructions on how to install the PWA when it is browsed but to hide these instructions after the user installs the app and the directions are no longer relevant.
"Both” is the default audience for each audience category.
When building or updating an app, the dashboard preview has a selectable filter that enables one to toggle between different audience views. For example the below filter will show what content a mobile user will see if they are browsing the app. Desktop users or users that add the app to their home screen can see different content, but one can easily preview their experience by adjusting the filter.