AI summary by TwinMind

Zoom Picked My Stack ๐Ÿ‘€

Theo - t3โ€คgg

16m 29s

T3 Stack Selection at Zoom

  • Zoom chose T3 stack for SDK reference apps to empower developers
  • Goal: create reference apps across different verticals as starting points
  • Aon (community member) moved to Zoom to help with SDK development
  • Focus on developer tools for integrating Zoom's WASM servers into applications

Technology Stack Decision Process

  • Primary consideration: usefulness for maximum number of developers
  • Rejected approaches:
    • Rust for frontend (too niche audience)
    • Custom implementations (greater dev barriers)
  • Chosen approach: open source libraries over building from scratch
    • Allows developers to read library docs instead of custom source code
    • Enables time allocation toward building more vertical-specific apps

Core Technology Choices

TypeScript Selection

  • Chosen over JavaScript for type safety
  • Benefits:
    • Simplified writing/managing apps within team
    • Seamless collaboration on shared frontend/backend features
    • Immediate feedback on package changes via type errors
    • Essential for library developers
  • Considerations:
    • Adds syntax complexity
    • Can intimidate unfamiliar developers
    • Code still reads like JS, extra syntax can be skipped

React Framework Choice

  • Still most popular web framework/library
  • Simple programming model with component composition
  • React ecosystem most willing to adopt new tools
  • Modular space culture (Unix-style adding/removing parts)
  • Perfect for SDK examples

Backend Language Constraint

  • Limited backend choices to TypeScript
  • Reasoning: audience wouldn't need to learn another programming language
  • Target developers are frontend-leaning when exploring video SDKs
  • Backend examples should be accessible to frontend-focused developers

Next.js Selection

  • Chosen for full-stack React development
  • Abstracts complexity in web tooling (frontend + backend)
  • Provides solid foundation for reference apps
  • Decided to stick with Pages router over newer App router
    • Pages router still well-supported and default in many tools
    • App router more flexible but has more foot guns
    • Pages router easier for newer teams once you avoid problematic features

T3 Stack Components

Styling Solution

  • Tailwind CSS: recommended default styling approach
  • Shadcn/ui: UI components to save development time
    • Accessible out of the box
    • Allows easy theme customization for branding
    • Components owned as part of source code

Authentication

  • NextAuth: current T3 stack default option
  • Alternative options mentioned: Lucia, Clerk
  • NextAuth chosen for ease of setup within create-t3-app

Database and ORM

  • PostgreSQL: chosen as most commonly used open source database
  • Prisma: current T3 stack default ORM
    • Keeps DB queries type-safe
    • Note: should potentially move to Drizzle (faster, more modern)
    • Prisma still acceptable choice

API Layer - tRPC

  • tRPC: "star of the show" that brings everything together
  • Benefits:
    • Blurs line between frontend/backend in best way
    • Team initially apprehensive but quickly fell in love
    • Makes API layer design effortless (normally requires dedicated teams)
    • Smoother, faster, easier than GraphQL
    • Built on React Query with TypeScript inference
    • Command-click navigation from frontend calls to backend code
    • No explicit type definitions needed - uses Zod validation + TS inference
    • Real-time type checking without build steps
    • Uses TypeScript as API service layer and documentation

Development Experience Benefits

  • Individual work on same features across full stack
  • No worry about breaking others' code
  • Effortless collaboration
  • Easier code reading and navigation
  • Simplified code reviews and major changes
  • Modern tools that balance developer impact with ease of use/maintenance

Community and Documentation

  • Large community building with these tools
  • Comprehensive T3 stack documentation available
  • Great explanations and guides for each component
  • Strong open source contributor community

TwinMind

Get summaries like this for your own meetings

TwinMind takes notes in the background during meetings, lectures, and calls, then writes the summary for you.

Free plan to get started

No bot joins your calls

Phone, desktop & Chrome apps

Your next meeting, summarized like this

TwinMind listens in the background and turns meetings, lectures, and calls into searchable notes you can chat with. Start free.

Available on phone, desktop & Chrome

Your next meeting, summarized like this

TwinMind listens in the background and turns meetings, lectures, and calls into searchable notes you can chat with. Start free.

Available on phone, desktop & Chrome

Your next meeting, summarized like this

TwinMind listens in the background and turns meetings, lectures, and calls into searchable notes you can chat with. Start free.

Available on phone, desktop & Chrome