Overview:
NodeChat is a full-stack real-time chat application built from scratch as part of a Node.js crash course. It demonstrates core backend concepts including REST APIs, WebSocket communication, JWT authentication, and Google OAuth — all served from a single Express server with a vanilla JS frontend.

Core Features:

• Authentication: Email/password registration and login with JWT, plus Google OAuth via Passport.js.
• Rooms: Create public or private rooms, browse and join public rooms, invite users to private rooms.
• Direct Messages: Find users by email and start private one-on-one conversations.
• Real-time Messaging: Instant message delivery using Socket.IO with room-based broadcasting and online user tracking.
• Message History: Persistent chat history loaded from MongoDB on room or DM open.

Technical Implementation:

• Backend: Node.js + Express with a domain-driven folder structure (auth, messages, rooms, users)
• Real-time: Socket.IO with JWT middleware on the handshake for authenticated connections
• Database: MongoDB via Mongoose with User, Message, and Room models
• Auth: JWT tokens + bcrypt password hashing + Passport.js Google OAuth 2.0
• Frontend: Vanilla HTML, CSS, and JavaScript — no framework required
• Deployment: Single-repo deployment on Render with MongoDB Atlas

What I learned:
Building NodeChat covered the full backend development lifecycle — from designing a REST API and real-time socket events, to handling authentication flows, database modeling, and deploying a live production app.

Overview:
SabaiJob is a mobile platform for Myanmar immigrant workers, connecting them with verified blue-collar job opportunities. The app aims to be easy to use, secure, and tailored to job preferences, while fostering connections with employers, NGOs, and the community. I contributed to the mobile app UI and API integration, ensuring a smooth and responsive experience for users.

Key Features:

• Job Seekers: Browse secure and verified job posts tailored to your preferences.
• Employers & NGOs: Connect with the workforce and contribute to the community.
• Notifications & Updates: Stay informed on application status and opportunities
• Freemium & Premium Features: Access to daily limited job posts or unlimited job posts.
• User-Friendly Design: Intuitive interface for easy navigation.

Technical Implementation:

• Mobile App (Flutter): UI development and API integration

Project Impact:
Successfully launched on Google Play Store with active user base. The platform has facilitated numerous job placements and received positive feedback for its user-friendly interface.

Overview:
The Ultimate Tic Tac Toe project is an enhanced version of the traditional game, expanding it into 9 big grids with 9 small grids each (total of 81 cells). It introduces player accounts with sign-up and log-in, while delivering a more complex and strategic experience compared to the classic version.

Key Features:

• Player Accounts: Players can sign up (generating a unique ID) or log in with their existing ID.
• Game Mechanics: Classic X vs O gameplay, but expanded to 9×9 nested grids for deeper strategy.
• Victory Conditions: Winners are determined by capturing large grids through diagonal, vertical, or horizontal alignments. If no clear winner emerges, the player with more large grids wins; ties are also supported.
• Deployment: Hosted on Google Cloud for online play

Technical Implementation:

• Backend: Java Spring Boot (MVC architecture)
• Frontend (View): HTML, CSS, JavaScript
• Deployment: Google Cloud Run

Overview:
A full-stack platform that integrates AI-driven healthcare recommendations with modern mobile and web interfaces. It enables patients, doctors, and administrators to collaborate seamlessly, ensuring efficient healthcare workflows supported by AI and doctor validation.

Core Features:

• Patient Mobile App: View lab data with doctor-approved recommendations and manage appointments.
• Admin Dashboard: Upload patient lab data (manual or bulk), manage doctors, departments, and appointments.
• Doctor Dashboard: Review lab results with AI-generated recommendations, refine or override them, and approve final recommendations for patients.

Technical Implementation:

• Backend: Node.js (API services) + Python (rule-based algorithm)
• AI: Google Gemini (processes lab results and generates recommendations)
• Mobile App: Flutter (Clean Architecture + BLoC for state management)
• Web Frontend: ReactJS (Admin & Doctor dashboards)
• Database: PostgreSQL (hosted on Render)

Project Impact:
Developed as part of a team project, this system demonstrates the application of technology in healthcare to improve patient care and operational efficiency. The AI recommendation system achieved 85% accuracy in preliminary testing.

Overview:
The Restaurant App is a mobile restaurant management system developed as a second-year Mobile Application Project. It streamlines operations across three key roles — Waiter, Chef (Kitchen), and Cashier — improving coordination and efficiency with real-time updates.

Key Features:

• Chef (Kitchen): View incoming orders, update status (e.g., In Progress, Ready to Serve), and notify waiters when food is prepared.
• Waiter: Take customer orders, track order status, and receive notifications when dishes are ready.
• Cashier: Manage orders, handle billing & checkout, and oversee customer reservations.

Technical Features:

• Frontend (Mobile): Flutter (cross-platform development)
• Backend Services: Firebase (Authentication, Firestore Database)

Overview:
The Smart Campus Mobile App enhances the student experience by centralizing essential university services. From schedules to navigation and document requests, it makes campus life more convenient and connected.

Key Features:

• Class Schedules: View personalized timetables and stay updated on upcoming classes.
• Interactive Campus Map: Easily navigate campus landmarks such as buildings, dormitories, cafeterias, and facilities.
• Document Requests: Submit official requests for transcripts, certificates, and more directly in the app.
• AI Chatbot: Gemini-powered chatbot that provides instant answers to student inquiries.

Technical Implementation:

• Mobile Development: Flutter framework for consistent cross-platform experience
• Backend (CMS): Strapi
• Database & Authentication Firebase Firestore
• Maps Integration: Custom indoor mapping solution with GPS coordination

Overview:
A full-stack cake shop management system built as two separate web apps: a customer-facing storefront for browsing, customizing, and ordering cakes, and an owner dashboard for managing the business end-to-end. Backend built using agentic AI coding workflows (Claude Code) with active review and iteration; frontend similarly built with Google Antigravity, with me directing architecture, reviewing/editing generated code, and making all technical decisions.

Key Features:

• Customer Storefront: Browse and customize cakes, add to cart, place orders, schedule pickup, track order status, and reserve the birthday room with double-booking prevention.
• Owner Dashboard: Manage cakes, categories, and orders; confirm and process bookings; print baking slips; view sales analytics with CSV export.
• Auth: Google OAuth and email/password login on both apps.
• Notifications: Event-driven email notifications for order and reservation updates.

Technical Implementation:

• Backend: NestJS with modular architecture — auth, cakes/categories/options, cart, orders, room reservations, analytics/reporting, email events.
• Frontend: Two separate React apps — a Next.js owner dashboard and a Vite + React customer storefront.
• Database: PostgreSQL with JWT-based auth.

Overview:
A full-stack, multi-tenant SaaS platform for companies and teams to manage projects and tasks. Organizations register their own workspace, invite team members by email, and subscribe to tiered plans (Free, Starter, Pro, Business) with usage limits enforced per plan. Billing is handled through Stripe with a webhook-driven architecture for reliable, asynchronous payment processing.

Key Features:

• Multi-Tenant Architecture: Company-based workspaces, each with their own projects, members, and billing state.
• Two-Tier Role-Based Access Control: Independently scoped company- and project-level roles and permissions, enforced through composable authorization middleware.
• Stripe Subscription Billing: Tiered plans via Stripe Checkout, with plan-based project limits and subscription-status gating on key actions.
• Webhook-Driven Payment Sync: Subscription lifecycle events (checkout completion, renewal, cancellation) processed asynchronously and verified via signature checks.
• Email-Based Invitation System: Token-based invitation flow supporting both existing users and brand-new signups, for both company and project membership.
• Activity Logging: Company- and project-scoped audit trail surfacing key actions across the platform.
• Database Transactions: Atomic operations for registration, invitation acceptance, and project creation to ensure data consistency across related records.

Technical Implementation:

• Backend: Node.js/Express with a layered architecture — routes, controllers, services, repositories — organized by domain module (auth, company, project, task, billing, activity log, admin).
• Database: MySQL via Prisma ORM, with a relational schema covering identity, tenancy, RBAC, work management, and billing.
• Auth: JWT authentication with middleware for membership verification, permission checks, and plan/billing enforcement.
• Billing: Stripe Checkout sessions with metadata-based tenant tracking and webhook signature verification.
• Validation: Zod schemas on all mutating endpoints with centralized error handling.
• Email: Mailtrap/Nodemailer integration for invitation and notification emails.
• Frontend: React single-page application consuming the REST API, with role-aware UI and plan-based feature gating.
• DevOps: Containerized with Docker and Docker Compose for reproducible local development; deployed with the backend on Render, MySQL database on Neon, and frontend on Vercel.

Subscription States:
New companies start on the Free plan automatically. Upgrading triggers a Stripe Checkout session; the subscription transitions to active only once Stripe confirms payment via webhook — never optimistically on the client-facing redirect alone.