To me a weird part where these hit hard is on shared access to common resources. The two options I see are either: - Have shared access baked in the service

To me a weird part where these hit hard is on shared access to common resources. The two options I see are either: - Have shared access baked in the service and each user has its own account, with its own auth means - Go through elaborate schemes to somewhat share a single account's credentials. Shared access with multiple accounts is currently a PITA in most services. Apple for instance still doesn't really understand how families work. Google is also suboptimal, even for cases like common photo libraries (not albums, whole libraries), and their weird separation of standard accounts getting access to all services under the sun, and GSuite/Workplace "second class" accounts doesn't help at all. I don't see Microsoft being better on most of its services, but I don't use them enough to have a strong opinion. So the remaining way to handle these fairly common issues is to have a master account shared among two or more people, and most of these auth options rely on biometrics or fairly personal services. If that's the path forward, I wish they'd clear the surrounding issues first.