الإحرام

## The Connectivity Crisis

When two million people are concentrated within a few square kilometers, cellular infrastructure cannot cope. Network speeds drop to near-zero. This is the daily reality during الحج.

## Our Architectural Decision

الإحرامOS was designed offline-first from day one. Online connectivity enhances the experience but is never required for essential functions.

## The SQLite Foundation

All content is stored locally using Drizzle ORM. During pre-trip setup over WiFi, the app downloads ritual guidance, دعاء library with audio, offline map tiles, and الصلاة time data.

## What Works Offline

All ritual guidance, دعاء library with audio, الطواف and السعي counters, الصلاة times, القبلة compass, الطوارئ contacts, SOS with SMS queuing, medical card, journal, and settings.

## The Sync-When-Available Strategy

Local writes are queued and synced when connectivity appears. Critical data like SOS alerts are prioritized. Sync uses last-write-wins for user data.

## Pre-Trip Content Download

A clear checklist of content packages, progress tracking, integrity verification, and resume capability. Download over hotel WiFi in your first day in المملكة العربية السعودية.

## The Technical Challenge

Every feature must work without server communication. Data schemas avoid server-side processing. Audio is compressed for size. Map tiles are optimized for specific areas. These constraints shaped every architectural decision.