Use this site offline, Progressive Web App architecture, and emergency device preparation¶
During catastrophic hurricanes, severe winter storms, major earthquakes, or widespread power grid blackouts, telecommunications infrastructure is frequently severed within hours. Cell towers lose commercial grid power, backup diesel generator fuel lines fail, and underground fiber optic lines are severed by falling trees or landslides. In an acute crisis, the internet connection you normally rely on to look up critical survival instructions can disappear entirely.
Emergency Guide is engineered from the ground up as a Progressive Web App (PWA) with complete offline operational independence. The entire library of hundreds of emergency manuals, first aid protocols, search capabilities, and interactive checklists can be stored permanently inside your device storage.
This guide provides technical instructions for saving the site on your smartphone, tablet, or laptop, details the underlying service worker caching mechanics, and outlines essential device power management techniques during grid collapse.
Interactive offline installation status¶
Use the status indicators below to confirm whether the complete guide is cached in your browser storage or to install the application directly onto your operating system.
Checking whether this guide is saved on your device.
How offline caching operates in your browser¶
Unlike conventional websites that require continuous server round-trips for every link clicked, Emergency Guide uses client-side web technologies designed for disconnected operations.
+---------------------------------------------------------------------------------+
| PROGRESSIVE WEB APP CACHING PIPELINE |
+---------------------------------------------------------------------------------+
| 1. SERVICE WORKER REGISTRATION (BACKGROUND THREAD) |
| - When you visit any page on emergency.guide over a secure HTTPS connection, |
| the browser registers a background JavaScript service worker daemon. |
| - This thread operates independently of web page rendering tabs. |
+---------------------------------------------------------------------------------+
| 2. STALE-WHILE-REVALIDATE CACHING ARCHITECTURE |
| - Online Mode: Requests return the cached asset immediately for instant |
| sub-millisecond load times, while querying the server in the background to |
| update changed guides transparently. |
| - Disconnected Mode: When no network connection is detected, the service |
| worker intercepts the network request and serves the pristine page from |
| the browser CacheStorage API. |
+---------------------------------------------------------------------------------+
| 3. IN-MEMORY CLIENT-SIDE SEARCH ENGINE |
| - The search bar does not send search terms to a remote server database. |
| - A pre-compiled index file containing all guide headings, keywords, and |
| synonyms is cached locally on your device. Searching executes in real time |
| even when your phone is in airplane mode. |
+---------------------------------------------------------------------------------+
| 4. LOCAL STORAGE ISOLATION (ZERO NETWORK TELEMETRY) |
| - Interactive checklist checkboxes (such as go-bag gear and pet supplies) |
| persist their checked status in browser localStorage. |
| - Your checklist data remains strictly private on your physical device and |
| is never transmitted across the network. |
+---------------------------------------------------------------------------------+
Service worker lifecycle and update verification¶
The service worker operating behind Emergency Guide functions as a client-side programmable proxy. Understanding its operational states ensures predictable performance:
Service Worker Lifecycle States:
=============================================================================
1. REGISTRATION AND PARSING:
- Upon initial navigation, the browser downloads the service worker script
from `/sw.js`. The browser parses the script and executes global code.
2. INSTALLATION (ASSET PRE-CACHING):
- The `install` event triggers the immediate pre-fetching of essential core
runtime files: HTML templates, CSS style sheets, JavaScript bundles,
search indexes, and vector icon fonts.
- All critical assets are written atomically into a versioned CacheStorage
container. If any single asset fails to download, the entire installation
aborts, ensuring corrupt or partial caches are never activated.
3. ACTIVATION AND CACHE PRUNING:
- Once installed, the `activate` event fires. The new service worker iterates
through existing CacheStorage keys and automatically purges deprecated
caches from previous site deployments, freeing local device disk space.
4. BYTE-FOR-BYTE SCRIPT UPDATE CHECK:
- Every time you open any guide while connected to the internet, the browser
checks the server for a newer version of `/sw.js`. If the server returns a
script that differs by even one single byte, the browser downloads the new
worker in the background.
- When a newly deployed version is fully cached, an unobtrusive update banner
appears at the top of the interface, allowing you to reload and adopt the
latest emergency guidance with a single tap.
=============================================================================
Operating system installation instructions¶
Installing Emergency Guide as a standalone web application places a dedicated icon on your device home screen, launches the guide in a borderless full-screen window without browser address bars, and prevents accidental cache eviction by operating system memory managers.
Apple iOS and iPadOS (Safari)¶
Apple iOS imposes unique privacy rules that require users to install PWAs to the home screen to ensure persistent offline storage.
iOS / iPadOS Safari Installation Protocol:
=============================================================================
1. LAUNCH IN NATIVE SAFARI:
- Open Safari and navigate to emergency.guide. (Note: Third-party browsers
on iOS like Chrome or Firefox operate under WebKit restrictions and
cannot install native home screen PWAs).
2. ACTIVATE THE SHARE SHEET:
- Tap the Share button (the square icon with an upward-pointing arrow)
located in the center of the bottom navigation toolbar on iPhone, or at
the top right on iPad.
3. SELECT "ADD TO HOME SCREEN":
- Scroll down through the vertical menu options and tap "Add to Home Screen".
4. CONFIRM APPLICATION TITLE:
- Tap "Add" in the upper right corner.
5. VERIFY INDEPENDENT LAUNCH:
- Close Safari and locate the Emergency Guide icon on your home screen.
- Tap the icon to launch. The app opens full screen without browser toolbars.
=============================================================================
Google Android (Chrome and Chromium browsers)¶
Android devices support direct Web App Manifest installation with automatic background sync.
Android Chrome Installation Protocol:
=============================================================================
1. LAUNCH IN CHROME OR BROWSER OF CHOICE:
- Navigate to emergency.guide in Google Chrome, Samsung Internet, or Brave.
2. USE THE INSTALL BUTTON OR BROWSER MENU:
- Tap the "Install this guide as an app" button displayed near the top of
this page, or tap the three vertical dots in the browser top-right corner.
3. SELECT "INSTALL APP" OR "ADD TO HOME SCREEN":
- Tap "Install app" (or "Add to Home screen").
- Confirm by tapping "Install" on the system confirmation dialog.
4. CONFIRMATION:
- The operating system adds the Emergency Guide application icon to your
app drawer and home screen launcher.
=============================================================================
Windows, macOS, and Linux desktop computers¶
Emergency Guide installs as a lightweight, native desktop application on desktop operating systems using Google Chrome, Microsoft Edge, or Chromium.
- Open
emergency.guidein Chrome or Edge. - Look at the right side of the URL address bar at the top of the browser window. Click the "Install Emergency Guide" icon (represented by an open computer monitor or computer screen with a down arrow).
- Alternatively, click the browser settings menu (three dots) and select "Save and share" followed by "Install Emergency Guide".
- Click "Install". The application immediately launches in a dedicated, isolated application window and creates a shortcut on your desktop, taskbar, or macOS Applications folder.
Critical storage eviction risks and prevention¶
Operating systems manage storage aggressively when internal memory is constrained. Understanding how mobile browsers handle cached data prevents losing your offline guides during a crisis.
+------------------------------------+--------------------------------------------+
| OPERATING SYSTEM / BROWSER | CACHE EVICTION POLICY AND REMEDY |
+------------------------------------+--------------------------------------------+
| Apple iOS WebKit (Safari Tabs) | 7-DAY EXPIRATION WINDOW |
| | Safari automatically deletes website local |
| | storage and caches if a site is not visited|
| | within seven calendar days. |
| | REMEDY: Installing to Home Screen bypasses |
| | the 7-day rule, granting persistent space. |
+------------------------------------+--------------------------------------------+
| Google Android (Chrome) | DYNAMIC STORAGE QUOTA |
| | Allots up to 60 percent of free disk space |
| | for web caches, but may purge data during |
| | severe device storage warnings. |
| | REMEDY: Keep at least 1 GB of free device |
| | internal storage clear of clutter. |
+------------------------------------+--------------------------------------------+
| Private / Incognito Browsing | EPHEMERAL IN-MEMORY CACHING |
| (All Platforms) | Private browsing sessions purge all caches,|
| | cookies, and service workers immediately |
| | upon closing the browser tab. |
| | REMEDY: Never use incognito mode when |
| | preparing offline emergency materials. |
+------------------------------------+--------------------------------------------+
Power conservation and hardware readiness during blackouts¶
Having offline guides stored on a smartphone is useless if your device battery drains to zero percent during the first twelve hours of an extended electrical outage. Implement strict hardware power conservation protocols.
Emergency Smartphone Battery Preservation Sequence:
=============================================================================
1. ENGAGE AIRPLANE MODE DURING TOWER OUTAGES:
- When cellular towers lose power, smartphones continuously transmit at
maximum radio frequency power (up to 2 watts) searching for cellular
base stations. This radio hunting drains a full battery in 3 to 5 hours.
- Switch your device to Airplane Mode. The cached Emergency Guide remains
fully readable and searchable in airplane mode because all data is stored
locally on your flash storage.
2. ACTIVATE EXTREME BATTERY SAVER MODE:
- Enable "Low Power Mode" on iOS or "Extreme Battery Saver" on Android.
- These profiles reduce CPU clock frequencies, suspend background app
refreshes, throttle animation refresh rates, and disable mail fetching.
3. OPTIMIZE DISPLAY SETTINGS (OLED BLACK THEME):
- Modern smartphone displays use Organic Light Emitting Diode (OLED)
technology where black pixels are completely powered off.
- Switch Emergency Guide and your operating system to dark mode.
- Reduce screen brightness to 20 to 30 percent. A dim display consumes
up to 75 percent less power than maximum brightness.
- Set screen auto-lock timeout to 30 seconds.
4. PRE-STAGE HARDWARE POWER RESERVES:
- Keep a minimum of two 20,000 mAh external lithium power banks fully
charged in your emergency supply kit. A 20,000 mAh pack recharges an
average smartphone 4 to 5 times.
- Store power banks at room temperature. Extreme cold below 0 degrees
Celsius (32 degrees Fahrenheit) reduces lithium-ion battery capacity
by 30 to 50 percent.
- Acquire a portable 15 to 28 watt folding monocrystalline solar panel
with direct USB charging ports for extended multi-week grid failures.
=============================================================================
Generating physical hard-copy paper backups¶
Digital storage is resilient, but electronic devices can suffer catastrophic physical trauma: salt water flooding during storm surges, screen breakage from impact, or complete battery exhaustion. Always maintain printed paper documentation for high-priority emergency scenarios.
Physical Paper Backup Checklist:
=============================================================================
1. HIGH-PRIORITY PRINT LIST:
- Emergency Numbers by Country (resources/emergency-numbers.md).
- Cardiopulmonary Resuscitation CPR Protocol (../first-aid/cpr.md).
- Choking Heimlich Maneuver Protocol (../first-aid/choking.md).
- Severe Bleeding and Tourniquet Application (../first-aid/bleeding.md).
- Family Emergency and Evacuation Plan (../prepare/family-plan.md).
- Emergency Go-Bag and Water Safety Checklists.
2. PRINTING PROTOCOL:
- Open the target guide in any desktop or mobile browser.
- Press Ctrl + P (or Command + P on macOS) to open the print dialog.
- The website stylesheet automatically formats the page for physical paper,
stripping away navigation menus, search bars, and dark backgrounds to
conserve printer ink.
- Select "Save as PDF" to generate a portable electronic document that can
be stored on USB flash drives or shared across offline devices.
3. WEATHERPROOFING AND STORAGE:
- Place printed documents inside heavy-duty, sealable plastic freezer bags.
- For ultimate durability, laminate vital medical and emergency contact
cards using clear thermal laminating pouches.
- Store one full hard-copy set inside your home waterproof safe and an
identical set inside your primary vehicle glove compartment.
=============================================================================
Troubleshooting offline access issues¶
If you attempt to access Emergency Guide without an internet connection and the site fails to load, execute these troubleshooting steps:
- Verify Home Screen Launch: Ensure you are launching the application from the home screen icon or app drawer shortcut rather than typing URLs into an incognito browser window.
- Check Available Disk Space: If your device has less than 200 MB of free storage, mobile operating systems purge browser caches automatically. Clear unnecessary video files or cached media in your phone storage settings and reopen the app while connected to Wi-Fi to re-cache the guide.
- Manual Cache Refresh: Open the website while connected to a stable internet connection. Allow the home page to remain open for 15 to 30 seconds. Look at the offline status bar near the top of this page; when it confirms the guide is saved, the updated service worker has completed its background asset caching.
- Avoid Clearing Browser Data: Be aware that running third-party "phone cleaner" apps or selecting "Clear History and Website Data" in browser settings will delete cached offline guides. If you clean your browser data, open Emergency Guide once while online to rebuild your offline archive.