Mobile App for Library: Catalog, Search, Offline

Library App Challenges: The Catalog Is Just the Tip of the Iceberg

Integrating a library mobile app with existing infrastructure is a quiet nightmare for many teams. It seems like just a book catalog and offline book search, but reality is: MARC21, Z39.50, OPDS integration with invalid XML, or even IRBIS-64 with a socket-based API. With 5+ years of experience and 50+ successful projects, we have developed an approach that prevents getting stuck at the data connection stage, saving up to 30% of the budget. For example, a basic library app starts at $8,000, while a full-featured solution with offline mode and scanner is from $15,000. Average project cost ranges from $8,000 to $25,000.

Why Is Integration with Library Systems a Challenge?

Most libraries use standardized data formats (MARC21, OPDS, Z39.50), but not all provide a modern REST API. For example, IRBIS-64 often works via TCP sockets — direct connection from a mobile device is impossible; a server adapter is needed. Even OPDS feeds can be broken: invalid XML, missing mandatory fields. Without a detailed audit of the existing infrastructure, the project risks stalling at the data connection stage.

How We Solve Compatibility Issues

If the library uses a modern system, it likely has an OPDS feed (Open Publication Distribution System). This is an Atom/XML API for catalogs. We parse it using XMLParsing (Swift) or kotlinx.serialization with a custom XML deserializer (Android).

If OPDS is not available, we either negotiate a REST API with the IT department or build our own backend proxy on top of the existing system. Z39.50 over the internet without an intermediary from a mobile device is practically impossible — a server adapter is needed. For small libraries without an external system, we build a custom backend (Laravel/Node) with manual catalog entry via CMS.

Comparison of Integration Approaches

Choosing the right approach at the start saves project budget.

Local Database — The Key to Offline Work

Book catalog is cached locally: Room (Android) / Core Data (iOS). Key entities:

@Entity data class Book(
    @PrimaryKey val isbn: String,
    val title: String,
    val author: String,
    val year: Int,
    val genre: String,
    val coverUrl: String?,
    val availableCopies: Int,
    val totalCopies: Int
)

@Entity data class Reservation(
    @PrimaryKey(autoGenerate = true) val id: Long = 0,
    val bookIsbn: String,
    val userId: String,
    val status: String, // ACTIVE, COMPLETED, CANCELLED
    val dueDate: Long
)

FTS (Full-Text Search) via Room @Fts4 for searching by title and author without network requests:

@Fts4(contentEntity = Book::class)
@Entity(tableName = "book_fts")
data class BookFts(val title: String, val author: String)

Search works instantly offline — important for reading rooms with poor WiFi. We guarantee local search is 10x faster than any network request.

Key Features and Implementation

Catalog with Filters

LazyColumn (Compose) / UICollectionView with Diffable Data Source. Filters: genre, year, availability, language. Filtering via Room queries with dynamic conditions or @Query with nullable parameters.

Personal Account and Membership

Login via library card number + password or via QR code of the card. After login — current books on hand, history, debts, reservations. Push notifications 3 days before due date (via FCM / APNs). Background sync via Background fetch and WorkManager.

Barcode / QR Scanning

Scan ISBN for quick book search — via MLKit Barcode Scanner (Android) or Vision framework (iOS). Scan library card — QR Code via the same libraries.

E-books

If the library provides electronic resources — integration with partner programs or custom EPUB/PDF reader. EPUB rendering via Readium (iOS/Android) — open standard with DRM support.

How Integration Works: Step by Step

1. Analysis — audit of library system, identification of available APIs and data formats. (1-2 days)
2. Design — selection of optimal integration method, app architecture design. (1-2 days)
3. Implementation — development of backend proxy (if needed) and mobile client. (2-4 weeks for MVP)
4. Testing — integration verification, load testing, bug fixes. (1 week)
5. Deployment — release to App Store and Google Play, push certificate setup (APNs, FCM). (1 week)

Feature Performance Comparison

What's Included

• Analysis of existing library system and integration method selection
• OPDS parser or REST API integration
• Local catalog with FTS search
• Personal account: membership, history, reservations
• Push notifications for due dates
• ISBN/QR scanner
• Offline mode with sync

Timelines

MVP with catalog, search, and personal account: 4–6 weeks. Full-featured app with offline mode, push, scanner, and integration with existing library system: 8–12 weeks. Cost is calculated individually after API audit. Average project cost ranges from $8,000 to $25,000.

Contact us for a free consultation — get an assessment of your library system and integration recommendations. We will select the optimal implementation option.

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.