
OTP auth, Google Maps SOS shell, QR device pairing, FCM — Flutter + App Engine API.
Personal safety product combining phone OTP, QR-based trusted device pairing, Google Maps shell with contextual bottom sheets, SOS triggers, geofencing, and emergency contacts — all in a calm UI under stress.
Provider-pattern Flutter, REST API on Google App Engine, Firebase Cloud Messaging for push, SharedPreferences for session continuity, and structured device registration flows for QR onboarding.
Map + bottom sheet interaction patterns on small screens, IMEI/SIM-enriched device payloads for support, and reliable FCM token sync on login so alerts always reach the handset that actually answered OTP.

Phone verification, secure token storage, and logout wiping local secrets.
Scan flows bind hardware identifiers visible to support dashboards.
Google Maps with draggable sheets for SOS and contact shortcuts without obscuring the map entirely.
Background location policies aligned to platform rules; SOS triggers server notifications.
REST endpoints for contacts, devices, and alert routing with auth middleware.
Production safety workflows shipped for field testing — OTP-first trust, geofence alerts, and SOS paths validated with real users rather than mocked location stubs in QA only.
Production safety workflows shipped for field testing — OTP-first trust, geofence alerts, and SOS paths validated with real users rather than mocked location stubs in QA only.





Phone ownership verified before pairing wearables or trusted contacts.
FCM token refresh on login prevented silent push failures after reinstalls.
Readable separation for map, sheet, and auth trees as safety features expanded.
App Engine kept compliance-friendly boundaries versus a monolithic Firebase-only backend.
We take on a small number of projects at a time. If the problem is hard, we're interested.