689: Tyler Sticka on Colorpeek 2 and Awesome CSS

What It Covers

Tyler Sticka discusses rebuilding ColorPeek, a minimal color-sharing tool using vanilla web components, view transitions, and CSS nesting. The conversation explores modern web standards, AI browser skepticism, and maintaining focused side projects.

Key Questions Answered

• •Vanilla Web Components: Building with native web components, mutation observers, and abort controllers eliminates framework dependencies while maintaining scalability. ColorPeek uses only Color.js as a front-end dependency, demonstrating that web standards now handle complex interactions without React or Vue for many use cases.
• •URL-Based State Management: Storing application state directly in URLs enables instant sharing without authentication systems or databases. This approach serves designers and developers who need to quickly communicate color palettes across teams without creating accounts or managing cloud storage infrastructure.
• •Modern CSS Architecture: CSS nesting, container queries, and scope features reduce the need for strict naming conventions like BEM. Developers can write maintainable CSS with fewer classes and less protective methodology, as the language itself now provides better encapsulation and organization tools natively.
• •Side Project Monetization: Adding simple revenue streams like merchandise or tip jars covers hosting costs and validates community support. ColorPeek's shirt sales funded multiple years of domain fees, demonstrating that creators should overcome discomfort about monetization for sustainable open-source work.
• •AI Browser Limitations: Current AI browsers primarily route functionality through chatbots rather than innovating on browser capabilities. The focus on conversational interfaces ignores that users prefer clicking buttons for most tasks, and meaningful browser innovation requires multiple interaction pathways beyond text-based commands.