SafeLocket
Mobile App2023

SAFELOCKET

OTP auth, Google Maps SOS shell, QR device pairing, FCM — Flutter + App Engine API.

2
Phone + device trust factors
1
QR hardware pairing flow
24/7
FCM-capable alert path
SCROLL
Client
Domain
Mobile / Safety
Platform
Flutter
Duration
Core Stack
Flutter · Maps · FCM · App Engine
The Brief

THE
PROBLEM

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.

Core Engineering Challenge

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.

Mobile
Platform
Extended stack
mobile
Flutter
mobile
Google Maps
backend
Firebase
safelocket
safelocket
How we built it

THE ARCHITECTURE

01
OTP & session

Phone verification, secure token storage, and logout wiping local secrets.

FlutterAuth
02
QR device pairing

Scan flows bind hardware identifiers visible to support dashboards.

QRProvider
03
Maps shell

Google Maps with draggable sheets for SOS and contact shortcuts without obscuring the map entirely.

Google MapsFlutter
04
Geofencing & SOS

Background location policies aligned to platform rules; SOS triggers server notifications.

GeolocationFCM
05
App Engine API

REST endpoints for contacts, devices, and alert routing with auth middleware.

App EngineNode.js
System Data Flow
Ingestion
CrawlerContent Hash10K+ pages
Processing
ChunkerDeduplicatorEmbedding API
Storage
pgvectorPostgreSQLRedis Cache
Auth
Identity ProviderJWT BridgeSessions
Query
HNSW SearchRe-rankerLLM Stream
Delivery
Web AppMobile AppUsers
What we delivered

THE RESULTS

Mobile

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.

Mobile
Platform

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.

Visual documentation

SCREENS &
INTERFACES

safelocket2
safelocket2
safelocket3
safelocket3
safelocket4
safelocket4
safelocket5
safelocket5
safelocket6
safelocket6
Engineering decisions

TECH
DEEP DIVE

OTP
OTP-first trust

Phone ownership verified before pairing wearables or trusted contacts.

FCM token refresh on login prevented silent push failures after reinstalls.

PRV
Provider state

Readable separation for map, sheet, and auth trees as safety features expanded.

App Engine kept compliance-friendly boundaries versus a monolithic Firebase-only backend.

Next Case Study
Blockchain
ScotchMaltWhiskeyNFT

Whisky bottle marketplace

SolidityNext.jsMongoDB
Start a project

LET'S
BUILD
SOMETHING.

We take on a small number of projects at a time. If the problem is hard, we're interested.

Email
hello@techmusketeers.com
Response time
Within 24 hours
Availability
Open for new projects · 2025