Skip to content
lifelink

lifelink

When Networks Fail, Communication Shouldn’t

Created on 13th September 2025

lifelink

lifelink

When Networks Fail, Communication Shouldn’t

The problem lifelink solves

No Internet, No Help – most SOS apps stop working offline.

Wasted Time – emergencies need instant alerts, not delays.

No Backup Route – messages can’t hop through nearby devices.

Lives at Risk – when every second counts, help never arrives.

Challenges we ran into

⚡ Challenges I Ran Into

  1. Offline Message Forwarding

    • Hurdle: Implementing reliable Bluetooth/Wi-Fi Direct communication was tricky, as devices often disconnected or required manual pairing.
    • Solution: Added a fallback mechanism and auto-retry logic so messages would keep attempting until one device with internet was found.
  2. Permission Management

    • Hurdle: Android required multiple runtime permissions (Location, Bluetooth, Internet), and forgetting one caused crashes.
    • Solution: Implemented a centralized permission manager to request and check all required permissions at once.
  3. Data Packaging

    • Hurdle: Combining profile info, GPS, battery %, and timestamp into a single SOS payload without errors.
    • Solution: Created a structured JSON model so data is always consistent and easy to send.
  4. UI Simplicity vs. Features

    • Hurdle: Balancing a minimal interface with critical emergency details.
    • Solution: Designed a clean main screen with a single large SOS button and moved extra settings into the Profile page.

Discussion

Builders also viewed

See more projects on Devfolio