What about non EU users? Americans don't second guess themselves when they slap google/apple/meta sign in only. They know everyone in the world will never pause when they see their logo on the buttons. To reach this scale of worldwide adoption for a European service requires a massive amount of investment.

What's even the entry point? Google and Apple make the devices that everyone uses. Even if you build a service like you suggested, how do you ensure that everyone is using it?

▲

danelski 8 hours ago | parent [-]

> They know everyone in the world will never pause when they see their logo on the buttons.

As in, that they won't run away when they see them or that they will all happily use them? If you mean the latter, then it's just false. Also, why do you assume that such product would need to be used worldwide all of a sudden? Having something for the local market would be sufficient to call it a success in this instance. There's an ICC judge who could tell you a thing or two about having a whole digital life on the hook of services from one country, so reducing this dependency is a clear benefit.

▲

stackbutterflow 7 hours ago | parent [-]

> Also, why do you assume that such product would need to be used worldwide all of a sudden

Because I'm talking about not running on any American services. Which Americans can do and do all the time. I don't see how we can reach a point where we can one day not include google/apple sign in and not lose a massive number of potential users. Sure it's possible that one day we'll see a "Sign in with EU login" but below it they're always be sign in with google/apple, for a very long time.

	▲	danelski 6 hours ago \| parent [-]
		That post mostly concerned infrastructure, you won't likely run the same managed DB with 2 different providers, for example, but you can well offer sign-in with EU/non-EU options, and as long as the first one is viable, I'd say that would already be a win in terms of OP's goals.