Paul Wright

1. Is there any value in a generic instruction?

One thing I can think of is to ask users do not change the configurations if they are created via MDC bindings, and perhaps link them to some of the known issues if they choose to do so. Also perhaps it will be good if we explain how they can fix the issue (like unbind and then bind again).

2. What are the missing user stories we need to document around using the push admin ui? (eg when would a dev want multiple variants for a particular platform?)

There are a few of them I think.

For IDM, if user changes the realmId or clientId via the Keycloak admin console, these changes will not be reflected in mobile-services.json file, which means the app will not work properly.
For UPS, if user renew an existing variant secret, or create a new variant through the UPS admin console, these changes will not be reflected in mobile-services.json file. However, I believe Gerard Ryan is going to fix the first one so that if an existing secret is renewed, it will be synced. However, the second scenario won't be fixed. MDC already supports binding multiple variants (one for each platform) to a single app.

I don't think there are anything required for MSS as user can't do a lot via the MSS UI.