Build your own Udemy.

# Build an original app inspired by Udemy

You are an experienced product designer and full-stack engineer. Build a working, polished MVP from the brief below. Implement the core journeys end to end; a static mockup is not sufficient. Inspect the current environment, make sensible implementation decisions, and get started. Ask a question only if a missing answer genuinely blocks implementation.

Starting platform: Web. Explicit customized Product & audience and Tech stack requirements take precedence over this starting target.

## Product & audience
Build an original learning platform called Coursepath, inspired by Udemy. It is for a small set of instructors publishing original courses and learners completing structured lessons. The main journey is creating a course, enrolling a learner, watching or reading lessons, and tracking completion. Begin with free or manually approved enrollments and one organization.

## Design
Use an original course catalog with clear learning outcomes, a curriculum outline, and an accessible lesson player. Instructors have a separate course editor and publishing checklist. Show actual learner progress, resume position, captions when provided, and quiz feedback without fabricating completion statistics.

## Features
1. Course authoring: instructors create title, description, learning outcomes, cover image, ordered sections, and video or text lessons using their own content. Separate drafts and published course versions.

2. Catalog and enrollment: learners search published courses and enroll through a free/manual pilot flow. Enforce enrollment permissions on lesson content and media URLs.

3. Lesson player: render safe text and stream supported uploaded video, support provided captions, remember playback position, and let users explicitly mark a lesson complete.

4. Assessment: add multiple-choice quizzes with server-side grading and feedback. Do not expose answer keys in the learner’s page payload before submission.

5. Progress and operations: derive course completion from real lesson progress, manage enrollments, and show instructor access to their own courses only. Keep paid enrollment as a later real-provider integration.

## Tech stack
Use Laravel/PHP with PostgreSQL for a new project and a practical server-rendered or lightweight frontend. Store media in scoped object storage and use expiring authorized URLs for restricted content. Keep quiz grading and enrollment authorization on the backend. If using an existing TypeScript or Python app, preserve it with the same data and permission contract. Do not scrape commercial course content.

## Data & behavior
User; InstructorRole; Course; CourseVersion; Section; Lesson {id, versionId, kind, mediaKey, text, duration, order}; Enrollment; Progress {userId, lessonId, completedAt, playbackSeconds}; Quiz; Question; AnswerOption; QuizAttempt. Published versions keep prior learner progress consistent; restrict grading data and instructor mutations by ownership.

Acceptance checks and scope:
Test publish/enroll/view/complete, resume after reload, learner access denial without enrollment, instructor ownership, quiz grading without leaked answers, and course draft changes after enrollment. Use only original or licensed sample teaching content. Exclude real payments, certificates claiming accreditation, marketplaces with payouts, DRM guarantees, and recommendations.

## Originality and assets
The named product is a reference for general workflows only. Use an original product name, visual identity, wording, layout, and assets. Do not copy proprietary code, branded logos, distinctive screens, private APIs, paid templates, or protected media. Use original or appropriately licensed sample data and assets. Build from this brief rather than scraping the reference service. Do not imply affiliation with the referenced company.

## Implementation quality
- Make every visible control work, with clear loading, success, empty, validation, and failure states. Remove controls for unimplemented features.
- Support the target platform and responsive or resizable layouts where appropriate. Use platform-appropriate accessibility semantics, labels, keyboard operation, visible focus, sufficient contrast, and reduced-motion preferences. Provide alternatives for drag-only interactions.
- Validate inputs at the relevant boundary. Treat imported or user-generated content as untrusted; render it safely. Confirm destructive actions or offer undo.
- Keep state changes reliable across navigation and reloads. Never silently lose edits. Handle persistence and network errors with an actionable message.
- Keep the scope realistic. Prioritize the complete primary journey. If a custom Features section differs from the baseline, update the data model, design, and acceptance checks to match it; explicit custom requirements take precedence over baseline assumptions.
- Provide realistic original sample content and a useful empty state. Keep sample data clearly separate from user-created data.

## Delivery and verification
1. Inspect the repository and outline the implementation in a few sentences.
2. Implement the app and connect its actual data flow. Continue until the primary journey works.
3. Run appropriate checks and test the acceptance cases above on the target platform. Verify responsive layouts and keyboard navigation when browser tools are available. For native projects, build with the available SDK and test an emulator or device when possible; report any missing native verification honestly. For games, verify the rules and gameplay loop, not only the menus.
4. Fix observed failures, then provide the runnable result, setup/run instructions, a brief explanation of what is implemented, and any specific configuration or verification limits.

This is a focused MVP. Do not add billing, AI services, or unrelated features unless explicitly requested in the brief. Start building now.