Frontend Frameworks

I have working familiarity with multiple front-end frameworks. I understand component-based thinking, modern UI patterns, and front-end implementation logic. I do not over-identify with any single framework.

My stance

• Prefers using the right tool for the job
• Treats Next.js as my default
• Stays comfortable enough across frameworks to move if needed
• Cares more about shipping good UI than about framework politics

Where it shows up in my work

• Duodode products and client builds
• Component systems that mirror Figma libraries
• Interactive UI using Framer Motion and GSAP
• Full-stack apps connected to Supabase through Next.js
• Deployment through Vercel

Why this stance fits me

I am ROI-driven. Framework identity is low-leverage. Understanding the underlying model (JavaScript, components, rendering, state) is high-leverage. I stay focused on what compounds.

How it connects to my design work

Frameworks are where Figma becomes real product. Clean component thinking lets my design system translate cleanly into code without diluting my intentional, timeless, consistent standard.

Related

Next.js · JavaScript · HTML · CSS · Framer Motion · Interaction Design