The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
very hard working
Just finished building this modern, responsive e-commerce dashboard using React, HTML, and CSS! Featuring dynamic product grids, category filters, and seamless cart management. Open for web development projects and custom UI designs! 🚀
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
Twenty-five years of credits, finally on a website that looks the part.
Just take a look at what kind of web we create ✨👇
Reflection of the brand history with taste, precision, and premium branding.
Scroll responsibly: https://productionportugal.com 😉🔥
Wow! Nice setup 🎥
Can a designer push Lovable as hard as any design tool?
Yes, and the method is simpler than you'd think. Three steps. I'll show each one on real slides from this challenge.
First, why I'm back. I sat out the last couple of challenges: I needed a real break, and other projects needed me more. I hadn't opened Lovable in a bit over a year. When this one landed, I thought: let's see if a designer can take it to the limit, the way I do with every other tool. So far, it's holding.
The client is Endorphin, a run club in Turin. Every Thursday, 19:00, under the Arco del Valentino, free, any pace. Here's the method.
1. Design every state before you prompt. Default, hover, spots left, full, waitlist, booked, past. Look at the third slide: each chip is a different state of the same event, "You're in", "23 left", "31 going". If a state isn't designed, Lovable guesses it. So I never leave it a guess.
2. Write the prompt like a spec. Real sizes, real colors, real timings. Mine says things like: the slide takes 480ms, easing cubic-bezier(0.2, 0.8, 0.2, 1), no bounce. Then I attach the Figma export of that exact state and write "match this pixel for pixel". That's how the calendar on the last slide got its hover: the cell lifts, a preview card shows cover, time, place and spots left, and Book sits right there.
3. One prompt at a time. I send a piece, compare it with my board, and only then send the next. The phone view on slide two came out that way: a booking sheet with two fields and one line, "No account. No password. Just show up." Above it, a molecule where every dot is a moment from a Thursday.
The first slide shows the result of all three: the whole night as single cards. Price, distance, time, meeting point, crowd. One idea each.
The tool is only as sharp as the brief you give it.
If you've built with an AI tool: where did you hit the wall first, design or logic?
great designs, all made in lovable right?
I built NIGHT.OS, an interactive haunted operating system that slowly becomes aware of the person using it.
What begins as a clean, futuristic desktop interface gradually turns into a possessed UI. A mysterious creature appears, watches and follows the cursor, manipulates interface elements, and eventually takes control of the system. The experience ends with a glitch-driven reveal before resetting back to the seemingly normal desktop.
I used Rive CLI to establish the interactive UI structure and RML workflow, then refined the visual direction, character, motion, interactions, and transitions in Rive. I also used GPU Canvas effects to create atmospheric distortion, CRT-style glitches, flickering light, fog, and visual reactions around the creature.
The goal was to make Halloween feel less like a collection of spooky graphics and more like an interactive story where the interface itself becomes the haunted character.
A clean desktop that slowly turns possessed is a good way to build dread. What was the first sign you chose to show the OS becoming aware of the user?