Part 1: The "Lie-Fi" Problem & The Offline-First Mindset

 How Senior Engineers use SSOT, Room, and Flow to build resilient, production-grade apps that never feel broken.

The "Lie-Fi" Problem & The Offline-First Mindset

TL;DR

  • The Problem: “Online-first” apps break in “Lie-Fi” (zombie connections).
  • The Fix: Move from Request-Response to Single Source of Truth (SSOT).
  • The Flow: UI observes Room → Network updates Room → UI reacts.
  • Priority: Choose Availability (AP) over strict Consistency.

1. The “Online-First” Fallacy

In an online-first model, the UI becomes tightly coupled to the variability of network conditions. This creates a fragile experience where usability is tethered to the health of a remote socket.

The “Zombie” Connection (Lie-Fi): The TCP socket hasn’t timed out, but no data is moving. The app waits for an onResponse that may take tens of seconds (or never) to resolve. To the user, the app isn't "waiting"—it's broken.

Real-World Failure Scenario:

User “Likes” a photo → Network stalls → Heart doesn’t turn red → User taps 5 more times → Network recovers → 5 duplicate API calls sent → UI flickers between states.

2. SSOT Architecture: Room + Flow

In an offline-first Android architecture, the UI should never depend directly on API responses. Instead, the local database acts as the source of truth for the UI, even if the server remains the ultimate source of truth for the system. The network updates the database — not the UI.

class NewsRepository(
    private val newsDao: NewsDao,
    private val apiService: NewsApiService,
    private val ioDispatcher: CoroutineDispatcher = Dispatchers.IO
) {
    // UI observes this stream. Remains functional even if the network is dead.
    val newsArticles: Flow<List<Article>> = newsDao.getArticles()

    suspend fun refreshNews() = withContext(ioDispatcher) {
        try {
            val response = apiService.getLatestNews()
            if (response.isSuccessful) {
                // MERGE server data with local state. Don't blindly replace.
                newsDao.syncArticles(response.body() ?: emptyList()) 
            }
        } catch (e: Exception) {
            handleError(e)
        }
    }

    private fun handleError(e: Exception) {
        when (e) {
            is IOException -> { /* Retryable: Timeout/Lie-Fi */ }
            is HttpException -> {
                // Classify into retryable (5xx, 429) vs terminal (401, 404)
                if (e.code() == 429 || e.code() in 500..599) { /* Retryable */ }
            }
            else -> throw e 
        }
    }
}

3. Handling UI States: More Than Just a Spinner

Your UI must be smarter than a simple boolean. You need to distinguish between:

  • Empty: No data, fetching (Show shimmer).
  • Cached: Displaying DB data (Show content).
  • Refreshing: Background sync active while showing cached data.
  • Error (with data): Sync failed, but usable data exists (Show data + “Couldn’t refresh”).

4. Optimistic UI & Shadow States

Senior-level apps feel instant.

  • Local Mutation: Update Room immediately with an isPending = true flag.
  • Reactive UI: Room emits; the UI updates instantly.
  • Guaranteed Sync: Use WorkManager to ensure the action persists.
  • Reconciliation: If the server rejects, rollback Room. Rollbacks should be non-disruptive (subtle state reversal), not a blocking dialog.

Note: Use versioning or timestamps on local entities to prevent out-of-order server responses from overwriting newer client state.

5. CAP Theorem: Availability Over Consistency

Under network partitions, we prioritize Availability over strict Consistency. We don’t choose inconsistency — we accept it temporarily to preserve usability. The system works in the background to achieve Eventual Consistency.

6. Common Mistakes in Offline-First Apps

  • Treating Room as a Cache: If you wait for onResponse before updating Room, you aren't offline-first.
  • Overwriting Local State: Blindly calling insertAll() wipes out "pending" flags or user edits.
  • Ignoring Idempotency: Retrying a “Post” without an idempotency key creates duplicates.
  • No Sync Trigger Strategy: Not defining when data should refresh (e.g., App Open vs. Pull-to-refresh).

Summary & Next Steps

If your UI depends on the network to function, your app doesn’t own its state — the network does. Real engineering starts when the internet is treated as an optional optimization.

In Part 2, we’ll build the Sync Engine — designing the Outbox pattern and WorkManager orchestration that makes this architecture production-ready.

💬 Join the Conversation

  • How do you handle “Rollbacks” in your Optimistic UI without jarring the user?
  • What’s your TTL (Time-To-Live) for cached data before it’s considered “stale”?
  • Is your current project a true SSOT, or is it a “pass-through” for API calls?

📘 Master Your Next Technical Interview

Since Java is the foundation of Android development, mastering DSA is essential. I highly recommend “Mastering Data Structures & Algorithms in Java”. It’s a focused roadmap covering 100+ coding challenges to help you ace your technical rounds.

Comments

Post a Comment

Popular posts from this blog

No More _state + state: Simplifying ViewModels with Kotlin 2.3

Image
 Clean up your Android code with Explicit Backing Fields—the modern way to handle read-only state without the boilerplate. TL;DR:  Kotlin 2.3 introduces  explicit backing fields , allowing you to replace the classic  _state  +  state  boilerplate with a single, cleaner property—provided you're okay with a few experimental trade-offs. If you’ve been developing Android apps, you know the “Backing Property Dance.” It’s that repetitive ritual where we create a private  MutableStateFlow  and a public  StateFlow  just to ensure encapsulation. The “Old” Way (The Boilerplate) private val _uiState = MutableStateFlow(UiState.Loading) // Exposing a read-only view of the mutable internal state val uiState: StateFlow<UiState> = _uiState.asStateFlow() We’ve done this for years to prevent external classes from mutating our state. While effective, it pollutes our IDE suggestions with underscores and adds unnecessary ceremony to every singl...
Read more

Why You Should Stop Passing ViewModels Around Your Compose UI Tree 🚫

Image
 Master State Hoisting and the "Route-level" pattern to build scalable, testable, and preview-friendly Android apps. If you’ve been building with Jetpack Compose for a while, you know how tempting it is to just pass a  ViewModel  instance down through five layers of UI components. It’s convenient—one object gives you all the data and all the functions you need. But here is the architectural reality:  Passing ViewModel instances deep into your UI tree is an architectural anti-pattern.  It couples your visual components to business logic and makes your code significantly harder to maintain, test, and preview. The Core Problem: Lifecycle and Scoping ViewModels are designed to be state holders tied to a specific lifecycle (usually a Navigation Destination). When you pass a ViewModel into a small UI component, you break the  Unidirectional Data Flow (UDF) . ❌ The “Bad” Way (Tight Coupling) // ❌ BAD: This component is now impossible to preview or reuse @Composabl...
Read more

Is Jetpack Compose Making Your APK Fatter? (And How to Fix It)

Image
 Unpacking the Compose Tax, compiler-driven DEX optimization, and why your resource strategy must evolve for modern UI. TL;DR DEX Bloat:  Compose’s compiler injects “Restartable” and “Skippable” logic for memoization; R8 minification is effectively required. Code vs. Assets:  Moving iconography to  ImageVector  constants allows R8 to prune unused assets as code. Tooling Leak:   ui-tooling  in release builds is the #1 cause of "false" bloat. The Scale Factor:  Compose has a higher “size floor” but a much lower “size ceiling” than the legacy View system. The promise of Jetpack Compose was simple: “Write less code, ship faster.” But as teams migrate, a quiet concern often echoes in code reviews:  “Why did our APK size just jump?” While Compose removes the weight of deep XML hierarchies and the overhead of ViewBinding, it introduces a unique “Compose Tax.” For a senior engineer, the goal isn’t just to accept this tax, but to optimize the runtime...
Read more