For most of Android's history, the architecture decision was simple: process on-device (fast, private, limited) or process in the cloud (slow, scalable, powerful). Edge computing breaks that binary. Edge nodes — servers deployed at CDN PoPs, carrier infrastructure, or enterprise data centres — sit between the device and the origin cloud, offering cloud-level compute at near-device latency.
What Edge Computing Actually Means for Mobile
In practical terms: Cloudflare Workers, Fly.io, and AWS Lambda@Edge run your server logic at locations <20 ms from most users. Vercel Edge Functions, Supabase Edge Functions, and Firebase's new regional Cloud Functions deployment give you sub-50 ms server round-trips globally. The architecture implication: operations that were too slow for real-time (server-side AI inference, complex queries) become viable.
The Three-Tier Model: Device → Edge → Cloud
Architect with three explicit tiers: (1) Device — handles UI, local caching, offline operation, and simple on-device ML. (2) Edge — handles real-time operations that need server compute: personalisation, A/B testing logic, lightweight AI inference, fraud signals. (3) Cloud — handles data storage, complex processing, batch jobs, and operations that don't need to be real-time.
Edge for Real-Time Features
The killer use case for edge in Android apps: real-time features that currently require a round-trip to a distant data centre. Live auction bid validation (Cardamom Live uses Fly.io nodes in India — 18 ms vs 180 ms to a US data centre). Real-time delivery tracking ETA calculations. Live search ranking personalised to the user's history.
Implementing Edge Awareness in Your Android Architecture
Your app doesn't need to know about edge explicitly — that's the beauty. Use OkHttp with your edge-deployed API URL. The edge node handles request routing, caching, and computation. Add a custom header (X-Device-Capabilities) so your edge function knows what the device can handle locally and responds accordingly — this is the "capability negotiation" pattern for device-edge collaboration.
Cost and Complexity Trade-offs
Edge compute isn't free. Cloudflare Workers cost $0.30/million requests beyond the free tier — cheap at scale but non-trivial for indie apps with low volume. Debugging distributed edge logic is harder than a monolithic server. Start with edge for your highest-latency, highest-frequency operations only. Don't migrate everything; profile first and apply edge where the latency delta justifies the complexity.