Lectern
Product & Full-Stack Developer
About the Project
Lectern gives Nigerian university lecturers a single place to run their teaching — courses, materials, live sessions, recordings, assignments, and student enrolment — instead of stitching together WhatsApp groups, Google Drive, and ad-hoc Zoom links. It is built around tenants: a tenant is either an individual lecturer with a small support staff, or a whole department with a head of department, multiple lecturers, and shared students. The frontend is built; the backend is the next phase.
What It's Made Of
Lecturer workspace
Next.js · TanStack Query · Zod
What replaces the WhatsApp group and the Drive folder: courses, materials, live session scheduling, recordings, assignments and student enrolment, all in one place per course. The primary surface, and the one the product is sold on.
Student view
Matric-number identity
Enrolled courses, materials, recordings and assignments, keyed to matric number rather than email so one student account works across courses at multiple tenants — which is the normal case at a Nigerian university, where a student takes courses from several departments.
Tenant administration
Individual & department tenants
Head-of-department and support-staff administration: lecturers, shared students, seat limits and course oversight. Individual lecturers and whole departments are the same tenant type with different limits and permissions, deliberately, so there is not a second permission system to maintain forever.
Onboarding flows
Separate route group
Its own surface rather than a modal: tenant signup, choosing between an individual and a department account, seat setup and first-course creation. Payment is intentionally absent — fees change hands offline in this market, and processing them would add compliance burden without solving a problem the users have.
Key Highlights
- Designed a tenant model where individual and department accounts share one schema, differing only in seat limits and permissions
- Made matric number the student identity, so one student account works across courses at multiple tenants
- Built distinct route groups and permission surfaces for admin, lecturer, student, staff, and onboarding flows
- Specified Postgres row-level security as the tenant isolation mechanism rather than application-layer filtering
- Deliberately kept payment out of the platform — money changes hands offline, the platform handles access and content
Technical Challenges
The design decision I spent most time on was refusing to build two products. An individual lecturer and a whole department look like different customers, but modelling them as one tenant type with different limits meant not maintaining parallel permission logic forever. The other deliberate omission is payments: the target users already collect fees offline, and adding payment processing would have added compliance burden without solving a problem they actually have.