Guide · Engineering

Build for the network Syria actually has.

If your app assumes a stable connection and a charged battery, it will not survive in Syria. Here is how we design apps that keep working through dead spots and power cuts, and sync when they come back.

Updated 15 November 2026Reviewed by Eng. Hasan Kassas

The short answer

Make the phone the source of truth. The app reads and writes to a local database first, queues every change, and syncs with the server whenever the network allows. Keep every download small, treat the battery as a resource, and tell the user plainly which features work offline and which need a connection.

We build this way because our products run on Syrian networks every day. An app designed for a slow, intermittent connection feels instant on a fast one; the reverse is never true.

Our four rules

The rules we build by

01
Offline-first is the architecture

A local database is the source of truth. The server is where changes meet, not where the app waits. Conflict rules are decided up front, not after the first support ticket.

02
Payload budgets, enforced

We set budgets for first load, API responses and images, and the build fails when one is broken. A budget nobody enforces is a wish.

03
Battery is a resource

No polling loops. Sync in batches, push instead of pull, and do heavy background work when the phone is charging and on Wi-Fi.

04
Degrade by feature, not by failure

Decide which features work offline, which wait in a queue and which honestly need a connection, and show the user which mode they're in. Silent failure is the one unacceptable state.

How to do it

Building an offline-first app, step by step

  1. Write the offline matrix first

    List every feature and mark it: works offline, queues until online, or needs the network. For a marketplace, browsing saved results and drafting a listing work offline; publishing queues; payment needs the network.

  2. Put a local database under the UI

    Screens read from the device, never straight from the network. New data from the server updates the local store, and the screen updates from there.

  3. Queue every write

    Each change goes into an outbox with a unique ID, so retrying after a dropped connection can never create a duplicate order or listing.

  4. Retry with backoff

    When a sync fails, wait a little longer before each retry instead of hammering a weak network, and resume as soon as the connection returns.

  5. Decide conflict rules

    When the same record changed on the phone and on the server, decide in advance who wins, field by field. Most conflicts have an obvious business rule once you write it down.

  6. Shrink every download

    Paginate lists, send only what changed, serve images in modern formats at the size they are displayed, and cache what does not change.

  7. Test on the real network

    Throttle the connection, switch to airplane mode mid-action and kill the app during a sync. The bugs that matter only show up there.

FAQ

Common questions

The app works from data stored on the phone and treats the network as something that comes and goes. Changes are saved locally first and synced to the server when a connection is available.

Building for real Syrian networks?

Tell us what your app needs to do offline. We'll tell you what is possible and what it takes.