Implementing Data Export (CSV, Excel) from Mobile Apps

User taps "Export" — and waits. If there are 5000 rows in a local SQLite or Room database, and export runs on the main thread, the app freezes for seconds, and on older devices an ANR (Application Not Responding) is almost guaranteed. This is the first and most common mistake when implementing export. In our practice, we encounter such situations constantly and have developed a reliable approach that guarantees stable operation even on devices with 2 GB of RAM.

Our engineers with seven years of mobile development experience have delivered over 50 projects involving data export. Each project was tested on real data volumes up to 500,000 rows. For example, on a logistics app with 500,000 transaction records, we reduced export time from 15 seconds to 2.1 seconds by using batched writes on a background thread. Contact us — we'll review your architecture in 30 minutes.

Problems we solve in practice

UI freeze during file generation. Serializing 10,000 rows to CSV is not instant. On Android, use CoroutineScope(Dispatchers.IO), on iOS DispatchQueue.global(qos: .userInitiated). We always move file generation to a background thread and return the result via callback or Flow.

Encoding and delimiter. CSV is a trap. Excel on Windows expects Windows-1252 encoding and semicolon ; as delimiter, not a comma. If you deliver UTF-8 without BOM, Cyrillic becomes garbled in the client's office. The correct CSV for Excel: UTF-8 with BOM (\uFEFF) and semicolon delimiter. Or export directly as .xlsx using a library.

Export to Excel (.xlsx). On Android we use Apache POI or the lighter FastExcel. On iOS — xlsxwriter via Swift Package or a custom XML generator (.xlsx is a ZIP of XML files). React Native apps can use react-native-xlsx over the js xlsx library.

How we build the export

The scheme is simple: read data from local DB → transform into row model → write to file → share via system ShareSheet / Intent.ACTION_SEND.

On Android with Room:

viewModelScope.launch(Dispatchers.IO) {
    val rows = database.transactionDao().getAll()
    val file = CsvExporter.export(rows, context.cacheDir)
    withContext(Dispatchers.Main) {
        shareFile(file, "text/csv")
    }
}

On iOS similarly via Task.detached:

Task.detached(priority: .userInitiated) {
    let rows = await store.fetchAll()
    let url = try CsvExporter.write(rows, to: .cachesDirectory)
    await MainActor.run { presentShareSheet(url) }
}

For .xlsx on iOS, we generate XML structure manually or via CoreXLSX / xlsxwriter. For simple tables, the XML approach is faster and dependency-free.

Progress for large volumes

If rows exceed 50,000, we show a ProgressView with real percentage. On Android via StateFlow<Int> in ViewModel, on iOS via @Published var progress: Double. We write the file in batches of 1000 rows and update the counter after each batch.

File format and sharing

After generation, we place the file in cacheDir (Android) or FileManager.default.temporaryDirectory (iOS). We share via:

• Android: FileProvider + Intent.ACTION_SEND with correct MIME type (text/csv or application/vnd.openxmlformats-officedocument.spreadsheetml.sheet)
• iOS: UIActivityViewController with [fileURL]

We never save to Downloads without explicit user request — that violates both platform guidelines.

Why background thread export is critical

Any I/O and serialization work must be off the main thread. In practice, this reduces app response time by 5–10 times for exports starting at 10,000 rows. Our engineers verify this on every project.

How to correctly display Cyrillic in CSV for Excel

Use UTF-8 with BOM and semicolon as delimiter. Alternatively, export to .xlsx where encoding is not an issue. We have experience adapting exports for local markets including Cyrillic and Asian characters.

Step-by-step export implementation

1. Choose format (CSV or XLSX) and agree on column structure.
2. Read data from DB on a background thread.
3. Generate file with correct encoding and delimiters.
4. Show progress for large volumes.
5. Share via system dialog.

What's included in the work

• Format selection (CSV / XLSX) and column structure agreement
• Background file generation without UI blocking
• Correct encoding and localized delimiters
• Progress indicator for large exports
• System ShareSheet / Intent sharing
• Testing on real data volumes

Timelines

Simple CSV export from an existing database: 0.5–1 day. With format selection (CSV/XLSX), date range filters, and progress: 1.5–2 days. Cost is determined after data structure analysis — we'll assess your project for free. Contact us to discuss your task and get a consultation on format selection and work scope.

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.