Mine: require setting a URL to support password managers. You download an app, go to login, tap the password field, and open Bitwarden. Does it find your login? Half the time, nope! The dev didn’t tell Apple one time what their URL is, so everyone now has to search their password manager every time.
I know 1Password can detect the app ID and use that as a match criteria. The problem is that it is not user intuitive to get the app ID to key into password manager; also doesn’t change the fact that the app most of the time just front end to some website, which already has an entry for the website, and shouldn’t require the user to go out of their way to find App ID to work around the dev’s inability to surfacing basic metadata about their service.
Bitwarden and other password managers get the app Id automatically on Android and can have multiple apps/websites associated to a password, you only need to search once and tap “auto fill and save”
Apple community, we don’t care about android; sorry but not sorry. And yes, it is possible, I don’t think anyone is arguing that. The discussion is more what should happen in “the Apple way” where things just work — and that’s something Apple can mandate on app developers… something that might be pretty foreign and alien to the android crowd.
Our point was that it doesn’t need to involve app developers at all, it should just be handled by the OS automatically.
It doesn’t hurt to look over the fence and see what works.
Being aware of something outside of your own ass, something pretty foreign and alien to an apple fanboy like you.
It’s people like you who made it possible for Mac os to not have proper snapping until 2024.