AceBuddy — shipping frontend to real students.

Built the marketplace, the onboarding flow — invite-code validation, OAuth sign-in, and email/password with email verification — the notes editor (Markdown formatting, embedded images, math formulas), the collections page, and the contributor and admin surfaces.

Frontend-primary for the whole contract, but not frontend-only: touched backend when a change on that side was the actual fix, rather than working around it from the client.

Key technical patterns

• Shipped the marketplace behind feature flags instead of commenting out in-progress code — kept main always deployable while features landed piecemeal
• Adapted the frontend's auth handling when the team moved access tokens out of persistent storage and into memory

Shipped to real students, in continuous production use — the marketplace, onboarding, and notes surfaces built here are what students touch first and most often.

Feature flags did more work here than any single line of code — shipping incomplete features behind a flag instead of commenting them out kept the team unblocked and main always deployable, which mattered more on a fast-moving product than getting each feature “done” before it merged.