Day 1 of my 100 days of components 🧩

I saw a post in the Framer community about “100 days, 100 components” and I couldn’t stop thinking about it. So I’m doing it too: one custom Framer component at a time, for 100 days or until I land my next client, whichever comes first.

Day 1: Scroll Frame. A border around the viewport made of four marquee strips that move with your scroll and circulate around the edges. Each strip is a sequence of cells you can edit: wide, condensed and script text, pills, icons, your own logos, and inverted solid blocks.

I’m open for Framer, UX/UI and Shopify projects. See my work at jessicamena.com and let’s talk.

100 days of custom Framer components is a great challenge, and the scroll frame is a strong start. Looking forward to following the series.

I built this to see if I could make a point-cloud museum that moves with your mouse and still stays smooth at 60 FPS without any framework. No libraries. No build steps. Just Canvas2D and a bunch of tiny floating lights.

WHAT I WAS TESTING: I was testing how well I could keep point-cloud rendering alive under constant user motion while keeping the frame rate locked at 60. The system had to handle hundreds of thousands of points updating every frame, and I had to make sure the browser didn’t stutter from garbage collection or event throttling.

THE TECHNICAL SIDE: Everything runs in the browser with Canvas2D. No WebGL. No Three.js. No external dependencies. I wrote custom shaders with GLSL to color and animate the point clouds. I hand-tuned the event loop to avoid frame drops during mouse moves, and used requestAnimationFrame with manual frame pacing to stay at 60. Memory is allocated per object and recycled on demand. No global state leaks. No third-party tracking.

WHAT I LEARNED: The key was not making the math too tight or too loose. Too tight and the browser would freeze. Too loose and the frame rate would drop. I learned to profile frame times, adjust point update rates based on user velocity, and use a simple debounced event handler to keep mouse movement from overwhelming the system. It runs at 60 on an old laptop, and feels buttery on a mid-tier machine.

TRY IT YOURSELF: Open it in your browser, it's hosted live on my JSFiddle. Move the mouse around. Watch how the clouds react. No lag. No freeze. No framework.😊

Professional, nice work👍