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
I thought the next step would be better software.
I started working with a client in a very niche professional-products sector, first as a technical writer. My background with Chinese documents, test reports, photos and files that need basic electrical knowledge was what they needed.
Then they asked me to build their spec sheets. I expected specialized software, or at least Figma or Adobe. Instead, all their spec sheets are built in PowerPoint.
Two things changed my mind:
PowerPoint is often seen as a low-value tool. It isn't, if you know how to approach it.
The tool matters, but what matters most is knowing your field: what a spec sheet has to say, to whom, and in what order.
Have you ever had to do serious design work in a tool you didn't expect to use?
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
I’m currently open to work in UI/UX Design & Frontend Development. 🚀
My process starts with understanding the problem, researching users, and mapping their journey. Then comes wireframing, shaping the visual experience in Figma, prototyping, and turning designs into responsive code.
From the first question to the final pixel, I believe every design decision should have a purpose.
I’m ready for the next opportunity to turn ideas into meaningful digital experiences.
#OpenToWork #ProductDesign #UIDesign #UXResearch #Figma #FrontendDevelopment
A five step strip from research to Figma to code is a clean way to show you cover the full chain, and the green and blue in open to work make a readable hook. Blunt critique: this card describes the process every designer follows. The thing a hiring manager wants is one outcome,...
When it comes to design, every visual choice made should serve a purpose. A simple GIF with sequential icons should be able to tell a story.
When determining clarity, I ask myself, "If I share assets without context, can at least 7 out of 10 people understand what it’s communicating? Can they grasp the fundamentals (what it's about and who it’s for) without needing further explanation?" A bonus is how well it invokes curiosity.
If so, good. This question helps me decide what assets are included in my work based on how it fits into the project's story.
Good intentional design allows visuals to speak in the absence of words.
I like this approach. If a visual can communicate the idea without needing extra explanation, it makes the design much more effective and memorable.
1 designer + base44 + 3 days without proper sleep = Overdrive🤍
A job tracking system for a car repair shop.
✱ One board showing every car on the floor, where each one stands and what’s holding it up.
Add a car, assign the work, and from there it tracks itself- what’s late, which parts have landed, who’s in today. Visit history, receipts, and a widget that tells you the next free slot you can offer someone.
Three days. Not smooth ones. But it’s live❗️
✱ Now the why, because none of those features were my idea.
My client owns the shop. Four mechanics, up to seven cars a day, no front desk. For months he’d complain about the same stuff whenever we talked: parts he ordered and forgot about, mechanics starting one car and getting pulled onto another, people asking when they can bring a car in and him not knowing what to say.
It was never a brief, of course, he was just talking. But one day I asked him properly: what do you need to see the moment you walk in?
✱ He said four things. And those four made sense as widgets, naturally.
Nothing on the job board gets typed in by a person. For example, a car shows as blocked because the mechanic who has it is off today- the board works that out and writes the reason on the card. He doesn’t walk around the shop asking anyone, he can just see it now.
✱ And the part nobody puts in these posts😅
→ It is my first time ever (!) using Base44 and I started without a paid plan, so I had a hard limit on how many prompts I got.
You can’t iterate your way to something like that. Every prompt had to arrive already correct, which meant almost all of the work happened before I typed anything. I designed every screen and every state in Figma first, then worked out exactly what to ask for and in what order.
I spent hours with Claude and Google figuring out how to phrase things, what would break, what to check before changing anything. I’d write a prompt and then throw it away and write a better one, because a wasted prompt cost more than the time did 🤷🏻♀️
Honestly, the constraint made it better. No aimless tinkering. Every change had a reason before it was made, and I still got every core feature I wanted in there.
✸Research: https://miro.com/app/board/uXjVEWOXy9k=/?share_link_id=813311021448
✸Walkthrough: https://www.loom.com/share/69ffa2d58ca24e7bb10676be5173cdc2
✸Overdrive live demo: https://overdrive-shop-flow.base44.app
✸X thread: https://x.com/gurvchler/status/2114517480152740121?s=20
✸LinkedIn post: https://lnkd.in/p/dysRmrNw
Well done!
And love the "no proper sleep" detail - sounds so familiar 😂