>_ Jorge Uc / projects← All projects
~/projects/codigo-azul // ANDROID SYSTEM
◆ School communicationKotlin + CloudCase study

When every second matters.

Código Azul is an Android-based alert prototype developed for a Centro de Atención Múltiple (CAM), a specialized school serving students with substantial support needs, including some autistic students and students with ADHD. It coordinates authorized staff alerts through cloud services while considering how audible notifications might affect a sensory-sensitive environment.

Código Azul project cover
PROJECT FILE / CA-001ANDROID + CLOUD
CLIENTAndroidNative Kotlin & Compose
MESSAGINGFCMCloud-to-device transport
COORDINATIOND1Cloudflare Workers + SQLite
TEST SCOPE02devices in initial validation
01 / PROJECT CONTEXT

A notification is not enough.

An emergency protocol in a specialized educational environment brings two responsibilities together: notify staff promptly and avoid introducing unnecessary sensory stress for students who may be experiencing distress or a crisis.

01USABILITY

Make actions unmistakable

Give staff a focused mobile interface with recognizable visual feedback rather than a complicated control dashboard.

UX / ROLE DESIGN
02DELIVERY

Reach registered devices

Combine native Android notification behavior with cloud messaging and careful device-token management.

ANDROID / FCM
03SAFETY

Reduce unnecessary repeated sounds

Reject overlapping simulation requests so a repeated action does not generate avoidable bursts of alert audio.

BACKEND / SAFEGUARDS
02 / HUMAN-CENTERED DESIGN

An alert should be noticeable, not overwhelming.

In a CAM, some students can be especially sensitive to sudden or intense sounds. A notification that helps adults respond should be designed with its potential effect on students in mind.

SOUND DESIGN / CAREFUL TRADE-OFFS

Distinct enough for staff. Considerate of the environment.

Rather than defaulting to a piercing siren, the project explored a recognizable, chime-like alert with softer harmonic tones and controlled repetition. The aim was to make the signal identifiable to staff without adding an unnecessarily harsh auditory stimulus during a sensitive moment.

Sound preferences and sensory responses vary across individuals. These choices are design considerations, not evidence of clinical suitability or a guarantee that no student will be distressed.

RECOGNIZABLE · CONTROLLED · NON-STRIDENTConceptual sound profile · no audio playback
01 / AUDITORY EXPERIENCE

Consider sound quality

Choose a distinctive tonal pattern and avoid unnecessarily sharp, startling or continuously repeated signals.

02 / STAFF EXPERIENCE

Support rapid recognition

Pair the alert with a clear visual state so staff are not relying exclusively on audio to understand what happened.

03 / RESPONSIBLE VALIDATION

Test before wider use

Review volume, duration, accessibility and individual responses with the educational team in controlled, approved conditions.

This is a public description of the design rationale, not a disclosure of the institution's procedures, students' circumstances, trigger conditions or operational escalation rules.

03 / SYSTEM DESIGN

Three layers. One coordinated flow.

The public diagram shows component responsibilities only. It deliberately omits private infrastructure details, endpoint addresses, database paths and access policies.

> system.architectureCONCEPTUAL VIEW / NOT LIVE
IDENTITY & DEVICESFirebase

Authentication · Firestore

REQUEST COORDINATIONCloudflare

Workers · D1

Simplified technology overview · Not a complete production security diagram

04 / USER JOURNEY

From activation to attention.

A high-level description of staff notification. The alert design also considers the potential impact of audible signals in a sensory-sensitive school setting; specific response procedures remain private.

01

Authenticate

An authorized staff member accesses the Android application.

02

Request

An alert or simulation request passes through cloud coordination.

03

Distribute

FCM sends the event to registered recipients.

04

Notify

The Android client displays the alert and plays its configured sound.

05 / MOBILE EXPERIENCE

Designed around a clear next action.

The mobile experience favors readable states, predictable controls and a distinct, carefully considered audible alert for the CAM context.

REAL ANDROID SCREENSHOT

Less visual noise.
More clarity.

The application presents different views according to assigned roles. A prominent central action and concise state information reduce unnecessary interaction.

This is a screenshot of the actual project, not an interactive emulator or a live alert.

Before publication, confirm the screenshot does not reveal the CAM’s name, location, student or staff identities, internal alerts, or device identifiers.

Real screenshot of the Código Azul Android application
ANDROID APP SCREENSHOT
../assets/codigo ejemplo.png
06 / ENGINEERING

What I built.

From Android UI and notifications to serverless coordination, the project required several components to work as one system.

01 / CLIENT

Native Android

UI development with Kotlin and Jetpack Compose, prioritizing a streamlined staff workflow.

02 / IDENTITY

Role-aware access

Firebase-based sign-in with role and membership information used in application access flows.

03 / DEVICES

Push token lifecycle

Device registration and token cleanup associated with the user's application session.

04 / NOTIFICATIONS

Recognizable audio

A recognizable chime-like signal and dedicated Android notification behavior were explored with attention to sensory sensitivity, rather than relying on an aggressive siren. Sound behavior was checked on selected devices.

05 / BACKEND

Serverless services

Cloudflare Workers and D1 manage coordination and certain notification operations.

06 / SAFEGUARDS

Duplicate protection

A request-reservation mechanism rejects overlapping simulation attempts to avoid repetitive dispatch.

07 / DEVELOPMENT VALIDATION

Tested in a small, controlled setting.

These observations support functional integration, but not production-scale reliability or guaranteed emergency notification delivery.

✓ FUNCTIONALLY VERIFIED

FCM alert playback

A custom alert sound played in development testing.

✓ FUNCTIONALLY VERIFIED

Two-device simulation

A cloud-triggered test reached two registered devices, and both sounded the alert.

✓ FUNCTIONALLY VERIFIED

Overlapping requests

Duplicate simulation attempts were blocked during testing.

◈ DEVICE-SPECIFIC

Sound in restrictive modes

Alarm behavior was checked on a selected Android device, including Do Not Disturb configuration.

Important limitation. FCM delivery and Android audio behavior depend on permissions, operating-system settings, manufacturers, connectivity and other conditions. Código Azul is a software prototype, not a certified life-safety system or a guaranteed emergency channel.
08 / PERSONAL RETROSPECTIVE

What I learned building Código Azul.

The project connected mobile engineering and cloud infrastructure with a central lesson: software for an educational environment must respond to the needs of the people affected by it, not only the staff operating it.

BEYOND THE CODE

A working feature is only one part of a dependable experience. Building an alert-oriented application taught me to think simultaneously about usability, infrastructure, failure conditions and responsible validation.

01 / MOBILE ENGINEERING

Android is more than the interface

Building native notifications required understanding notification channels, audio behavior, device permissions and manufacturer-specific restrictions—not only UI screens.

KotlinJetpack ComposeAndroid
02 / DISTRIBUTED SYSTEMS

Cloud components need clear boundaries

Separating identity, device metadata, request coordination and push delivery helped me reason about responsibilities and troubleshoot the end-to-end flow.

FirebaseFCMWorkersD1
03 / PRODUCT DESIGN

Accessibility includes the sound itself

Working on an alert for a CAM taught me to think beyond screen accessibility: an alarm can help staff while also affecting students with sensory sensitivities. I learned to balance recognition, repetition, visual clarity and user needs without assuming one sound suits everyone.

UXAccessibilityRole-based UI
04 / VALIDATION & RESPONSIBILITY

A successful demo is not a reliability guarantee

Testing on two devices was valuable for proving integration, but it also clarified the need for broader device coverage, negative-case testing, security review and realistic deployment assessment.

TestingReliabilityPrivacy
KEY TAKEAWAY

Thoughtful engineering considers everyone affected by an alert.

Código Azul taught me that a technically successful notification is only part of the result. The experience also matters: how staff recognize the message, how students may experience the sound, and how the system communicates uncertainty and operational limitations.

09 / RESPONSIBLE DISCLOSURE

Public story. Private infrastructure.

This public case study explains why the system was built for a CAM and how sensory considerations influenced design, while keeping the school, students, procedures and deployed infrastructure unidentifiable.

SHARED PUBLICLY

Engineering case study

The general CAM context, accessibility and sound-design rationale, technology stack, conceptual architecture, sanitized UI screenshots and limited, non-identifying test observations.

KEPT PRIVATE

Operational details

The school’s identity and location, student or staff information, crisis scenarios and triggers, internal response protocols, live URLs, credentials, authorization rules, push tokens and private operational records.

PRIVATE IMPLEMENTATION

Interested in the engineering?

A sanitized technical walkthrough may be discussed upon request. The production-related source code and live environment are not publicly linked.

Contact me ↗