Project status

AILearn is an API-first course marketplace: one shared backend serving a Next.js web app today and a Flutter mobile app later. The public catalog, search, free enrollment, the course player with progress tracking, certificates (with downloadable, on-demand-rendered PDFs), profiles, and the full tutor panel (courses, curriculum, analytics, earnings, reviews) all run on the real database; the chess-coaching mini-app is fully live. The admin panel — site KPIs, member management (roles, tutoring, suspension), course moderation, categories, and enrollment oversight — now runs on the real database too, with an owner-vs-admin guard split; self-serve 'Become a tutor' is live. Video streaming is live too (Cloudflare Stream — tutors upload straight from the browser, a signed webhook confirms readiness, and enrolled students watch adaptive playback, verified end-to-end against a real Stream account). Quizzes are live too: tutors author multiple-choice questions per lesson, the server grades attempts (70% pass mark, capped retries), and graded quizzes gate lesson completion and the certificate behind a real pass. The student quiz player takes them one question at a time — a reusable, mobile-style runner (progress bar + graded score card, split into components ready for the Flutter surface); pnpm db:seed-quiz fills the demo lesson so it is playable. In-app notifications and transactional email are live: enrollments, receipts, and course completions fan out to a durable notification feed (with an unread bell) plus a best-effort email, provider-agnostic behind a zero-secret log adapter until a real email provider is chosen. Every slice is verified by a one-command test pyramid (pnpm test:all — unit tests, data audits, and real-HTTP journeys on seeded fixtures). Paid checkout is now built end-to-end on Razorpay — a student pays by UPI, card or netbanking in a popup on our own page, and only Razorpay's signed webhook unlocks the course — with the provider still swappable behind one adapter file, and prices in rupees. Real payments have gone all the way through — money captured at Razorpay, a signed webhook, and the course unlocked. The live site briefly took money without unlocking anything, because the webhook secret did not match; that is fixed, and settlement no longer rests on any single signal — if a webhook is ever refused or lost, the order page asks Razorpay directly and settles the payment the same way, and if the payment window closes or reports a failure, the page checks with Razorpay before telling you anything about your money, with the Pay button locked while it checks so a wrong 'failed' message can never lead to paying twice. Checkout now settles itself even with no browser present: a site-wide watcher re-checks the buyer's unfinished payments whenever they visit, return to the tab, or come back online (and quietly on a slow timer), a Vercel cron sweeps every site's unfinished payments every 10 minutes so even a buyer who never returns gets their course (plus receipt and push), a payment that lost its Razorpay reference in a crash is recovered by receipt, a declined-then-retried order still settles when the retry captured, and never-paid checkouts are honestly marked abandoned after 24 hours — only on Razorpay's positive say-so. Every payment is also fully investigable now: each one leaves a permanent event trail in our own database (who acted, what happened, why anything failed — outliving Vercel's one-day logs), the owner gets throttled alert emails for the scary cases (webhook refused, orphan webhook, Razorpay's API down, refunds) plus an at-most-daily digest sent only when something needs eyes, and site staff have their own Payments page in the admin panel that shows the day's health at a glance, opens any payment's full history, and asks Razorpay about it on the spot. On top of that the site owner now has a payments audit page where every payment ever made explains itself in plain words — whether it is healthy, or whether someone paid and never got access — with the next step spelled out, and our own test payments flagged so they never masquerade as a customer waiting. Anything already dealt with can be closed with a note, which quiets the daily email without hiding the record. And when a payment does need investigating, it is now one action: every row on the staff Payments page has an Investigate panel — the verdict in plain words, our status beside the provider's live answer, the webhook deliveries about that payment, and the full history, copyable as one JSON bundle — and the identical story is a single terminal command, pnpm payments:diagnose. Mobile readiness (M8) is well underway: the whole /api/v1 contract is self-describing — a machine-readable OpenAPI document at /api/v1/openapi.json (for typed Flutter/codegen clients), a human-readable reference at /api-docs, and a hard JSON-only guarantee (even unknown API paths answer structured JSON, never an HTML error page) — and the Flutter app itself now runs the core learner loop: slices 1–5 have shipped (sign-in + catalog browse, free enrollment + course player, certificates, search & filters, and profile editing), and a five-tab bottom-navigation milestone on top of them — Home/Explore, Enrolled, Wishlist, Progress, and Settings — adds a light/dark/system theme toggle, an in-app quiz player, and a saved-for-later Wishlist backed by a new GET/POST/DELETE /api/v1/wishlist, each verified against the live backend — and the web app now carries the same Wishlist (a /wishlist page plus a ♡ toggle on every catalog card and course page), so a course saved on the phone is there on the web. The phone can now BUY a course too: Buy now opens the same Razorpay checkout in the phone's browser, and an in-app Order-status screen confirms the truth from our ledger (asking Razorpay directly when needed) with the same honest wording as the web — plus a Purchase history screen in Settings and an every-app-resume sweep that rescues a purchase even if the app was killed mid-payment. That flow is green in tests and has been walked end to end on a real phone (with the no-money test provider): buying, a failed attempt retried to success, and the purchase landing in My Learning. Still open: one real-rupee payment against production, a real refund pass to close out checkout (M6), and white-label branding.