All originals
Place & memoryShipped 20245-week sprint

LocaMemory

Every place you have loved, remembered exactly where it happened.

Scroll for the technical layer
Layer 01 — The world

A dark topographic map where a single memory glows at the exact coordinates it belongs to.

A location-linked memory journal. Walk past a place and the memory surfaces, in the order it happened.

Interface01
Motion02
System03
Layer 02 — The build

X-ray the interface. See the engineering.

The challenge

Photo libraries are chronological, but memory is spatial. The moment you return to a place, the archive should know before you search for it.

Architecture decisions

  • 01One memory record per event, geofenced to a place record, never duplicated per view.
  • 02Background geofencing with a strict battery budget and on-device clustering.
  • 03Media stored privately; signed access only from within the app.

Build process

Week 1Mapped how people actually recall places.
Week 2Prototype: map first, list second.
Week 3Geofencing and battery discipline.
Week 4Privacy review, precision controls, offline map.
Week 5Ship with a three-place starter ritual.

Stack

Client
React Native · Expo
Geo
Native geofencing + clustering
Media
Private storage, signed URLs
Privacy
On-device precision reduction

From the codebase

// One memory, one place, many views
const memories = await byPlace(place.id) // map, list and timeline agree

Measured results

1.9%

daily battery cost

6.2

memories per active week

0

media records made public

The technical layer holds the challenge, the architecture decisions, the week-by-week build and the numbers. Open it when you want to judge the engineering, not the screenshots.