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
Before you sign off a design handover, open the Figma file from your own account and try exporting one frame.
View access can look fine until your developers need the assets. Ask for the file in your team's workspace, or a copy you own.
Solid tip. View only access looks fine right up until a dev needs the assets, so testing one export first is a good habit.
This is the kind of tip you only learn after getting burned once. View access looking fine right up until export time is such a classic handover trap, testing one frame is a great five-second insurance policy.
This one saves so much back and forth. Developers finding out at build time that they can't export a single icon is way too common.
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
A couple months ago I shared some thoughts on hand drawn logos, with a few images from a project I worked on. It wasn’t a finished case study and I didn’t even consider it among my strongest work.
It now has more than 50k views, 84 goats and 300 likes.
I’m very intentional about what I share and when, so this one caught me off guard. But it reminded me that we never really know how our work is going to land for someone else. As long as it’s thoughtful, sharing it is better than nothing. Keep going, keep perfecting your craft and keep showing your point of view.
And thank you to everyone who interacts and appreciates what I share. It never goes unnoticed. And of course to Contra for building a space where this kind of work finds its people.
I do wonder though, did this get traction because it was hand drawn in an era where everything is AI generated? Curious what you think.
lovelyy absolutely lovee it
How I structure every Figma file, so clients can review it and developers can build from it without a call:
• Cover: project name, status and the latest update
• 01 Sitemap + flows: what pages exist and how people move between them
• 02 Wireframes: structure before style
• 03 UI Desktop and 04 UI Mobile: what the client reviews
• 05 Components: buttons, cards, nav and forms with variants
• 06 Prototype: the clickable version for stakeholders
• 07 Dev handoff: specs, assets and notes for whoever builds it
Clients live in pages 03 and 04. Developers live in 05 and 07. Nobody has to dig.
How do you organize your Figma files?
This is the kind of structure clients never ask for but always thank you for. The clients live in 03 and 04 line is spot on. Do you keep the wireframes page around after the build, or do you archive it once the UI pages take over?
A tight deadline, a lot of screens, and an AI web demo to bring together.
For this Upwork project, I designed the UI in Figma using a consistent layout system to keep the work clear and deliver on time.
The client’s feedback says it best:
“Thanks to Mehdi, I was able to create the AI web demo product design very quickly. It wasn’t a small amount of work, but he put in the effort to meet an important deadline.”
Need help turning a complex web product into clear screens? Let’s talk.
More of my work: https://elkhatiri.com/
Congrats on the 5 star review Mehdi, nice win.