The POS & Wristband Management system is a .NET WPF desktop application used by staff to manage NFC wristbands and player records.

It was originally built for one simple purpose:

• initialize a wristband with time / game allocation
• let players complete registration themselves on the registration tablet

Over time, it evolved into a much more capable operational tool.

Today, it is used to:

• initialize wristbands
• register players directly
• renew old wristbands
• search and edit player records
• manage player details, time, and related wristband history

It communicates with the backend through the API and serves as one of the main staff-facing operational tools in the facility.

The POS includes 4 major pages.

1. Register

The Register page allows staff to create player records and bind a new wristband to them.

Staff can:

• enter the player's email (primary key)
• set their actual/game name
• assign time allocation to the wristband
• scan a new wristband when prompted
• bind the wristband to that player

It also supports family/group workflows:

• if a player is a minor, the parent can be registered as the primary account
• children can then be added under the same email

This made it easier to handle real family registration instead of forcing separate isolated entries.

2. Lookup

The Lookup page is one of the most feature-rich parts of the application.

It allows staff to:

• view all players in the database
• search players through the search bar
• inspect their records such as:
• wristbands used
• games played
• scores
• time remaining
• edit player information:
• name
• email
• children / dependents
• child information
• add more time to a wristband if needed

This page turned the POS into more than a scanner tool - it became a practical management system for day-to-day staff operations.

3. Renew

The Renew page supports returning players who already have an old wristband.

Instead of entering all the information again, staff can:

• scan the old wristband
• retrieve the linked record
• add more time directly

This makes repeat visits much faster and more convenient.

4. Initialize

The Initialize page supports fast preparation when staff are busy.

In this mode, staff can:

• scan a blank wristband
• add the time allocation
• skip full player registration at the POS

The player can then complete registration later using the registration tablet.

This created a faster fallback workflow during peak traffic.

I worked on the POS as part of the broader AeroSports software ecosystem and contributed to both the feature evolution and the operational workflow design.

My contribution included:

• helping define the workflow architecture for initialization, registration, renewal, and lookup
• contributing to the transition from a minimal WinForms tool into a full WPF application
• helping align POS behavior with the registration tablet system
• improving messaging, alerts, and user flow clarity
• supporting rollout, training, and staff adoption through documentation and guide materials

This project was also collaborative.

One of my teammates had stronger WPF experience and played an important role in helping complete:

• the new WPF/XAML UI
• page structure
• feature development

Together, we turned the POS from a limited initializer into a much more capable staff operations tool.

Other projects from the same platform and codebase.

Kiosk Host & Room Control (.NET WebView)

WinForms orchestration layer between the Kiosk UI, Scorecard UI, Game Engine, backend API, and room hardware.

WCPUS

View project

Registration Tablet System (MAUI + Next.js)

Self-service player registration system using MAUI kiosk tablets and a hosted Next.js interface with NFC wristband scanning.

M+2

View project

Admin Portal (Platform Control & Analytics)

Centralized web platform for managing games, players, analytics, smart devices, and documentation with authentication and role-based access control.

JAC/A

View project