The product problem
Student identity, assignments, card services, feedback, and campus resources often live in separate journeys. University App brought those concepts into a coherent native interface backed by consistent service contracts.
Selected work
Started as a final-year project · September 2025 – Ongoing
University App
A student-focused platform built end to end: a native SwiftUI experience, an authenticated Go API, a React administration portal, PostgreSQL persistence, and reproducible containerized environments. I continue to develop the project while exploring product validation and its potential for commercialization.
- Role
- Project creator and full-stack developer
- Context
- SETU final-year project turned ongoing product exploration
- Stack
- Swift · SwiftUI (MVVM) · Go · PostgreSQL · RESTful APIs · JWT Authentication · Docker · Kubernetes · AWS · Terraform · Grafana
- Timeline
- September 2025 – Ongoing
One student experience across many university services.
The project explored how frequently used student workflows could share one mobile entry point and one authenticated platform core.
From academic project to product exploration
The first delivery had to demonstrate the complete path from interface to stored data within a final-year scope. With the academic milestone complete, I continue to explore product validation, deployment, future clients, and whether the platform can develop into a commercially viable product.
A working interface backed by real application flows.
The iOS client communicates with the project API for authenticated student data and service operations.
Student identity
Authenticated profile retrieval plus QR and barcode generation and verification.
Student workflows
Card requests, assignment tracking and submission, feedback, and telemetry endpoints.
Administration
A separate React portal supports staff authentication and administrative workflows through the same API boundary.
Privacy boundary
The published screenshot contains no student identifiers. Digital student ID card imagery from the project is intentionally omitted because its demo content includes identifying data.
Separate clients, services, and state.
The architecture keeps the native experience independent from administration and persistence, with the Go API acting as the authenticated contract between them.
Decisions that kept the project understandable.
The design favored explicit boundaries and reproducible environments over hiding the system inside one application.
Use SwiftUI with MVVM
Views, state, and service calls remain separated so student workflows can evolve without concentrating behavior inside interface code.
Centralize authenticated contracts
A versioned Go REST API, JWT bearer tokens, and PostgreSQL give both student and staff experiences one consistent source of truth.
Make environments reproducible
Docker Compose supports local development, while Kubernetes base resources and overlays make deployment boundaries explicit.
The first milestone is a demonstrable vertical slice — and the project continues beyond it.
The final-year delivery connected a native iOS interface to implemented authentication, student data, verification, card-request, assignment, feedback, and administrative workflows.
SETU listed University App in its 2026 Software Development Showcase. I now continue to explore validation and commercialization potential without presenting adoption, availability, or performance claims that have not been verified.