How Should a Product Designer in Spain Show Private Figma Prototypes and Design Systems?
A product designer should turn each private Figma engagement into an approved project summary that states the problem, their role, the design-system or flow delivered, and the safest evidence a reviewer is allowed to open.
A Figma link is not a portfolio strategy: it may require access, reveal comments or future features, and say little about which decisions were yours. The public page should provide the missing map while approved prototypes, case studies, or shipped interfaces remain one click away.
What can a product designer show when the Figma file is private?
Show the product problem, your responsibilities, the constraints, and approved outputs while withholding source files, participant details, internal comments, and unreleased screens.
Describe whether you led discovery, interaction design, prototyping, usability testing, visual design, or system maintenance. If several designers contributed, make that boundary explicit instead of presenting the whole product as individual work.
Use a sanitised case study, a public shipped flow, or a prototype prepared specifically for review only when the client permits it. A card with a clear description and no link is safer than an access request to a confidential workspace.
- Public: shipped interface or approved case study.
- Conditional: redacted prototype prepared for review.
- Private: research recordings, roadmap screens, tokens, comments, and client files.
What is the fast way to organise the portfolio with IndieShow?
The fast way is to create one IndieShow card per meaningful product outcome and group shipped, active, and retired work by its current status.
Use the tag for the discipline or product area, the description for the problem and your role, and the project URL for the strongest approved evidence. Upload a neutral logo only when the client brand cannot be shown.
Lead with work that matches the role you want, not with the most visually polished screen. The live preview lets you check whether a hiring manager can understand the first projects without opening Figma.
Build your IndieShow pageClaim your handle, organise the projects in the editor, then review the $15 one-year and $30 lifetime publishing options in the dashboard.
Should a design system and its product flow be one project or two?
Keep them together when the system work supported one delivery, and split them only when the design system has its own scope, users, maintenance story, and reviewable evidence.
A token library, component documentation, and checkout redesign may be parts of one engagement. Three cards can exaggerate ordinary phases and make the portfolio harder to scan.
A system used across several products can justify its own entry if you can state your contribution accurately. Link public documentation or an approved case study rather than an internal component library.
How do you write a useful case summary without screens?
Write the summary as problem, constraints, decisions, your contribution, and approved outcome so the reader can assess your judgement even without source screens.
Replace vague claims such as ‘improved the experience’ with the flow you changed and the design responsibility you owned. Do not invent conversion figures or imply research validation that did not happen.
If the shipped interface changed after hand-off, record the delivery period and use a maintained case-study destination. For adjacent examples, use the related IndieShow guides below.
Related IndieShow guides: presenting client design work · handling private audit evidence
Why does IndieShow work for a private product-design portfolio?
IndieShow works as a stable public index for approved product evidence while private Figma files remain private and each project keeps an honest status.
You can update the order, description, tag, logo, optional metric, and destination from the dashboard as permissions or products change. Move obsolete work to Archived instead of leaving a broken prototype link.
Close the page with the clearest evidence first and a precise account of your contribution. IndieShow supplies the single personal URL; the approved artifacts still provide the proof.
Frequently asked questions
What can a product designer show when the Figma file is private?
Show the product problem, your responsibilities, the constraints, and approved outputs while withholding source files, participant details, internal comments, and unreleased screens.
What is the fast way to organise the portfolio with IndieShow?
The fast way is to create one IndieShow card per meaningful product outcome and group shipped, active, and retired work by its current status.
Should a design system and its product flow be one project or two?
Keep them together when the system work supported one delivery, and split them only when the design system has its own scope, users, maintenance story, and reviewable evidence.
How do you write a useful case summary without screens?
Write the summary as problem, constraints, decisions, your contribution, and approved outcome so the reader can assess your judgement even without source screens.
Why does IndieShow work for a private product-design portfolio?
IndieShow works as a stable public index for approved product evidence while private Figma files remain private and each project keeps an honest status.