BEACON

Inspiration

The current 911 system suffers from several institutional deficiencies: a voice-dominated system (911 relies heavily on real-time verbal communication), language barriers (the system primarily operates in English, disadvantaging non-native speakers or people who do not converse in English at all), inconsistent Phase II geolocation data transmission to PSAPs and dispatchers, over-dependence on user-provided location data, lack of access to crucial ambient, background sound, and limitations of the current Text-to-911 systems.

Real-world scenarios highlight this gap: i. A person injured and immobile in a remote area with little to no knowledge of their exact location. ii. Someone is hiding silently during a home invasion. iii. A passenger in a cab feels unsafe but is unable to alert authorities discreetly._ iv. A non-English speaker struggling to communicate with dispatchers.

These situations expose systemic deficiencies: --> Voice dependency excludes silent or unsafe-to-speak scenarios. --> Language barriers delay or distort communication. --> Inconsistent geolocation transmission hinders response accuracy. --> Lack of contextual/audio evidence limits situational awareness.

Core insight: Emergency systems should adapt to the user’s limitations; not the other way around

What it does

BEACON is a mobile emergency app that enables silent, multilingual, and structured communication with 911. It sends translated responses, real-time GPS data, and optional audio recordings to help responders act faster and more accurately.

Core Functionality:

= Multilingual Input Interface: Users provide information through guided questions (standard form) or custom responses in their preferred language, i.e., English, Spanish, Chinese (Mandarin and Cantonese), Haitian, Tagalog, Vietnamese, Arabic, Korean, Portuguese, and French.

= Automatic Translation: All inputs are translated into U.S. English for dispatchers using a local translation tool.

= Precise Geolocation Capture: The system automatically retrieves GPS-based location data from the user’s device. The user needs to provide BEACON GPS access and permission to their mobile device.

= Optional Ambient Audio Recording: With consent, BEACON records and transmits background audio (e.g., voices, threats, environmental cues, etcetera).

= Data Packet Compilation: BEACON combines a) Translated text responses, b) Geolocation data, c) User information, d) Language preference, and e) Audio recordings (if enabled).

= Conversion into a 911 Call: The compiled packet is converted into a voice-based emergency call, where the responses are vocalized using synthesized, natural-sounding speech. BEACON has been coded to perform this conversion locally. Location data is vocalized, too. Audio clips are included.

How we built it

Designed mobile UI/UX flows in Figma (iPhone frame: 14/15/16). Used Figma Make + MCP server for design-to-code pipeline. Generated code using Claude (Sonnet 4.6 / Opus 4.6). Built a Vite + React-based app. Integrated translation logic, geolocation capture, and a modular audio recording system. Tested and debugged in WebStorm IDE.

Challenges we ran into

Missing dependencies and environment setup issues during code execution. Translating a conceptual legal-tech idea into a working UI/UX flow. Designing a system that balances usability with legal/privacy constraints (audio recording, consent). Structuring emergency communication into a format usable by existing 911 systems.

Accomplishments that we're proud of

I built BEACON as a one-person team. I am an LL.M. student (Technology Law) at the University of Pennsylvania Carey Law School with my undergraduate legal education from the National Law University and Judicial Academy, Assam, India. Additionally, I graduated in Electrical Engineering from the Vellore Institute of Technology, India. As a lawyer and an engineer, I managed to create a technical solution that is legally sound. I made a working prototype that reimagines 911 communication.

The working prototype was designed for a packet-based emergency architecture (text + GPS + audio). I created a system that works even when users cannot speak. I successfully aligned the solution with real-world legal and institutional constraints while providing audio capability.

What we learned

Emergency communication is as much a human problem as a technical one. Simplicity and clarity are critical in high-stress UX design. Legal frameworks (privacy, consent, liability) deeply shape technical design. Building on existing infrastructure (911) is more practical than replacing it.

Built With

• claude
• figma
• webstorm