Offline-First Architecture in Android Apps with Room and WorkManager

Why Offline-First Matters

Most mobile users in India experience intermittent connectivity — patchy 4G coverage in tier-2 cities, sudden Wi-Fi drops, and airplane mode commutes. An application that freezes on every network failure is not production-ready. Offline-first architecture flips the data flow: the local database is the source of truth, and network sync happens opportunistically in the background.

The Three-Layer Architecture

A robust offline-first Android app uses three clearly separated layers:

1. Room Local Database: The permanent local cache. Every read operation pulls from Room, never directly from the network API.
2. Repository Layer: The single source of truth coordinator. It decides whether to serve cached data or trigger a background sync request.
3. WorkManager Sync Job: A constraint-aware background task. It retries on connectivity restoration automatically.

Setting Up Room for Offline Storage

@Entity(tableName = "sensor_readings")
data class SensorReading(
    @PrimaryKey val id: String,
    val temperature: Float,
    val humidity: Float,
    val timestamp: Long,
    val synced: Boolean = false // Track if this row has been uploaded
)

@Dao
interface SensorDao {
    @Query("SELECT * FROM sensor_readings ORDER BY timestamp DESC")
    fun observeAll(): Flow<List<SensorReading>>

    @Insert(onConflict = OnConflictStrategy.REPLACE)
    suspend fun upsert(reading: SensorReading)

    @Query("SELECT * FROM sensor_readings WHERE synced = 0")
    suspend fun getPending(): List<SensorReading>
}

Scheduling Sync with WorkManager

WorkManager provides guaranteed execution with retry and network constraints — it will retry until the job succeeds, even if the device reboots mid-sync.

val syncRequest = PeriodicWorkRequestBuilder<SyncWorker>(15, TimeUnit.MINUTES)
    .setConstraints(
        Constraints.Builder()
            .setRequiredNetworkType(NetworkType.CONNECTED)
            .build()
    )
    .setBackoffCriteria(BackoffPolicy.EXPONENTIAL, 30, TimeUnit.SECONDS)
    .build()

WorkManager.getInstance(context).enqueueUniquePeriodicWork(
    "sensor_sync",
    ExistingPeriodicWorkPolicy.KEEP,
    syncRequest
)

Conflict Resolution Strategy

When the same record is modified both locally and remotely while offline, a conflict resolution policy is essential. A common approach: server-wins with timestamp comparison. Include a server_updated_at column in Room, and on sync, only overwrite if the server timestamp is newer.

Conclusion

Offline-first is not optional for Android apps targeting Indian markets. Room + WorkManager gives you a battle-tested combination that handles network failures gracefully without requiring complex state machines.

Need a custom offline-capable Android app? Let's talk →