Google Messages Is About to Let You Drop a Pin Mid-Conversation — and It Says a Lot About Google’s Messaging Ambitions

Google is building native location sharing into its Messages app, letting users drop pins and share live coordinates within RCS conversations. The feature, discovered in code by Talk Android, signals Google's aggressive push to close the gap with iMessage and WhatsApp.
Google Messages Is About to Let You Drop a Pin Mid-Conversation — and It Says a Lot About Google’s Messaging Ambitions
Written by Ava Callegari

For years, sharing your location through a text message on Android has been a clunky affair — screenshot a map, paste a Google Maps link, or just type out an address and hope for the best. That’s about to change. Google is building native location sharing directly into its Messages app, a feature that would let users send their real-time or pinned location without ever leaving the conversation thread.

The feature was first spotted by the team at Talk Android, which reported that strings of code discovered in a recent Google Messages update point to an integrated location-sharing tool. According to the publication’s analysis, the upcoming feature will allow users to share a specific point on a map — essentially dropping a pin — or share their live location for a set duration, all within the RCS-powered messaging interface Google has spent the last several years pushing as its default standard.

This isn’t a minor UI tweak. It’s a strategic move.

Google has been methodically transforming its Messages app from a bare-bones SMS client into something that more closely resembles iMessage or WhatsApp. RCS (Rich Communication Services), the protocol that underpins the modern version of Google Messages, already supports read receipts, typing indicators, high-resolution media sharing, and end-to-end encryption in one-on-one conversations. Location sharing is one of the last conspicuous gaps between Google Messages and its more feature-rich competitors.

The code strings uncovered by Talk Android suggest the feature will present users with a familiar interface: a map view embedded in the attachment options, with the ability to search for a location or select the user’s current position. There also appear to be options for sharing live location over a defined time window — 15 minutes, one hour, or until manually turned off. That mirrors the approach taken by WhatsApp, which introduced live location sharing back in 2017, and Apple’s iMessage, which integrates tightly with the Find My framework for similar functionality.

Why Location Sharing Matters More Than It Seems

On the surface, sending someone a pin on a map doesn’t sound like much. But in the context of Google’s broader messaging strategy, it fills a critical role. Google has spent years lobbying Apple — publicly and loudly — to adopt RCS, arguing that the green-bubble/blue-bubble divide creates a degraded experience for cross-platform texters. Apple eventually relented, announcing RCS support for iOS 18 in late 2024. But the version of RCS Apple implemented is limited. It doesn’t include some of the richer features Google has built into its Android implementation.

That creates a dynamic where Google needs its own RCS experience on Android to be as polished and complete as possible. Every missing feature is an argument for users to default to a third-party app instead. And Google cannot afford that. The company’s entire mobile advertising and services model benefits from keeping users inside Google-controlled surfaces. If a user opens WhatsApp to share a location instead of staying in Google Messages, that’s a small but meaningful loss of engagement.

Location sharing also has practical implications for Google’s push into business messaging via RCS. Retailers, delivery services, and restaurants increasingly use RCS channels to communicate with customers. A native location-sharing feature could allow a delivery driver to share live coordinates with a customer, or let a user send their pickup location to a rideshare service — all through the default messaging app rather than a dedicated third-party application.

There’s competitive pressure from multiple directions. WhatsApp, owned by Meta, dominates global messaging with over two billion users and has offered location sharing for years. Telegram, Signal, and even Facebook Messenger all include it. Apple’s iMessage has had location features baked in since iOS 8. Google Messages has been the outlier among major messaging platforms in lacking this capability natively.

The timing of this discovery is also notable. Google has been on an aggressive feature-shipping cadence for Messages throughout 2025. Earlier this year, the company rolled out Gemini AI integration directly into conversations, allowing users to summon Google’s AI assistant mid-chat. It also expanded emoji reactions, improved group chat management for RCS threads, and added better support for scheduling messages. Each addition narrows the feature gap between Google Messages and dedicated chat apps.

But there are open questions. The code strings found by Talk Android don’t clarify whether location sharing will work in SMS/MMS fallback mode or only in RCS conversations. This distinction matters enormously. If the feature requires both parties to be on RCS — which means both on Android with Google Messages as their default, or on an iPhone running iOS 18 with RCS enabled — its utility will be limited in mixed-protocol conversations. Given that RCS messages between Android and iPhone still lack end-to-end encryption (Apple’s implementation doesn’t support Google’s encryption extensions), sending live location data over an unencrypted channel raises obvious privacy concerns.

Google hasn’t officially announced the feature or provided a timeline for its release. That’s typical. The company frequently seeds code for upcoming features into app updates weeks or months before flipping them on for users. Some features discovered in code teardowns never ship at all. But the level of detail in the strings — specific time intervals for live sharing, map integration references, UI element descriptions — suggests this one is relatively far along in development.

For Android users who’ve been cobbling together workarounds to share their location via text, the addition will be overdue and welcome. For Google, it’s another brick in the wall of an argument the company has been making for half a decade: that RCS, and specifically Google’s implementation of it, deserves to be the default messaging standard on every phone. Whether that argument ultimately prevails depends on execution. And on whether Apple ever meets Google halfway on the richer features that make RCS worth using in the first place.

For now, the pin is about to drop. Literally.

Subscribe for Updates

AIDeveloper Newsletter

The AIDeveloper Email Newsletter is your essential resource for the latest in AI development. Whether you're building machine learning models or integrating AI solutions, this newsletter keeps you ahead of the curve.

By signing up for our newsletter you agree to receive content related to ientry.com / webpronews.com and our affiliate partners. For additional information refer to our terms of service.

Notice an error?

Help us improve our content by reporting any issues you find.

Get the WebProNews newsletter delivered to your inbox

Get the free daily newsletter read by decision makers

Subscribe
Advertise with Us

Ready to get started?

Get our media kit

Advertise with Us