Why Should Mobile Devs Care About Cloud?
For the first 3 years of my career, I thought of the cloud as "someone else's problem." I'd call an API, get JSON back, and display it. What happened on the other side of that HTTP request was a mystery.
Then I joined PhonePe, where the backend runs on Azure, and I realized: understanding the cloud makes you a 10x better mobile developer.
The Services That Matter
Azure App Configuration
What it does: Centralized configuration management. Feature flags, A/B test parameters, and runtime config — all manageable without app updates.
Why you should care: Instead of hardcoding feature flags or waiting for Play Store review, you can toggle features remotely. At PhonePe, we use App Configuration to:
- Roll out features gradually (1% → 10% → 50% → 100%)
- Kill switches for broken features
- Regional configuration (different settings for different states)
As an Android dev, understanding this service helped me design our feature flag SDK to work seamlessly with App Configuration's key-value structure and label system.
Cosmos DB
What it does: Globally distributed NoSQL database with multiple consistency levels.
Why you should care: When your API returns stale data or takes too long, it's often a database issue. Understanding Cosmos DB's consistency levels (strong, bounded staleness, session, eventual) helped me understand why certain screens showed stale data and how to design proper cache invalidation.
Azure Functions
What it does: Serverless compute. Run code in response to events without managing servers.
Why you should care: Push notifications, analytics processing, image resizing — all commonly implemented as Azure Functions. Understanding the cold start problem explained why our push notification processing sometimes had a 30-second delay.
Azure CDN & Blob Storage
What it does: Content delivery and file storage.
Why you should care: Every image, video, and file your app loads comes from somewhere. Understanding CDN edge locations, cache headers, and blob storage tiers helped me optimize our image loading pipeline and reduce bandwidth costs by 25%.
Real-World Impact
Incident Response
When our payment confirmation screen started timing out, I didn't just report "API is slow." I looked at the Azure Monitor dashboard, identified that Cosmos DB RU consumption had spiked due to a non-indexed query, and pointed the backend team to the exact problematic query. Time to resolution: 20 minutes instead of 2 hours.
Architecture Discussions
When designing a new offline-first feature, I could meaningfully contribute to discussions about Cosmos DB change feed for syncing, Azure Functions for conflict resolution, and App Configuration for controlling sync frequency.
Better SDK Design
My analytics SDK at Glance was designed to batch events efficiently because I understood how Azure Event Hubs processes messages. Instead of sending one event at a time, we batch up to 100 events and send them together — saving battery and reducing server costs.
Getting Started
- Take AZ-900 — It's the easiest Azure cert and gives you a broad overview. Study for 2 weeks, pass the exam.
- Read your company's architecture docs — Most companies have architecture diagrams. Find them and understand what services you depend on.
- Get Azure Portal access — Ask your DevOps team for read-only access. Just being able to see metrics and configurations is valuable.
- Attend backend standups — Even once a month. Understanding what the other side is dealing with builds empathy and collaboration.
The Payoff
You don't need to become a cloud expert. But knowing enough to read a dashboard, understand a service's limitations, and contribute to cross-team discussions will set you apart from 90% of mobile developers.
The cloud isn't someone else's problem. It's the other half of your app.