Labs is a personal project I’ve been developing on my own. It started as an open space to sharpen my skills in frontend development, creative UI, animation and 3D integration. Over time, it also became a playground for visual expression and stylistic exploration.
The project is not bound to any deadline or delivery. I use it to iterate freely, test technical ideas, and build visual components that reflect an aesthetic I’m personally drawn to. The audience is undefined, but the project is public and accessible. Its main value lies in the creative process and technical exploration it enables.
Problem and Context
Labs doesn’t solve a functional problem in the usual sense. Instead, it responds to a personal need for a space where I can combine design sensibility with frontend engineering. I wanted a project that would reflect my taste for visual rhythm, structure and motion, while giving me the flexibility to write code without constraints.
The visual direction mixes three styles:
→ A parametric approach : geometric clarity, modulation, and rule-based compositions.
→ A playful and colorful style : vibrant interactions, friendly shapes, and smooth microinteractions.
→ A ghost data aesthetic: glitch elements, scattered particles, deconstructed interfaces.
The project has gone through many iterations. I’ve rebuilt the base several times to make it stable and modular enough to support dozens of small experiments. At the time of writing, I’ve listed 124 component ideas, prioritized in Notion based on complexity, development time, and relevance. I draw inspiration from websites I’ve been observing and saving for years.
Process and Choices
The foundation is built with Next.js and TypeScript. Navigation between prototypes is dynamic and animated with Framer Motion. A global context provider ensures that the base structure and shared state are not reloaded on every route change.
Each component is a self-contained visual or interactive unit, published when I’m satisfied with the result. I do not follow a timeline or publishing schedule. The logic is simple: experiment, build, evaluate, release.
I use Tailwind CSS for styling, GSAP and Framer Motion for animation, and the Three.js ecosystem (including several Poimandres tools) for 3D integration. Most interactions are prototyped directly in code, without passing through Figma or any design tool.
This is a solo project that grows through informal iteration and personal curiosity. I write components in isolation, revisit them later, and improve them when needed. I sometimes refactor the layout engine or animation flow, but only when a real constraint emerges.
Results
The project is online at labs.maximelbv.com. The homepage acts as a portal to the different components, each of which is a small, self-sufficient piece of UI or motion design. Some are purely visual, others are interactive.
There is no direct metric of success, but the project plays an important role in my portfolio. It demonstrates my range in frontend development, my attention to timing and visual flow, and my interest in spatial and animated interfaces.
Takeaways
Labs gave me more practice with motion handling, component structuring, and using 3D in the browser. I worked repeatedly with libraries like Three.js, GSAP, and Framer Motion, and learned when each was most appropriate depending on the context.
It also allowed me to explore a visual direction that mixes ordered structures with more abstract elements. I had to make choices between visual intent and code clarity, and I tried to keep the implementation clean even when the goal was experimental.
The project is still ongoing. I add new components when I want to test something or try out an idea. It’s become a long-term space where I write code and build interfaces that reflect my visual preferences.
