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
What we've shipped. 🖤
60+ products since 2022 — AI agents, SaaS, mobile apps & marketplaces.
See the full portfolio → demzagency-portfolio.created.app
Hello! I would like to collaborate with you. I am a Senior Mobile Engineer with 9+ years of experience in software development. I have a strong background in Java, Kotlin, Android development, React, Node.js, Python, Go, AWS cloud services, Kubernetes, and modern CI/CD practices.
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
Challenges
View all
Related posts
How I Actually Build Websites — From Inspiration to Final Build.
I don’t start with a blank screen. I usually start by exploring Pinterest to find visual references, layouts, interactions, and design ideas. Then I bring the reference into ChatGPT, explain what I want to build, and use it to turn the rough idea into a much clearer development prompt.
From there:
Pinterest → Reference → ChatGPT → Refined Prompt → Antigravity → Manual Refinement → Final Website
I give Antigravity the reference image + refined prompt, let it handle the first implementation, and then take over manually to fix the details that AI doesn't get right — spacing, responsiveness, interactions, typography, animations, and overall polish. AI speeds up the process.
But the final quality still comes from the decisions and corrections I make.
This is how I combine design inspiration, AI-assisted development, and manual frontend work to turn an idea into a real website.
Great explanation....❤️👌
As an AI developer, I like products where the workflow is clear to both sides. For Lidspace, I built a two-sided product where builders list their stack and neighbourhood, while brands discover relevant local evangelists through a map and filters. I keep decisions visible, integrations tested, and approval points explicit when automation is involved. If you need a focused product built around a real user flow, message me.
One thing I’ve learned from vibecoding: don’t break what already works.
When I’m building a new feature, I usually create a separate test area instead of modifying the live version directly.
If the current version is v3, I’ll experiment with v3.1 there first, test it, iterate, and only move it into the main app once it’s stable.
For bigger rewrites, I keep both versions locally and compare them side by side. The old one stays untouched while I work on the new one.
It’s a simple workflow, but it saves me a lot of headaches when AI starts losing context.
There are many ways to approach this. This is just the one that works best for me.
What’s your workflow when building with AI?
The isolated v3.1 workflow is such a practical guardrail—especially when AI starts drifting. Comparing the stable and experimental versions side by side makes iteration feel much safer.