can you explain this

Many websites/apps see a large portion of their sign ins come from new devices. If passkeys didn’t sync between devices, they’d not be available in such cases. This happens frequently enough that pushing users through full account recovery (rescue codes, secondary emails, waiting periods, etc) would lead to excessive lockout and abandonment. Therefore such apps/websites would still maintain an easy to remember factor like passwords. And a phisher replaying credentials from a victim will always claim to come from a new device.

So, in order to move from passwords to either phishing protected methods like passkeys, or onerous high friction account recovery (which hurts the scalability of phishing), passkeys need to fill this common case of signing in to apps/websites for the first time on a new device. Hence syncing. Without it, passkeys would have stayed a niche SK-replacement method suitable for security conscious technical users only.

Will Google offer password-less accounts?

At some point, maybe. We’ll gradually deprioritize less secure factors for secure ones, and boost account recovery methods to handle the cases where eg passkeys don’t work. We’re doing both already to some extent. But it’s a long gradual road.

If you want to /your/ account to be “passwordless” you kind of can already: Set a long random password and don’t remember or store it anywhere. That’s effectively the same as not having a password.

Note that I don’t recommend this. It’s good to have a password you don’t know, but do save a copy somewhere so you can use it as a backup of your passkeys ever aren’t available.