Molearn
An education platform connecting students and tutors, allowing tutors to sell educational videos and books.
- Next.js
- TypeScript
- Prisma
- PostgreSQL
- NextAuth
- Stripe
- Zod
- Tailwind CSS
01 · Context & Product
The Problem & Product Solution
Tutors create valuable educational content — recorded lessons and written material — but have no simple way to package and sell it to students.
Students looking for specific help end up scattered across chat groups, one-off links and unorganised file shares, with no single place to buy, own and revisit material.
Molearn brings both sides into one product: tutors publish educational videos and books, and students browse, purchase and learn from them through a single interface.
The platform handles accounts, content browsing, purchases and content delivery, so a tutor can sell and a student can learn without leaving the product.
My Role & Ownership
Product design, frontend engineering, API integration, authentication and database layers.
02 · Technical Architecture
How It's Engineered
Next.js with the App Router and TypeScript, styled with Tailwind CSS. Server components carry the data-heavy pages so the client bundle stays small, while interactive pieces — forms, checkout, account views — stay isolated client components.
Prisma as the data layer over PostgreSQL (Neon), with typed models for users, content and purchases. Schema changes are versioned through Prisma migrations instead of manual SQL.
NextAuth with credential-based sign in and bcrypt password hashing, wired to the same user records the rest of the product reads from.
Stripe is integrated on both client and server so a purchase is confirmed on the server before access is granted — the frontend is never trusted to mark an order as paid.
Zod schemas validate input at the API boundary, and secrets live in environment variables — nothing sensitive ships in client code.
03 · Problem Solving
Engineering Challenges & Solutions
Two very different users — students and tutors — share one product without the interface becoming confusing.
Role-aware navigation and separate account views, so each user only sees the actions that matter to them while both sides share the same design language.
Digital content must only reach paying students, without locking out legitimate owners.
Access is decided server-side from purchase records in the database, never from client state, so a refresh or shared link cannot bypass payment.
Marketplace flows span multiple pages — browse, buy, access — and easy to drift out of sync.
A typed API layer shared between routes and components, so the same contract drives the UI and the server responses.
04 · Scope
Shipped Features
Implemented and working in the codebase today.
- Student and tutor accounts with sign up and sign in
- Browseable library of educational videos and books
- Video and book content pages for purchasing and learning
- Stripe payments for purchases
- Tutor-side content publishing flow
- Protected account areas for signed-in users
- Responsive interface across mobile, tablet and desktop
05 · Craft & Quality
Interface, Responsiveness & Performance
Interface Design
The interface is built around content discovery: clear cards, readable metadata and obvious calls to action so a student can go from browsing to learning in very few steps.
Typography and spacing do the heavy lifting instead of decoration, which keeps dense catalogue pages scannable on small screens.
Every flow — browsing, purchasing, managing content — was designed mobile-first, since most students will arrive on a phone.
Responsive Behaviour
Mobile-first layouts throughout: catalogue grids collapse to single columns, navigation moves into a compact menu, and content pages prioritise the lesson itself.
Touch targets, spacing and type scale were checked at 320px through to wide desktop so nothing overflows or becomes untappable.
Performance & Accessibility
Server components for content-heavy routes keep client-side JavaScript down.
Next.js image handling and lazy loading keep media-heavy pages from blocking first paint.
Fonts and scripts are minimised — the platform loads content fast even on slower mobile connections.
06 · Result & Reflection
Outcome & Takeaways
Molearn is live in production and continues to be developed, with the codebase open on GitHub.
It stands as the clearest example of my end-to-end product work: interface, authentication, payments and data model shipped as one working product.
Key Engineering Lessons
- Marketplace products live or die on role clarity — knowing exactly which screen belongs to which user removes entire categories of confusion.
- Doing payment and access control on the server from day one is far cheaper than retrofitting it later.
- Typed data contracts between the API and the UI catch a surprising share of bugs before they ever reach the browser.