The designer sent a PDF mockup of the new homepage. The hero text is misaligned, the CTA colour clashes with the brand, and the spacing under the headline feels off.
Text feedback won't communicate this clearly. Annotating in place will. Flint handles design reviews properly.
Arrows and shapes for alignment
Use arrows to point at misalignments. Draw a line from the hero text to where it should align with — visually obvious to the designer. Use rectangles to indicate desired widths or margins. Designer sees exactly what you're talking about.
Notes for content and copy feedback
Sticky notes capture the textual side: 'Change CTA from "Submit" to "Get started"', 'Headline reads cold, try warmer voice', 'Add subhead under hero'. Notes are anchored to the page location, so the designer knows which element each note refers to.
Colour callouts
For colour issues, highlight or circle the offending element and attach a note: 'This blue clashes with the brand teal — try #2F5F5F'. Be specific. Vague colour feedback ('feels off') wastes everyone's time; hex codes don't.
Bundle with other design files
If you're reviewing a multi-page mockup PDF and want to attach reference assets (logo file, brand guide), merge them into one file before sending back. Designer gets your annotations plus all reference material in one bundle.
FAQ
Does Flint match Figma's commenting?
Different tool, different file format. Figma is for live design files; Flint is for PDFs. If your designer exports PDFs for review, Flint is the match.
Can I sketch a fix?
Yes — use the freehand ink tool to sketch your suggested layout.
Will the designer see annotations in their PDF reader?
Yes. PDF annotations are standard and visible in every major reader.
Should I send the annotated PDF or a separate doc?
Annotated PDF — everything in context. Separate docs make the designer hunt across files.
Point, comment, sketch, save. Review design PDFs.