Lilacpane01 / Use the cover to establish project form
A cover can pair one primary device with a supporting device, but do not fill every screen just to imply a large amount of work. The cover should identify the project, not explain every detail at once.
02 / Place mockups after key decisions
Explain the problem and choice, then show the result in context. A framed final screen after a navigation redesign is more persuasive than five decorative mockups at the beginning.
- Problem and goal
- Constraints and design decisions
- Key screens or prototype
- Final result in device context
- Metrics, feedback, or next iteration
03 / Give iPhone and iPad a clear hierarchy
Two devices should not always carry equal visual weight. Enlarge the primary use case and let the secondary device explain responsiveness or cross-device behavior. The screens should have a real relationship, not be random fillers.
04 / Keep enough interface close-ups
Mockups provide context but cannot replace UI detail. Include screen close-ups, components, or flows so the reader can inspect the actual design work instead of seeing only attractive shells.
FAQ
Can a portfolio cover include several devices?
Yes, but give one a clear lead role. Supporting devices should explain platform scope or context.
Should every portfolio screen be framed?
No. Use a mockup for device context and a close-up or screen-only image for detailed design explanation.
Must mockup backgrounds exactly match the brand color?
No, but color, contrast, and typography should keep the mockups connected to the overall case study.
