app routing UX inconsistencies
Currently the app shows different information about whether All, None or particular apps are routed over the VPN (aka. "protected") at different places of the app. I will try to summarize UX inconsistencies here:
- On the connect screen, the subtitle of the Apps super toggle only shows Protect all apps or None protected, a state for X apps protected doesn't exist yet. If you click on the left part of the Apps super toggle the app routing screen appears (title of that screen is Apps) showing a list of all installed apps. It can reveal that some apps are protected while the global toggle is disabled and the previous connect screen showed None protected
- If the global Protect all apps toggle in the app routing screen is checked, all apps traffic will still be routed over the VPN, even though the manual toggle at the end of each app entry might be unchecked. In context of the App routing screen this becomes obvious, because the manual toggle can't be changed (= is disabled) if the global toggle is checked. However, in contrast to that the toggle of the app detail screen (which appears after the user tapped on an app list entry in the app routing screen) is never disabled if global tor routing is enabled.
- In addition to that, on that app detail screen it is not obvious anymore that an app might still be routed over tor, because there's no indication if global routing is enabled or not.
Proposed solutions: for 1.:
- We can add a string X apps protected or X apps manually protected if the global routing is unchecked but some apps have been manually selected to be routed over the VPN. This string would be shown in the connect screen as a subtitle of the Apps super toggle
for 2.:
- we disable the manual Protect this app toggle in the app detail screen if the global routing toggle is checked, similar ing to the UX in the App routing screen
for 3.
- if the global routing toggle is checked, we show a string in the app detail screen indicating that the app will be routed over the VPN (even though the toggle is in an disabled and maybe unchecked state)
@donuts I'll assign this ticket to you first due to the open UX questions, please reassign me, if you have decided solutions for these inconsistencies.