New 42-day free trial Get it now
Smarty
RecommendedFunctional options pattern in Go: Flexibility that won’t make future-you sigh loudlyFebruary 10, 2026Ambiguous address matches: What they are and why compliance teams should careFebruary 3, 2026Smarty's January 2026 release adds parcel boundaries, provisional addresses, and smarter international geocodingJanuary 27, 2026

Google retracts physical address requirement for Play Store developers

Google Strands
Updated October 29, 2025
Tags
Address validation blog tagAddress validationCustomer experience blog tagCustomer experienceAddress verification blog tagAddress verification
Google Strands

Must have address to play

Every month, tens of billions of apps are downloaded from the Google Play store. Users of those apps have historically had limited contact with the app developers for asking questions or lodging a complaint. And getting a response from some developers has proved to be a very difficult experience.

Google briefly considered requiring app developers to provide their physical address or have their app removed from Google's play store. Providing a physical address where customer questions or complaints can be handled would work well for developers that have a separate business address.

Image of usps address verification Google Play

Simple solution

However, many Google Play app developers are work-from-home freelancers who feel uncomfortable with giving out their home addresses to a company that already has most of their identifying data. Additionally, Google was concerned that developers might enter a fake address. The fake-address issue could easily be solved by using simple address verification services like those provided by Smarty. However, never one to use a simple solution, Google has decided jump into the Big Brother arena with their latest project, Google Strands: a DNA-based developer identification system.

Strands of truth

With Google Strands, app developers can fill out a simple request in Google Play and have the Strands kit sent to them free of charge. Within 2 days, a DIY cheek-swab kit will arrive at the developer's preferred address.

cheek swabbing a cat

The developer simply swipes the inside of their cheek with the swab and returns it to Google. Google then rapidly sequences the developer's DNA, and the developer's unique DNA sequence is immediately linked to all of the developer's Google Play apps.

Plans are also in the works for developers to be able to simply lick their webcam to expedite the DNA sequencing process. Job applications from developers to work on the new app have been sparse, though several developers have sent in stool samples to Google corporate headquarters for DNA sequencing in lieu of a formal application. A release-date for the new app has not yet been published.
 

(This post is intended to be a satirical commentary on Google Play's address requirement.)

Subscribe to our blog!
Learn more about RSS feeds here.
Read our 5 address validation use cases ebook now
Read our recent posts
Functional options pattern in Go: Flexibility that won’t make future-you sigh loudly
Arrow Icon
SDK authors live in a permanent tug-of-war:Users want a simple constructor they can paste and ship. Maintainers want room to grow without breaking everybody’s build on the next release. That second part matters a lot right now, because a lot of people are still relatively early in their software careers. Approximately one in three developers has coded professionally for four years or less. That matters because unclear or fragile APIs disproportionately hurt newer developers—they don’t have scars yet.
Ambiguous address matches: What they are and why compliance teams should care
Arrow Icon
If you’ve ever run into an address that seems to exist in more than one place, congratulations—you’ve discovered the world of ambiguous address matches. They’re the Schrödinger’s cat of location data: valid, yet potentially two distinct locations. This blog will focus on a few key things: What are ambiguous address matches?Why ambiguous address matches matter for compliance and customer serviceHow to handle matches with address ambiguityWhy you should inform your customers of ambiguous address matchesOur final thoughts on ambiguous address matchesWhat are ambiguous address matches?An ambiguous address match occurs when an entered address resolves to two or more valid locations with slight but meaningful differences.
Smarty's January 2026 release adds parcel boundaries, provisional addresses, and smarter international geocoding
Arrow Icon
OREM, UT, Jan 27, 2026—Smarty®, an expert in address data intelligence, today announced a three-part release designed to help organizations turn messy, fast-changing location data into operational confidence. The January 2026 bundle introduces: 1) A brand-new parcel dataset, 2) Expands provisional address programs into core U. S. products, and 3) Upgrades Smarty’s International Geocoding engine—giving organizations more precision and more usable signals for automation at scale. “Address data is never ‘done.
Next Post
Previous Post

Ready to get started?

Schedule Demo