Professional WorkCase Study

Art of Wine Companion App

A production mobile-first event companion application built to organize event and vendor information, support discovery and wayfinding, and provide a reusable foundation for future event experiences.

Professional Systems + SoftwareProductionNext.jsTypeScriptPrismaPostgreSQLTailwind CSS

Role

Sole Full-Stack Developer

Status

Production

Focus

Information Access + Event Experience

Type

Professional Production Application

Overview

Organizing an event experience around accessible information

The Art of Wine Companion App is a production mobile-first application built to help attendees navigate event information and discover participating vendors. The project combined structured content, relational data, backend-supported information access, and reusable interface patterns within an experience designed primarily for mobile use.

Problem

Helping attendees find useful information during a live event

Large events can make vendor discovery, wayfinding, and access to event-specific information difficult, especially when attendees are moving through a busy environment and relying on their phones. The application needed to organize that information into a clear, responsive experience without overwhelming users or making important details difficult to find.

Goals

What the application needed to accomplish

  • Create a mobile-first experience for attendees using the application during the event
  • Make vendor and event information easier to browse and locate
  • Organize content through a structured and maintainable data model
  • Support reusable interface and data patterns for future event applications
  • Balance useful functionality with clear navigation and fast scanning

System

Connecting structured event data to a mobile-first interface

The application connected structured event and vendor information with a relational database, server-side application logic, and reusable frontend components. This separation supported clearer content organization while allowing the interface to present information in a format suited to mobile event use.

Event and vendor information

↓

Structured Prisma data model

↓

PostgreSQL database

↓

Server and application logic

↓

Next.js mobile-first interface

Technology

Tools used

The application used Next.js and TypeScript for the application layer, Prisma for structured data access, PostgreSQL for relational storage, and Tailwind CSS for responsive interface styling.

  • Next.js
  • TypeScript
  • Prisma
  • PostgreSQL
  • Tailwind CSS

Application Work

Key implementation areas

  • Vendor discovery and browsing flows
  • Mobile-first event information access
  • Structured event and vendor content
  • Relational data modeling with Prisma and PostgreSQL
  • Reusable interface components for related event experiences
  • Responsive navigation and content presentation

Technical Decisions

Implementation choices shaped by event use

Design for mobile use first

Attendees were expected to access the application while moving through the event, so the interface prioritized mobile screen sizes, clear navigation, fast scanning, and focused content presentation.

Model event information relationally

Vendor and event information contained structured relationships that needed to remain consistent and maintainable. Prisma and PostgreSQL provided a typed data-access layer and a relational foundation for organizing that content.

Build reusable patterns

The application was designed as more than a one-time interface. Reusable components and structured content patterns created a foundation that could support similar event experiences without rebuilding every interaction from the beginning.

Constraints

Building for attention-limited event use

The application needed to remain useful on a small screen while users were navigating a live event with limited time and attention. The work required balancing information depth with scanability, organizing varied event content consistently, and keeping the production implementation maintainable without introducing unnecessary interface complexity.

Outcome

What the completed work demonstrates

The result was a production mobile-first application supported by structured content, relational data, reusable components, and backend application logic. The project demonstrates full-stack product development, information architecture, database-backed content organization, responsive interface design, and the translation of event and operational requirements into a usable digital system.

Further Development

How the application could continue to evolve

  • Evaluate information findability using appropriately collected feedback and product data
  • Refine vendor discovery, filtering, and browsing states
  • Expand event guidance and wayfinding support where useful
  • Add saved or favorited content interactions if supported by user needs
  • Strengthen documentation for reuse across future event applications