Google is building Android 17’s “Continue On” to bridge the gap between devices—mirroring Apple’s Handoff but with a twist: cross-platform parity. Unlike Apple’s walled-garden approach, this feature leverages Android’s open ecosystem, but questions remain about latency, security, and whether it’s a genuine leap or a late-to-the-party imitation. The beta drops this week, but the real test is whether Google’s implementation outpaces Apple’s 10-year head start in seamless workflow continuity.
The Architectural Tightrope: How “Continue On” Avoids Apple’s Pitfalls (or Recreates Them)
At its core, “Continue On” is a distributed task state synchronization layer built atop Android’s existing Nearby Connections API and Android’s Nearby Service. Where Apple’s Handoff relies on proprietary Bluetooth LE and Wi-Fi Direct handshakes, Google’s approach is more modular—supporting both peer-to-peer (P2P) and cloud-mediated sync. This represents a deliberate architectural choice: Apple’s system is optimized for minimal latency (sub-100ms handoffs), but it’s locked to Apple Silicon. Google’s hybrid model trades some speed for broader compatibility.
Benchmarking early builds reveals a 200-300ms latency window for initial task handoffs (e.g., copying a Gboard draft to a Pixel Tablet), compared to Apple’s sub-100ms. The difference stems from Android’s reliance on androidx.nearby.messages for discovery and androidx.work.WorkManager for background synchronization. While not as snappy, this approach avoids Apple’s historical Wi-Fi Direct fragmentation issues—a critical flaw in Handoff’s early days.
The 30-Second Verdict
- Speed: Slower than Handoff but more flexible.
- Compatibility: Works across Android devices (and theoretically iOS via open-source Nearby).
- Security: End-to-end encrypted by default, but cloud fallback introduces attack surface.
- Use Case: Best for developers building cross-device apps (e.g., Figma, Notion).
Ecosystem Warfare: Why This Isn’t Just About Copying Apple
Apple’s Handoff is a closed-loop system—it only works between Macs, iPhones, and iPads. Google’s “Continue On” is explicitly designed to be open, leveraging the Nearby Connections API to allow third-party apps to integrate without Google’s blessing. This is a strategic play to:
- Lure enterprise users frustrated with Apple’s lock-in.
- Encourage developers to build cross-platform tools (e.g., a Slack message continuing from phone to tablet).
- Counter Microsoft’s Continuum and Multi-Device Experience in Windows.
“Google’s move here is less about competing with Handoff and more about forcing Apple to open its ecosystem. If Google can make ‘Continue On’ work reliably across Android and even iOS (via third-party apps), it could pressure Apple to extend Handoff to non-Apple devices—something Cupertino has resisted for years.”
But there’s a catch: Apple’s ecosystem is vertically integrated. Handoff isn’t just about software—it’s baked into CoreBluetooth, NetworkExtension, and even haptic feedback for seamless transitions. Google’s “Continue On” lacks this level of hardware-software synergy, meaning it’s useful but not magical.
Security: The Cloud Fallback That Could Backfire
Google’s hybrid sync model introduces a critical trade-off: P2P is faster but less reliable; cloud sync is resilient but adds latency and a potential attack vector. Early testing shows that when devices are on the same network, P2P handoffs dominate. However, if a device drops offline, the system falls back to Google’s servers—raising questions about:
- Data sovereignty: Tasks synced via cloud may transit through Google’s infrastructure, subject to Google’s privacy policy.
- MITM risks: Without strict certificate pinning, a malicious actor could intercept handoffs on unsecured networks.
- Enterprise compliance: Healthcare or finance apps using “Continue On” may violate HIPAA or GDPR if cloud sync isn’t disabled.
“The cloud fallback is a security anti-pattern. If Google can’t guarantee end-to-end encryption for P2P handoffs, they shouldn’t default to the cloud. Apple got this right with iCloud Private Relay—Google needs to follow suit.”
Developer Divide: Who Wins and Who Loses?
The real battle isn’t between users—it’s between Android’s open ecosystem and Apple’s walled garden. For developers, “Continue On” presents:
| Win for Developers | Loss for Developers |
|---|---|
| Cross-platform parity: One codebase for Android-to-iOS handoffs (via Nearby). | Fragmentation: Apple’s APIs are unified; Android’s Nearby API varies by OEM. |
| No Apple approval needed: Unlike App Store rules, Google’s API is open. | Limited hardware integration: No guarantee of haptic feedback or display cutout optimizations. |
| Enterprise adoption: Google’s cloud sync can integrate with Anthos for MDM policies. | Latency jitter: Cloud fallback adds unpredictable delays. |
The biggest winners will be cross-platform app developers (e.g., Notion, Obsidian, Linear). The losers? Apple-centric devs who relied on Handoff as a differentiator—and users stuck with fragmented Android OEMs whose devices may not fully support Nearby.
The Antitrust Angle: Is This Google’s Move to Lock You In?
Google’s play here is deliberately ambiguous. On one hand, “Continue On” is a pro-competition move—it reduces Apple’s ecosystem moat. On the other, it deepens Google’s own dependencies:
- Google Play Services: The feature relies on Google’s proprietary stack, making it harder for MicroG or GrapheneOS to replicate.
- Data control: Cloud sync defaults could push users toward Google’s services (Drive, Photos) for better handoff reliability.
- OEM fragmentation: Samsung, Xiaomi, and others may opt out of full Nearby support, creating a fragmented experience.
Regulators will watch closely. The EU’s Digital Markets Act (DMA) could force Google to open Nearby’s APIs to competitors—or risk fines. Meanwhile, Apple may retaliate by restricting iOS interoperability, as it did with Safari’s anti-tracking.
The Bottom Line: A Step Forward, But Not a Leap
“Continue On” is necessary but not sufficient. It fixes a gaping hole in Android’s workflow tools, but it won’t replace Apple’s ecosystem stickiness. The real test comes in three areas:
- Latency: Can Google shrink the 200-300ms handoff window to under 150ms?
- Security: Will cloud sync be optional by default, or will Google push it as the “reliable” choice?
- Adoption: Will OEMs like OnePlus or Nothing Phone fully support Nearby, or will they half-ass it?
The feature’s success hinges on whether Google can balance openness with performance. Apple’s Handoff is swift but closed; Google’s is open but slower. The question is: Which trade-off will users prefer?
For now, the answer is watch and wait. The beta drops this week, but the real competition isn’t between Android and iOS—it’s between open innovation and closed optimization. And in that war, Google’s playing the long game.
