For the desktop presentation in the mocks, we currently present the following "mobile" options when MFEnableMobilePreferences is active:

This setting is currently disabled on prod.

Edit: also, preferences are only available to logged in users.

Note: we're not planning to support the logged out case as part of this task.

Edit: so these are the configuration modes we need to add:

• Logged in client Minerva
• Logged in server Minerva
• Logged in server Desktop

These are the old modes we need to maintain and test:

• Logged out client Minerva
• Logged out server Minerva

Edit: the matrix of supported configurations for AMC functionality in general is therefore:

• Logged in enabled client Minerva
• Logged in enabled server Minerva

And the supported configurations to maintain the old configuration for is:

• Logged in disabled client Minerva
• Logged in disabled server Minerva
• Logged out client Minerva
• Logged out server Minerva

The worst case would be six different presentations for a given feature. However, some features, for example, talk tabs, only present differently on AMC state, not login state specifically. That is, logged in disabled client Minerva and logged out client Minerva are identical as are logged in disabled server Minerva and logged out disabled server Minerva. This means only four different presentations would be required. If only client support is needed, this drops the number of presentations down to two.

@alexhollender I see you revised the mock to:

So let's talk about this here...
I see two separate tasks here in this mock:

1. informational overlay
2. feedback links

Let's create tasks for both of those (cc @ovasileva )
Also are we sure we want feedback links given the problems we had before (see T187712 )

In T210653#4867739, @Jdlrobson wrote:

@alexhollender I see you revised the mock to:

@alexhollender his is big scope creep soI've reverted to old mock - it was causing confusion and I want to keep us focused on getting the switch in.

So let's talk about this here...
I see two separate tasks here in this mock:

1. informational overlay
2. feedback links

Let's create tasks for both of those (cc @ovasileva )
Also are we sure we want feedback links given the problems we had before (see T187712 )

Given that these will be just for logged-in users, I am less worried about adding a feedback link here. However, I do agree that this should be a separate task. I also had a couple of questions on the timeline - @alexhollender - let's discuss tomorrow.

@ovasileva is this epic still current? It seems done to me.