I spent three years refusing to organize group drives with friends who had the “wrong” phone. If our group chat had even one Android user among the iPhones, I’d quietly downgrade my expectations for coordination to “just text when you get there.” I told myself it was a technical limitation, when really I just didn’t want to figure it out.
I had organized dozens of group trips by that point, so I should have known better.
The stubbornness broke on I-35 south of Dallas, Thanksgiving weekend. Five cars, a mix of Pixels and iPhones and a Galaxy. Somebody clipped a tire on road debris outside Waco, and within seconds every person in the group could see exactly whose dot had stopped and where.
After that trip I stopped treating the iPhone-Android divide as a real barrier.
Priya is the reason I’d been thinking about it at all.
The Group Chat Nobody Talks About
My friend Priya got a Pixel. She’d been on iPhones forever, switched for the camera, loved it. Good for her. Except our friend group had been sharing locations through FindMy for years, and FindMy doesn’t work with Android.
Nobody said anything directly. We just stopped including her in the location-sharing circle. She’d ask “where are you guys?” in the group chat and someone would screenshot their FindMy map and text it to her like that was a reasonable substitute for live tracking. She stopped coming on road trips for a while and said she was busy. Months later, over dinner, she admitted she hadn’t been busy at all; she was tired of her phone always being the complication.
And I, the guy who organized every single one of those trips, did nothing about it because solving the cross-platform problem felt like more work than just accepting the split. I’m still a little annoyed at myself about that.
Why Does Everyone Assume This Won’t Work?
Blame the ecosystems. Apple built AirDrop, iMessage location sharing, and FindMy to work exclusively with other Apple devices. Google built Nearby Share and Google Maps sharing to favor Android-to-Android.
For those built-in tools, the assumption holds, and mixing phones really is a compromise.
Apps that route data through a shared server work differently, because the phone’s operating system barely matters to them. A Pixel sends GPS coordinates to a server over a WebSocket connection, and an iPhone receives that data from the same server over its own connection. The server doesn’t know or care what brand manufactured either device; it just moves numbers.
Think about a Zoom call where someone joins from a MacBook and another from a Windows laptop, and nobody thinks twice about it. Konvoyage follows the same pattern as Zoom: each phone only has to talk to the server, and the server is what keeps everyone’s positions in sync.
What the Setup Actually Looks Like
One person creates a trip and gets a six-character code to text to the group.
Everyone signs in with Google first, which means tapping a button and picking an account that’s already on the phone (there’s no password or email form to fill in). Then they enter the code and join, with their name already filled in. Nobody sends friend requests, and nothing has to pair over Bluetooth. The code doesn’t know what phone you typed it into, and it doesn’t need to.
Preparing each device does differ a little, and skipping one of these small steps is how a trip goes wrong.
For Android users (Pixel, Samsung Galaxy, OnePlus, etc.):
- Location permission needs “Allow all the time.” The app explains why and then sends you to the screen where you pick it. If you tapped something else, go to Settings > Apps > Konvoyage > Permissions > Location and switch to the always-on option. Skip this, and the app will tell you background tracking is disabled, which means your dot stops updating once the screen locks.
- Battery optimization is the single biggest source of problems on Android. Samsung phones ship with aggressive power-saving defaults that kill background apps. Go to Settings > Battery > Background usage limits and make sure Konvoyage isn’t restricted.
- You’ll see a persistent notification while tracking is active. Don’t dismiss it, because that’s proof the app is working.
For iPhone users:
- Set location to “Always” when prompted. If you chose “While Using the App” by mistake, fix it at Settings > Privacy & Security > Location Services > Konvoyage.
- A blue arrow in your status bar means background location is active. Normal.
- Low Power Mode reduces GPS update frequency. Plug into a car charger before departure and leave it plugged in.
Signal Drops and Fading Dots
Anyone who has organized a multi-car trip eventually gets asked what happens when someone loses signal.
The behavior is identical on both platforms, because the server controls it. When a phone stops sending location data (tunnel, mountain pass, dead zone on a rural highway in West Texas), everyone else sees that person’s dot fade at its last known spot with a “no signal” label, rather than a guessed position. Meanwhile the disconnected phone keeps recording where it goes, and chat messages typed in the dead zone wait in a queue. Once signal returns, the phone reconnects, sends what it saved, and the dot starts moving again on its own.
If your route includes stretches with genuinely zero coverage, download offline maps in Google Maps before you leave (the app itself suggests this), and start navigation while you still have data, since turn-by-turn needs a connection to get going.
A Stopwatch Test Nobody Asked For
Android reconnects slightly faster after a signal gap because its foreground service keeps the WebSocket connection warm. iOS takes a beat longer. You will not notice the difference in practice. I tested it with a stopwatch once because that’s the kind of person I am. My friends found the results far less interesting than I did.
Differences That Actually Exist
Cross-platform still doesn’t mean the two kinds of phone behave identically.
Battery drain runs higher on Android during active tracking, because Android’s continuous GPS polling through a foreground service consumes more power than Apple’s CoreLocation framework. If your Android friend’s phone isn’t fully charged at departure, they need a charger.
GPS accuracy on modern flagships is nearly identical across platforms, and both degrade about the same in heavy tree cover or mountain terrain.
The map itself looks slightly different. Android renders with Google Maps, iPhones use MapKit. Your group’s live location dots look the same everywhere, but road labels and satellite imagery come from different providers. This affects nothing practical. The markers do change as you zoom out, dropping names and photos until only plain dots are left so a big group doesn’t bury the map, and I went into that in why your group’s dots disappear when you zoom out.
Night-Before Prep
Reading about cross-platform compatibility the night before a trip probably means you’re the one who ends up organizing it anyway.
Send the download link tonight to anyone who doesn’t have the app yet. Not tomorrow morning when everyone’s packing the car.
If everyone has the app, create a test trip and share the code so people can join from the couch. That’s when a permission problem or a forgotten Google sign-in shows up, and fixing it at home takes a minute instead of holding everyone up in a parking lot. I run this test before every trip, and the groups that skip it tend to be the ones texting me from a gas station asking why their dot isn’t showing up.
Swap the driving order if the lead car has the weakest phone or worst data plan. People glance at the front dot more than any other, so put the strongest GPS and most reliable connection up there.
Before you go to bed, check the test trip one last time and make sure every dot is on the map, including the friend who switched phones and has quietly been left out of things. Send that person the code first.