Professional WorkCase Study
Art of Wine Companion App
A mobile-first event companion app designed to support vendor discovery, event navigation, structured information access, and reusable UI patterns for future event experiences.
Role
Sole Developer
Status
Production
Focus
Information Access + Event Experience
Type
Professional Production Application
Overview
What this project is
This project is a mobile-first event companion application built to support users during a large-scale event experience. It focuses on vendor discovery, event-specific information access, structured content modeling, and reusable frontend patterns for future event applications.
Problem
Why this project exists
Large events often create friction around wayfinding, vendor discovery, and access to event-specific information. The goal of this project was to create a more usable digital companion that improves navigation, information access, and decision-making during the event experience.
Goals
Project goals
- Design a mobile-first interface for event attendees
- Support vendor browsing and discovery workflows
- Create a reusable UI and data structure for future event apps
- Build a maintainable application foundation that can scale beyond a single event
- Make event-specific information easier to find, understand, and act on
System
Information architecture and system flow
The app combines structured content modeling, frontend interaction design, and backend-backed event data so users can move through event information in a more coherent way.
Event content / vendor data
↓
Structured data model
↓
Prisma / PostgreSQL
↓
API / server logic
↓
Next.js mobile-first UI
Stack
Technology used
- Next.js
- TypeScript
- Prisma
- PostgreSQL
- Tailwind CSS
Features
Key capabilities
- Vendor discovery and browsing flows
- Mobile-first layout for event use
- Structured event content modeling
- Reusable component patterns for future event apps
- Interactive support for event-specific information access
- Backend-backed content organization for event and vendor data
Technical Decisions
Important implementation choices
Why mobile-first by default
Because the application is intended for live event use, the interface needed to prioritize on-the-go access, fast scanning, and constrained mobile attention first.
Why Prisma with PostgreSQL
The project benefits from a structured schema and typed data access, making Prisma and PostgreSQL a strong fit for event and vendor-related content relationships.
Why reusable UI patterns matter
The app was designed not only as a single event experience, but as a foundation for similar future experiences, so reusable components and scalable structure were important from the start.
Constraints
Challenges and limitations
Event applications must balance usefulness with speed, simplicity, and attention constraints, especially on mobile devices. One key challenge was deciding how much functionality to include without making the experience feel heavy or cluttered.
Outcome
What this project demonstrates
This project demonstrates mobile-first application development, structured content modeling, relational data systems, reusable interface design, and the creation of tools that improve information access in a real-world environment.
Next Steps
Future improvements
- Expand interactive event guidance and wayfinding support
- Refine vendor discovery flows and UI states
- Add richer saved or favorited content interactions
- Document reusable architecture patterns for future event apps
- Apply the information architecture lessons from this project to future patient education and care navigation tools