Delivery.
In active development and not publicly released. The 500+ figure describes the curated venue dataset, not users or adoption. No live demo or source-code link is offered until a public version is available.
CASE STUDY 03 / Independent product · Full stack
Coffee & Craft Beer Discovery Map
An independently built discovery product with 500+ curated places, connecting a React / Next.js map experience to a structured location dataset.
In development · Not releasedCONTEXT
Personal project
MY ROLE
Independent developer · Frontend and backend
TOOLS & FOCUS
Next.js · Node.js / Express · Supabase / PostgreSQL · SSR · Web SDK
01 / THE PROBLEM
What needed to work.
Place discovery needs both a useful browsing experience and organized location data. I am building a coffee and craft beer map around a curated dataset of more than 500 venues.
CONCEPT / 03
01Curated places
02PostgreSQL
03Map discovery
A summary of my responsibilities and technical approach. This workflow illustration does not reproduce the product UI.
02 / MY CONTRIBUTION
Where I took ownership.
- Developing the React / Next.js map product independently.
- Organizing and importing a dataset of 500+ places.
- Building with Node.js / Express and Supabase / PostgreSQL, including data access policies and server-side rendering.
- Built an initial web SDK for embedding Coffee Map functionality in third-party websites.
03 / TECHNICAL APPROACH
Decisions in context.
A structured foundation for discovery
Using PostgreSQL through Supabase for the venue dataset, with data imports and access policies treated as part of the product work.
04 / DELIVERY & REFLECTION
What I can share.
Have a similar challenge?
Let’s talk ↗