CMS Development for Mobile App Content

CMS Development for Mobile App Content

A marketer wants to change a promotional banner, update prices, or add a new product category. In an app with hardcoded content, this means building a release, reviewing in App Store and Google Play — 24-72 hours of waiting. Users see outdated data. We solve this with a Headless CMS, which moves editable content outside the app. Now changes are published in minutes, without updating the app. Our experience: 50+ projects where this architecture reduced content publishing time by 10x compared to the release cycle.

What CMS Architecture to Choose for a Mobile App?

Headless CMS — delivers content via API, the mobile client renders itself. Contentful, Strapi, Directus, Sanity. Backend + Admin Panel — custom CMS on your own backend (Laravel Nova, React SPA) with full control over structure. Firebase Remote Config — only for flags and simple configs, not for content with images. Contentful reduces content load time by 2x compared to a custom panel thanks to built-in CDN. At 100K DAU, traffic savings can reach $2000 per month.

Rule of thumb: if content changes less than once a quarter — leave it in code. If frequent — use CMS. For a quick start, Contentful works; for long-term flexibility, choose Strapi or custom.

How to Implement Caching with ETag?

A typical mistake is loading all content every time the screen is opened. At 100K DAU and 50 loads per day, this consumes hundreds of gigabytes of traffic. Solution — ETag: the server computes a hash of content, the client sends it in If-None-Match. If content hasn't changed, the server responds with 304 without body.

class CmsRepository(
    private val api: CmsApi,
    private val dao: CmsContentDao,
    private val prefs: CmsPreferences
) {
    fun observeHomeScreen(): Flow<HomeScreenContent> = flow {
        // From cache first
        val cached = dao.getHomeScreen()
        if (cached != null) emit(cached.toContent())

        // Check for update
        try {
            val response = api.getHomeScreen(
                ifNoneMatch = prefs.homeScreenEtag
            )
            if (response.code() == 304) return@flow // cache is fresh

            val fresh = response.body()!!
            dao.upsertHomeScreen(fresh.toEntity())
            prefs.homeScreenEtag = response.headers()["ETag"]
            emit(fresh)
        } catch (e: IOException) {
            // Network unavailable — cache already served
        }
    }
}

On the client, we store cache in a local database (Room on Android, CoreData on iOS). First serve from cache, then check for fresh version. This gives instant response and saves bandwidth. In one project, this approach reduced server load by 70%, saving $3000 per year on hosting.

What Is Managed Through CMS?

Not all content should be externalized. If it changes less than once a quarter, keep it in code. Typically we externalize:

• Banners and promo blocks on the home screen
• Onboarding and splash content
• Push notification texts and in-app messages
• Product/service catalog (if not from ERP)
• Static pages (FAQ, terms, contacts)
• Feature flag settings
• Localized content (different texts for regions)

Typical Mistakes When Implementing CMS

Let's look at three common problems with approaches to solutions.

ETag caching is 2x faster than versioning for update checks and reduces network traffic by 70%.

CMS Implementation Process

Based on five years of experience (50+ mobile CMS projects), the stages are:

1. Analysis — determine dynamic content, design data structure.
2. API contract design — JSON schema for all screens.
3. Platform selection — Strapi / Contentful / custom.
4. Implementation — configure CMS, write API endpoints, admin panel.
5. Integration with mobile client — caching, updates, error handling.
6. Testing — correct operation offline and under load.
7. Deployment — CI/CD for CMS, CDN for images.

What Is Included in the Work

• Headless CMS development (Strapi / custom) with API contracts for your screens
• Client library with ETag caching (iOS / Android)
• Admin UI for content editing
• Localization and feature flags setup
• API documentation and data schema
• Test and production environments
• One month of support after launch

Timelines: 3 to 6 weeks, depending on complexity. Pricing is tailored individually. We guarantee content updates in minutes, without extra releases.

Contact us to estimate your project and get a consultation — we will help you choose the architecture and design the API contract.

How to Choose a Local Data Storage Solution (Room, Core Data, Realm, Isar)?

We've all seen the scenario: the app loses data when the network drops — and it's not just a bug, it's a failure of the use case. The user fills out a form, taps "Submit", gets a timeout, and loses everything. Or worse: data gets sent twice due to incorrect retry logic. A properly chosen and configured storage layer solves this problem once and for all. The wrong choice can cost teams months of rewriting code and up to 70% of time spent on synchronization. Our experience — 10+ years in mobile development, over 50 projects with offline storage — confirms: the storage choice determines 80% of future performance and synchronization issues.

In practice, storage selection is driven by two factors: data type and synchronization requirements, not library popularity.

Room (Android) — a wrapper over SQLite with compile-time verification of SQL queries. If a query is invalid, the build fails — better than a SQLiteException at runtime. Room integrates well with Kotlin Flow and LiveData, making reactive UI updates straightforward. The main challenge is schema migrations. @Database(version = N, exportSchema = true) with migration files in assets/databases/ is mandatory; otherwise, fallbackToDestructiveMigration() will simply delete the user's data on app update.

Core Data (iOS) — not a database, but an object graph management framework over SQLite (or XML, or in-memory). NSPersistentContainer with viewContext for reading on the main thread and newBackgroundContext() for writing is the basic setup. The trouble begins when a developer calls save() on viewContext from a background thread: EXC_BAD_ACCESS at a random moment, happens once a week, with almost nothing useful in the crash log. You must use performAndWait or perform for each context strictly on its own thread. Apple Core Data Programming Guide recommends this approach.

Realm wins where you need speed with large object sets and built-in reactivity through Results + observe(). Realm stores objects directly without ORM mapping, so reads require no deserialization. According to our measurements, Realm processes reads 2–3 times faster than Core Data for volumes over 10,000 objects. On Flutter, the Realm SDK (ex-MongoDB Realm) supports Device Sync — but that's a managed service with separate infrastructure.

Hive and Isar are Flutter-specific solutions. Hive is a key-value store, fast, simple, suitable for settings and caches. Isar is a full document-oriented database with indexes, written in Rust, compiled to native code. For Flutter apps with offline functionality, Isar is now preferred: built-in query builder with type-safe filters, transactions, watchObject/watchQuery for reactivity.

Contact us for a free audit of your current storage and optimization recommendations — this will save you hundreds of development hours and up to 60% of server request traffic.

Why Is Offline Synchronization the Hardest Part?

Local storage itself is not complicated. The complexity lies in synchronizing with the server in the presence of conflicts.

The most common pattern is optimistic updates with rollback. The user edits a record, the UI reflects the change instantly, a background request goes to the server. If the server returns an error, we roll back the local state. Sounds simple. In practice: if the user has left the screen and returned before the rollback (which may take 3 seconds), the UX is broken. You need an explicit operation queue with states (PENDING, SYNCED, FAILED) in a separate table.

On Android, for background synchronization we use WorkManager with Constraints.Builder().setRequiredNetworkType(NetworkType.CONNECTED). Don't forget setInputMerger(ArrayCreatingInputMerger::class) when batching tasks — otherwise, concurrent runs will overwrite data. A typical operation queue implementation:

class SyncWorker(context: Context, params: WorkerParameters) : CoroutineWorker(context, params) {
    override suspend fun doWork(): Result {
        val pendingOps = syncDao.getPendingOperations()
        for (op in pendingOps) {
            try {
                apiClient.send(op.payload)
                syncDao.markSynced(op.id)
            } catch (e: Exception) {
                syncDao.markFailed(op.id, e.message)
                return Result.retry()
            }
        }
        return Result.success()
    }
}

On iOS, the equivalent is BGTaskScheduler with BGProcessingTaskRequest. iOS limitations on background execution time (~30 seconds for refresh tasks) mean that synchronization must be incremental: not "sync everything," but "sync the next N records, save the cursor."

Conflicts in multi-device scenarios are resolved with one of three approaches:

• Last-write-wins based on updated_at (simplest, loses data on concurrent edits)
• Server-wins (client always accepts server version)
• Three-way merge (complex, requires a common ancestor — suitable for documents)

For most B2C apps, last-write-wins with a user-level time vector is sufficient, but for collaborative editing, a CRDTs approach is needed — then look at Automerge or Yjs with mobile bindings.

How We Build the Storage Layer

The repository pattern is not optional — it's mandatory. UserRepository doesn't know where the data comes from: Room, Realm, or network. The ViewModel calls repository.getUser(id), gets a Flow/Stream, and displays data. Caching logic resides inside the repository.

For Flutter, a typical architecture: Isar for persistence, Riverpod for state management, ConnectivityPlus for network status, and a custom SyncService with an operation queue. Riverpod's AsyncNotifier conveniently covers the logic of "show cache, update from network, show new data." Example repository with caching:

class UserRepository {
  final Isar isar;
  final ApiClient api;

  Future<User> getUser(String id) async {
    // try from local storage first
    final cached = await isar.user.where().idEqualTo(id).findFirst();
    if (cached != null) return cached;
    // otherwise from network
    final remote = await api.fetchUser(id);
    // save locally
    await isar.writeTxn(() => isar.user.put(remote));
    return remote;
  }
}

Another important topic is encryption. If the app stores medical data, payment cards, or corporate documents, SQLCipher (Android) and NSFileProtection (iOS) are not optional. Realm supports encryption natively via a 64-byte key that must be stored in Keychain/Keystore, not in SharedPreferences. Skimping on security can lead to data leaks with serious consequences.

What the Work Includes

We guarantee a transparent process and document each stage:

Want to avoid common mistakes when designing storage? Contact us — we'll help design a reliable local storage from scratch or improve an existing one.

Stages of Work

We start with a requirements audit: what data, what volume, is synchronization needed, are conflicts possible. At this stage, it becomes clear whether Core Data or an SQLite-based solution is needed, whether Realm Sync is required or simple REST polling will suffice.

Next, we design the schema with migrations in mind. Schemas change in any project — the question is not "will there be migrations," but "how painful will they be." We export the schema as JSON, store it in the repository, and write tests for each version's migration.

Development includes unit test coverage for the repository layer: network layer mocks, a real in-memory database for query testing. Before release, we profile queries using Android Profiler (Database Inspector tab) or Core Data debug flags (-com.apple.CoreData.SQLDebug 1).

The implementation timeline for a storage layer with basic offline synchronization ranges from 2 to 6 weeks, depending on schema complexity and conflict resolution requirements. Contact us to get a consultation on choosing the optimal stack and migrations.