Three audiences, one codebase
Route access is defined per role, and each user lands in their own workspace: students on the dashboard, instructors in teaching tools, administrators in approvals.
University platform — full-stack web applicationLive application
UniFlow Campus
One live workspace for students, instructors and administrators — with real sign-in, roles and attendance.
A full-stack campus application: email and social sign-in, role-based workspaces, attendance and grades, institution approvals, file uploads and an AI study assistant, all served by its own API layer.
- My part
- Full-stack development, product design and interface engineering
- Status
- Live application
- Built with
- Next.js
- React
- TypeScript
- Tailwind CSS
- API routes
- OAuth
- Brevo
- Vercel
Creator-provided interface screenshots, plus a fresh capture of the current public sign-in page.
Why it exists
Give a university one connected workspace: students follow courses, assignments, schedules, grades and attendance; instructors work in their teaching space; administrators approve institutions and invite staff — Arabic first, with English alongside.
My part: full-stack development, product design and interface engineering.
How it is built
Next.js App Router conventions built with Vinext (Vite and Rolldown) and deployed on Vercel. React and Tailwind CSS on the client. A server API layer of about thirty routes covers authentication and account security, registration, institutions and campuses, staff invitations, student records and directory, the grade overview, file and profile-photo storage, verification documents, the workspace and the study assistant. Requests carry the session cookie. The database engine is not visible from the public client, so it is not named here.
What is implemented
- Email sign-up and sign-in, Google and Facebook sign-in, and linking social accounts to an existing profile
- Account security: password change, recovery by email or authenticator app, a security overview and account deletion
- Role-based access: student, instructor and administrator workspaces, each limited to its own routes
- Attendance per course with recorded sessions and absences, alongside grades and a grade overview
- Courses, assignments, timetable, announcements and events for students
- Institution and campus onboarding with an approval review backed by uploaded proof documents, plus staff invitations
- Student directory and student records for staff
- File uploads and profile photos served through the application’s API routes
- An AI study assistant with saved conversations, running on the user’s own key for Groq, Gemini, OpenAI, Claude or DeepSeek
- Transactional email through Brevo, with rate-limit handling
- Arabic-first bilingual interface with right-to-left layouts
Hard parts and decisions
Trust before access
New institutions are reviewed against uploaded proof before staff can operate, and staff join by invitation rather than open sign-up.
AI without hidden costs
The study assistant uses the user’s own provider key, and each provider’s pricing and limits are linked before connecting.
Where it stands today
Live applicationPublicly deployed on Vercel. The features below were verified on 11 November 2026 from the live application’s production client and its API surface; signed-in flows were not exercised during that check, and no institutional adoption figures are claimed.