Ohio joins Google Wallet's state ID list 45 months after Maryland

Eleven states and one territory is the entire list, and the pace behind it is the part worth pricing. Maryland went live in December 2022 and Ohio in September 2026, according to 9to5Google's rollout tracker ^[1], which works out to 45 months for the 11 jurisdictions added after Maryland, roughly one every four months ^[2]. Five of the twelve arrived during 2025 ^[3]. Coverage sits at 22% of states ^[1], so a flow that treats the mobile licence as its only acceptable credential locks out most of the country.

The split that actually matters is between what enrollment does and what presentation does. To add the card, a user photographs the front and back and records a short video, and a frame from that video goes to the issuing agency ^[4]. Nothing like that happens afterwards. When an app asks for age, the user gets a system-level sheet, confirms the share and authenticates with device unlock ^[8]. Google says its zero-knowledge proof work is meant to answer those requests "without any possibility to link back to a user's personal identity," and that the technology will be open-sourced ^[9]. An mDL share hands the requester an assertion rather than pictures of a card, which is what a lot of compliance files were built to store ^[4].

Holders tap at the airport, then keep the plastic in the wallet, because Google tells them to ^[6] and because almost nothing else takes the phone. DMV counters accept it in Arizona, Georgia, Maryland and New Mexico ^[10], and car rental apps are described as beginning to accept digital IDs for identity and age checks ^[7]. A commenter on the 9to5Google post, an Ohio resident named Connor, put the user's position plainly: the ID was announced more than a year before it shipped and is still useless, because the physical card is needed for almost everything, alcohol purchases included ^[13].

For anyone who owns an onboarding step, two axes decide this. First, does the step need an assertion (over 21, name matches) or an artifact (a stored image, a number read off the card)? Second, does the moment happen on the phone or somewhere else? For an assertion requested on the phone, an mDL path pays for itself now, and it is where Google is aiming its own pipeline. Pushed to a desktop, that same assertion costs a QR handoff to a second device ^[8], the kind of step your funnel already punishes. And any artifact request, on any device, still means a camera capture, so the mDL adds a branch without retiring one. Accepting mDLs early has a real price: two verification paths to maintain, one serving a minority of users, plus the support load when a lost phone means an ID pulled remotely from a Google account page ^[12] instead of a card reported to a DMV.

The rollout list carries no enrollment counts and no acceptance rates, so it cannot be used to size demand. What it does support is a narrower question with a date attached. Refusing the credential is defensible at 22% coverage ^[1]. Refusing it without a written script is how the answer ends up being whatever the newest support hire decided on a Friday.