Prabesh Kunwar

AeroSports

Admin Portal (Platform Control & Analytics)

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

Stack

Next.js admin platform

Security

JWT + role-based access

Control

Game + player + config management

Automation

Smart device operations

Insights

Analytics dashboards

Case study →

Tech Stack Overview

Grouped by the primary systems, languages, and infrastructure used in this build.

Frameworks

Next.js

Libraries

React, Tailwind, shadcn/ui, Radix UI, Chart.js

Languages

TypeScript, JavaScript

Supporting Systems

Backend

Overview

The Admin Portal is a centralized web platform used to manage almost every operational aspect of the facility.

It started as a simple internal tool for developers to:

  • modify game settings
  • update game variants
  • avoid directly working with the database

Over time, it evolved into a full platform that supports:

  • game configuration
  • player data management
  • analytics and reporting
  • smart device control and automation
  • internal documentation and troubleshooting guides

It is built using Next.js and communicates with the backend through a secured API.

Architecture

The admin portal is a frontend application hosted on the server that interacts with a secured backend API. All database operations, authentication, and smart device control are handled through the API.

Platform controlJWT securedAPI-driven
Admin Portal (Next.js)
Backend API
Database
Smart Devices

Core Modules

The admin portal eventually became a multi-module system.

1. Game Management

Allows developers/admins to:

  • create new games and variants
  • modify game descriptions
  • adjust time, levels, and difficulty
  • update game-specific configurations

This removed the need to directly modify database tables.

2. Player Management

Includes a full player table with the ability to:

  • view player records
  • update player details
  • manage wristband-related data

3. Config Management

Stores system-level configurations such as:

  • game parameters
  • feature flags
  • environment-related settings

4. Smart Device Control

Once smart switches and automation were introduced, we added:

  • control of smart devices from the portal
  • scheduling and automation settings
  • manual override capabilities

Important note: All device logic is handled in the API, not the frontend.

The admin portal only:

  • updates settings
  • triggers API actions

5. Analytics Dashboard

Later, analytics became one of the most valuable parts of the portal.

It allowed:

  • tracking number of players
  • analyzing game performance
  • monitoring usage trends

This removed the need to run SQL queries manually and made insights accessible to managers and owners.

6. Documentation & Manuals

I added a dedicated documentation section that includes:

  • game room details
  • device explanations
  • troubleshooting steps
  • FAQs

This turned the portal into a knowledge base for staff and developers.

Workflow

Step 1

Authentication

When a user opens the portal:

  1. User enters username and password
  2. Request is sent to the API
  3. API validates:
  • credentials
  • request origin (IP / CORS checks)

If valid:

  • API returns a JWT token
  • user is logged in

Step 2

Authorization

Access is role-based.

  • Developers / Admins

  • full access

  • game configuration

  • device control

  • system settings

  • Staff / Managers

  • limited access

  • player management

  • documentation

  • selected device controls

Users only see the sections they are authorized to access.

Step 3

Data flow

  • Admin UI sends requests to API
  • API processes:
  • authentication
  • authorization
  • database operations
  • device actions
  • Response is returned to the UI

This keeps all sensitive logic out of the frontend.

Interface Evolution

Challenges

My Contribution

This project evolved alongside the entire AeroSports system, and I played a major role throughout its lifecycle.

My contributions included:

  • building and evolving the initial developer tool
  • designing workflows for game and configuration management
  • guiding the transition into a multi-user platform
  • working with the team to rebuild the portal with authentication and improved UI
  • integrating smart device control through API design decisions
  • adding a full documentation section with system knowledge, guides, and troubleshooting
  • supporting analytics integration and making the platform useful for managers and owners

This project reflects both my technical work and my role in shaping the system as it scaled.

Tech Used

Core technologies

Next.jsNext.js
ReactReact
TypeScriptTypeScript
JJWT

Supporting technologies

AAPI
C/ACharts / Analytics