Triple Take Anime

Overview

Designed and engineered Triple Take end-to-end: a public discovery site for readers and a private multi-host studio for takes, comments, and episode discussion. Solo full-stack build — auth, data model, studio workflows, and anime API integrations on a shared Next.js + Neon stack.

The problem

Anime discovery is flooded with generic lists. What’s missing is opinionated, human recommendation from people you trust — and a real publishing system for hosts that isn’t a generic CMS bolted on after the fact.

The solution

One product, two intentional surfaces: public discovery and discussion up front; a secured host portal behind it for real publishing. Full-stack ownership from schema and auth to studio UX — not a marketing site with a rented CMS.

My role

Founder · Product Design · Full-Stack Engineering

Process

Defined the cousin-host product model, then split surfaces across domains (ttanime.com / host.ttanime.com). Built the backend and ops layer first-class: Auth.js + WebAuthn passkeys, Prisma/Neon data, host studio for watching desks and takes, and catalogue sync from Jikan/AniList — so posting habits match how the cousins actually watch.

Key features

• Public catalogue and cousin-led discovery
• Host studio on a separate domain
• Passkey auth for hosts
• Watching desks and takes publishing
• Anime metadata via Jikan / AniList

Tools and technologies

Results

• Shipped dual-domain product (public + host studio)
• Live at ttanime.com with solo full-stack ownership
• Multi-host publishing with passkey auth and Neon-backed data
• Studio workflows for takes, watching desks, and host security

What I learned

• Splitting public and host domains clarified permissions and habits better than one overloaded admin.
• Passkeys reduced friction for a small host team that lives on phones as much as laptops.

Status and next steps

Keep iterating catalogue discovery, host tools, and the cousin voice that makes the product different from generic list sites.