← Selected work

Full-stack product case study

Samaritan Inn

A full-stack web application designed to streamline guest services and staff workflows.

A collaborative UT Dallas EPICS project built around real stakeholder requirements.

Organization
Samaritan Inn / UT Dallas EPICS
Focus
Full-Stack Development, Product Requirements, Stakeholder Collaboration
Technologies
Next.js, TypeScript, Prisma, SQLite, NextAuth

The problem

Move essential workflows beyond the front desk.

Guest services such as class and appointment scheduling were being handled manually at the front desk.

The product challenge was to reduce manual administrative work while giving guests easier access to scheduling and important information.

The solution

One application for core guest-facing workflows.

The team developed the broader application collaboratively.

01

Class scheduling

Guest class scheduling within the centralized application.

02

Appointment scheduling

Appointment scheduling through an API-based system.

03

Announcements

A staff-to-guest communication channel for more than 200 guests.

04

Authentication

Login controls for access to the application.

05

Role-based access

Different permissions for administrators and guests.

Announcements system

A controlled channel from staff to 200+ guests.

Administrators could publish announcements, while authenticated guests could view them after logging in. Guests could not publish or modify announcements.

01

Administrators publish

02

Authenticated guests view

03

Guests cannot create or modify

04

Permissions control each action

  1. 01

    Admin

  2. 02

    Login

  3. 03

    Create announcement

  4. 04

    Announcement stored

  5. 05

    Authenticated guest

  6. 06

    View announcement

My contribution

Technical implementation and stakeholder coordination.

My work centered on the announcements feature, access control, and keeping development connected to stakeholder needs.

Announcements system

Built the announcements system for more than 200 guests.

One-way communication

Designed the feature so administrators could publish and authenticated guests could view announcements.

Role-based access

Implemented access controls so only administrators could create announcements.

Authentication

Worked with the login and authentication system to enforce user permissions.

Stakeholder liaison

Connected the development team with Samaritan Inn stakeholders.

Iterative delivery

Presented product iterations, gathered feedback, clarified requirements, and helped keep development aligned with stakeholder needs.

Stakeholder collaboration

An iterative bridge between stakeholder needs and team delivery.

I presented product iterations, gathered feedback, clarified requirements, and shared updated direction with the team to help keep development aligned.

  1. 01

    Stakeholder requirements

  2. 02

    Team development

  3. 03

    Product iteration

  4. 04

    Stakeholder demo / feedback

  5. 05

    Updated requirements

Technical implementation

A concise full-stack foundation.

01

Frontend / Application

Next.js, TypeScript

02

Data

Prisma, SQLite

03

Authentication

NextAuth

Technical artifact

Explore the project repository.

The GitHub repository contains the collaborative UT Dallas EPICS application work.

Team

Built collaboratively through UT Dallas EPICS.

The UT Dallas EPICS team standing beside the Samaritan Inn project poster
The EPICS team behind the Samaritan Inn application.

Samaritan Inn was a team project. The broader application—including guest scheduling, appointments, announcements, authentication, and role-based access—was delivered through shared development and stakeholder collaboration.

Outcome

A digital path for guest-service workflows.

The team delivered a web application designed to move guest-service workflows such as scheduling and announcements from manual processes into a centralized digital system.

What I learned

Building software with the stakeholder—not just for them.

Real requirements

Building software around the needs of a real stakeholder organization.

Permissions and roles

Designing user roles and permissions around who should perform each action.

Feedback into product changes

Translating stakeholder feedback into clear updates for the development team.

Technical and user needs

Balancing implementation choices with the needs of staff and guests.

Iteration and alignment

Presenting work in progress and helping a team remain aligned with its stakeholder.