AWS Builder Center
Full Stack Challenge: EchoBlock

Full Stack Challenge: EchoBlock

EchoBlock is a hyperlocal storytelling app where residents drop anonymous "time capsule" stories tied to real street corners and landmarks - locked behind a threshold of unique passersby who have to physically show up before the story unlocks. Built on AWS Lambda, DynamoDB, and Amplify Hosting, it turns foot traffic into the key that unlocks a neighborhood's hidden memory.

AWS Community Builder - AI Engineering | Junior Engineer @ MulticoreWare
Great Day Everyone!! ☺️🤗
This is a random word, random project, random article. Enjoy your time reading this.

Vision and What It Does

Every neighborhood is full of stories nobody tells - the park bench where someone got engaged, the corner store that closed after forty years, the alley where a first kiss happened. Those moments live in people's heads and then quietly disappear. EchoBlock gives them a place to live instead.
EchoBlock is a hyperlocal storytelling platform. Residents drop anonymous "time capsule" posts tied to real, physical locations - street corners, park benches, landmarks 💓. But a post doesn't just sit there waiting to be read. It stays locked behind a threshold: a minimum number of unique people have to physically walk through that exact spot before the story unlocks for anyone. You can't read what your neighbor wrote until your community shows up for it.
It's built for people who want a quieter, more physical alternative to social media's broadcast-everything model - a layer of memory tied to place rather than to a feed. The target audience is anyone curious about the history sitting under their feet: long-time residents, newcomers to a neighborhood, and communities that want a shared, evolving record of the places they live in.
FYI : Coudn't think of something better with the given word 🥲

Full Stack Breakdown

The Full Stack series walks through pitch → prototype → MVP → UX → launch, and EchoBlock followed that arc closely:
  • Pitch: The idea started from the challenge word itself. "Threshold" suggested two things at once - a physical doorstep and a tipping point a community has to collectively cross. Tying an unlock mechanic to real foot traffic, rather than just a like count, felt like the most literal and most interesting reading of the word.
  • Prototype: The first version was scoped down hard - no real geofencing, no Amazon Location Service, just the core loop: submit a story pinned to a location, register a "ping" when someone is near it, unlock once enough unique pings land.
  • MVP: The MVP cut the heatmap view and the "preserve" voting logic to focus entirely on making the unlock mechanic work correctly and feel satisfying - that's the one loop a demo lives or dies on.
  • UX: The visual language leans into "dark-mode urban cartography meets handwritten journal" - locked posts render blurred with a progress indicator ("1 of 3 pings"), unlocked posts get a warm gold accent, and the whole thing is built to feel like finding a handwritten note rather than scrolling a feed.
  • Launch: Deployed via AWS Amplify Hosting for a fast, low-friction path to a live HTTPS URL. What shipped is the full loop: you can drop a story at your real coordinates, walk past someone else's, and watch it open. Three Lambdas behind a REST API, two DynamoDB tables, a Leaflet map, and a live HTTPS URL. What got cut was everything that made the loop prettier rather than true. Amazon Location Service and real geofencing went first - a full table scan with a haversine filter in application code does the same job at MVP scale and took an afternoon instead of a week. The heatmap went next. The "preserve" button survived in the UI but only as a local toggle; there's no endpoint behind it, because upvote plumbing would have eaten the time I needed to get the unlock mechanic actually correct. One cut I didn't anticipate: the per-card "I'm here" button. It works fine against mock data and is impossible against a real location API, for reasons I'll get to.

How You Built It

Scaffolded well first time: React components, the visual language, the map, the locked-card blur, and the Lambda handlers structurally.
Needed iteration: every seam between systems.
  • 502 on all three endpoints after a clean deploy. SAM's esbuild was emitting ESM while the AWS SDK ships CommonJS, so the generated __require shim broke at runtime. Nothing wrong with my code or template. Switching the bundle to CJS fixed all three.
  • sam validate --lint caught that nodejs20.x was already deprecated. I'd have shipped a runtime on a countdown.
  • First Amplify deploy served HTML and 404'd every asset. PowerShell's Compress-Archive writes ZIP entries with backslashes, so Amplify extracted files literally named assets\index-abc.js. Had to build the archive through .NET to get forward slashes.
  • A React bug that was mine, not the tooling's: I collected freshly-unlocked stories inside a setState updater and returned them. Updaters don't run synchronously, so the array was always empty — and StrictMode's double-invoke would have duplicated every entry. Fixed by computing from a ref snapshot before setting state. The haversine maths, supposedly the hard part, was fifteen lines and worked immediately.

AWS Services / Architecture

EchoBlock runs on a serverless architecture end to end:
  • AWS Amplify Hosting - frontend hosting and deployment
  • Amazon API Gateway - REST endpoints for submitting stories, registering pings, and listing stories
  • AWS Lambda - three functions:  submitStory  (create a new time-capsule post),  registerPing  (the core threshold/unlock logic), and  listStories  (feed data)
  • Amazon DynamoDB - two tables:  EchoBlockPosts  (story content, location, ping count, unlock state) and  EchoBlockPings  (tracks which anonymous device has pinged which post, to enforce unique-visitor counting)


What You Learned

  • The API's shape dictates the UI's shape, and I designed the UI first. registerPing takes your coordinates and decides what's nearby - that's the integrity of the mechanic. A per-card ping button would mean posting the story's own coordinates as your position, unlocking anything from anywhere. The buttons had to collapse into one global "I'm here".
  • The atomic increment held up, but ADD alone wasn't enough. It protects the count, not the unlock. Three people crossing the threshold in the same second produce three correct increments and three unlock announcements. Exactly-once needed a second conditional update guarded on unlocked = false. It can't be one call because DynamoDB condition expressions can't do arithmetic across attributes - "pingCount + 1 >= threshold" is inexpressible. Two calls then need a compensation path: a failed increment must delete its own ping claim, or that device is locked out of that story forever.
  • The mechanic lives in the API, not the CSS. The feed was specced to "return all posts". Built literally, the frontend blurs locked text while shipping it in plain JSON - one curl and the premise collapses. Locked stories now leave the server with no text field, and the geohash index deliberately doesn't project the story body.
  • Next: Location Service for enforced geofences (the GSI is already in the table and both handlers are one function away from a query), then a real preserve/decay endpoint, then the heatmap.
  • On Kiro: fast on scaffolding and on anything with one right answer. Useful friction wherever my spec was subtly wrong - it pushed back on returning locked text, on read-then-write device dedup, and on ISO timestamps for DynamoDB TTL. More of my time went to environment archaeology than code: a control character in my AWS config, an access key and secret pasted into each other's fields, an IAM user with zero permissions, and 75 seconds of IAM propagation where only Lambda stayed denied.
Repo Link
Any opinions in this article are those of the individual author and may not reflect the opinions of AWS.
Enjoyed reading this content? Let the author know!

Your likes, comments, shares, and saves help creators reach more builders.

Loading recommendations

Loading article