Hey everyone! I'm a computer science student who's gearing up to create a project inspired by AniList—a media tracker where users can manage their personal watch-lists, create profiles, and show off their collections to others. My goal here is more about learning and applying best practices than creating a polished product.
I have run my ideas through an AI model, and it suggested a tech stack that includes TypeScript for the language, Next.js for the front end, PostgreSQL for the database, Prisma as the ORM, and Rust for the backend using either Actix-web or Axum. I want to know if this stack is considered "standard" for 2026 or if it's too much for what I'm trying to accomplish.
As for core features, I plan on including authentication, a search panel, public/private profiles, and a tracking system where users can add, edit, or delete their watch statuses. Each item will have a dedicated page displaying details like where to watch, synopsis, and genre tags.
I'm also thinking about a few extra features like a comment section, a rating system, a recommendations panel, and possibly expanding to include movies and web series.
I would really appreciate your thoughts on:
- The tech stack
- Any features you think would be fun to add
- General tips for moving forward with this project!
3 Answers
Honestly, using Rust might be overkill for this project, and jobs in that area are not as common yet. Plus, Prisma isn't even designed for Rust, so that AI suggestion might've missed the mark. Consider sticking with TypeScript for the backend too. You'll be able to find more resources and support this way.
Your tech stack looks pretty solid for what you're aiming to do, but you might want to reconsider mixing Next.js with a separate Rust backend. This could complicate things for your first project. A full-stack Next.js setup with API routes might be simpler and still effective. As for features, you could think about adding import functionality from existing platforms like MAL or AniList, which would save users the hassle of manually transferring their lists. Start with basic CRUD operations for the watchlist, then expand from there—don't try to do it all at once!
I suggest scaling back a bit. It's crucial to nail down your concept first to see if it's truly viable. Think about the fundamental requirements of your app: how will you add movies, what metadata do you need, and how your lists will function. Start simple! Design your database and features according to your goals without overcomplicating things right from the start. Beginning with a straightforward setup will help you adjust and pivot as needed.
Related Questions
How To: Running Codex CLI on Windows with Azure OpenAI
Set Wordpress Featured Image Using Javascript
How To Fix PHP Random Being The Same
Why no WebP Support with Wordpress
Replace Wordpress Cron With Linux Cron
Customize Yoast Canonical URL Programmatically