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
Have joined the lovable challenge but did not receive any promotional code for lovable what shall i do ??
same for me also
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
Hello! I'm working on my SVGator contest submission. I've created an animated perfume and skincare product template, but publishing a public template link requires a paid Pro subscription.
Is there an alternative way to submit my project for judging, such as sharing the project link privately along with a demo video?
I'd love to participate in the contest, but I'd prefer not to purchase a subscription just to submit my work.
Thank you for your help!
Pause this video and scan the code. It works. 📱
Most QR codes on posters and menus get ignored because nothing tells people what to do. So for the @SVGator × @Contra challenge I built SCAN ME, an animated QR template:
✅ A scan line sweeps the code
✅ The frame locks on and a check pops
✅ Every element is named, so you can swap the logo, QR, text and colors in minutes
One template, two brands: a bridal mehndi studio in Lahore and my software house, UI Trax.
The fun part: I built and edited it with @Claude through the SVGator MCP. With one instruction, it updated 17 elements in seconds. Then I edited it myself in the SVGator editor.
Which business should I make one for next? 👇
#svgatorchallenge #SVGator #Contra #MotionDesign #SVGAnimation #QRCode #AIAutomation #ClaudeAI #MCP #UITrax
https://on.contra.com/WFRk6n
If you want to ship fast in 2026-2027, the happy path can't be the whole review.
A happy-path demo gets a quick yes from the team. Then the questions start.
→ What shows while the image uploads?
→ What happens when the post fails?
→ Does retry work?
Nobody can see the states side by side, comment on them, or check the Figma file against the code.
So decisions get lost between design and the build, and customers are the ones who find the gaps.
This is the process I use:
Swim-lane user flows: the full feature, with each edge and error state documented.
The happy path and core edge cases built in code.
CPO and engineering review, with comments tied to each state.
Decisions and open questions logged in one doc the team and its AI tools build from.
The code and the file stay in step, and no one has to remember why the retry works the way it does.
Each review starts from what's already decided.
Customers get a product that holds up when things go wrong, they continue to build trust, and the app grows.
