NOLIN
A campus commerce platform transforming how students order food and interact with university canteens.
Overview
NOLIN is a campus commerce platform built to modernize food ordering inside universities. Students can browse menus, place orders, receive real-time order updates, and collect meals only when they're ready, while vendors manage operations through dedicated dashboards and administrators oversee the entire ecosystem from a centralized portal.
Rather than simply digitizing food ordering, NOLIN is being designed as a scalable SaaS platform capable of supporting multiple campuses, vendors, and future student services through a unified operational ecosystem.
Problem
University canteens continue to rely on manual ordering systems that create long queues, payment confusion, and inefficient communication between students and vendors. During peak hours, students often spend more time waiting in line than actually eating, while vendors struggle to organize incoming orders alongside food preparation.
Traditional food delivery platforms are optimized for city-wide logistics rather than closed campus environments, making them expensive, unnecessarily complex, and poorly suited for university operations. NOLIN was created specifically to solve this operational gap.
Solution
NOLIN allows students to order food from anywhere on campus, monitor live order progress, and collect meals only after vendors mark them as ready. Vendors receive incoming orders through a dedicated operations console that simplifies preparation, updates order status in real time, and reduces manual coordination.
Administrators manage canteens, vendors, menus, users, and platform operations through a centralized administration portal while secure role-based authentication ensures every user accesses only the functionality relevant to them.
The result is a faster ordering experience for students and a significantly more efficient workflow for campus vendors.
Architecture
NOLIN is built using Next.js with Firebase Authentication providing secure user management and Firestore acting as the real-time operational database. Authentication supports both Email/Password and Google Sign-In, while role-based authorization determines access across Student, Vendor, and Administrator portals.
The platform currently includes over 40 application pages, 100+ reusable components, three independent dashboards, and approximately 15 Firestore collections supporting users, orders, menus, canteens, analytics, notifications, support tickets, and administrative data.
The architecture follows a modular, component-first approach designed for scalability, maintainability, and future multi-campus deployment.
Engineering Decisions
Firebase as the application backend.
Firebase provides authentication, real-time synchronization, Firestore, and security rules within a managed infrastructure, allowing development effort to focus on product functionality rather than backend operations.
Role-based platform architecture.
Instead of maintaining separate applications for students, vendors, and administrators, NOLIN uses a unified authentication layer with strict role-based routing and authorization. Each portal shares common infrastructure while exposing only the features relevant to its users.
Reusable component architecture.
The platform is built around reusable UI components and modular services instead of page-specific implementations, making new dashboards and future features easier to develop and maintain.
Production-first development.
Every feature is designed with scalability, responsiveness, accessibility, and long-term maintainability in mind rather than simply demonstrating functionality.
Challenges
The most challenging aspect of NOLIN was designing a secure authentication and authorization system capable of supporting multiple user roles without compromising user experience.
Managing Google Sign-In, first-time account creation, protected routes, suspended accounts, role synchronization, Firestore Security Rules, and dashboard-specific permissions required careful planning to ensure every user could only access the data and functionality assigned to their role.
As development progressed, maintaining consistency across three independent dashboards while preserving component reusability became an equally significant architectural challenge.
Impact
- Built a production-oriented SaaS platform with 40+ pages and 100+ reusable components.
- Developed three independent portals for Students, Vendors, and Administrators.
- Implemented secure role-based authentication using Firebase Authentication and Firestore Security Rules.
- Designed approximately 15 Firestore collections supporting scalable real-time operations.
- Integrated Google Authentication, email notifications, cloud deployment, and real-time database synchronization.
- Built a responsive, mobile-first experience optimized for desktop, tablet, and mobile devices.
Product Vision
NOLIN began as a solution to eliminate food queues inside university campuses, but the long-term vision extends far beyond canteen ordering.
The platform is being designed as a campus commerce ecosystem where students, vendors, and university administration can interact through a single operational platform. Future expansion includes digital payments, vendor analytics, inventory management, support systems, campus announcements, event services, and additional university-focused experiences.
Every architectural decision made during development prioritizes scalability and long-term product evolution rather than short-term feature delivery.
What I Would Improve
Future development will focus on integrated online payments, vendor analytics, inventory management, AI-powered demand forecasting, automated order prioritization, QR-based order collection, and a dedicated support dashboard.
Long term, I plan to evolve NOLIN into a multi-tenant SaaS platform capable of serving multiple universities through isolated campus environments while maintaining centralized administration, scalable infrastructure, and production-grade reliability.