HISTORICAL RESEARCH / INDEPENDENT APPLICATION BUILD

Tiki Tropical

Tiki Tropical translates historical cocktail research into an interactive reference concept, with a structured recipe model and an independently developed Next.js, React, and MongoDB prototype.

NEXT.JSREACTMONGODBRESEARCH + DATA MODELING

A playful premise, serious source work.

Tiki Tropical started with a simple consumer idea: help people discover and make excellent, historically grounded tiki cocktails. But turning that into a useful reference meant more than collecting drink names and throwing a palm tree on a screen.

Vintage bartending literature, provenance research, and hands-on recipe preparation informed the data model. Each record needed to preserve more than ingredients: context, method, origin, presentation, and source.

The experience was designed to feel playful without compromising the care given to recipes, history, or source material.

Research translated into an application model.

The prototype uses Next.js, React, Tailwind CSS, and MongoDB. Server-side logic retrieves a drink catalog; dynamic detail pages present structured records; an API route looks up individual drinks by database ID.

01 / CATALOG

Database-backed discovery.

A server-rendered listing queries a MongoDB drink collection and presents names with origin-year metadata.

02 / RECORD MODEL

More than ingredients.

Detail fields cover measurements, methods, garnishes, vessels, dates, tags, source references, creators, and origin bars.

03 / APPLICATION FLOW

Individual drink retrieval.

Dynamic detail routing and an API endpoint define how a selected drink is requested and represented in the interface.

The application remains a prototype, with its catalog, drink-detail model, and individual-record retrieval paths implemented.

Accuracy and atmosphere belong together.

Historical context shaped the taxonomy and drink-detail design. A cocktail's story can involve who created it, the bar and place it came from, the era, the serving vessel, and the preparation method—details worth modeling intentionally.

I also directed the visual identity and commissioned original artwork for the project.

The graphics here are illustrative; they are not application screenshots.

What this project demonstrates.

What began as subject-matter research became an exercise in product design: identifying the important details, modeling them, connecting database access to user-facing routes, and establishing a coherent visual identity.

Development paused at the prototype stage.

BACK / FLAGSHIP ARCHITECTURESANCTUM-CIRCE ↗