How to get feedback on a mobile mockup
To get feedback on a mobile mockup, share it in a way your client can view at the right size — on their actual phone, not zoomed out on a laptop where every tap target looks bigger than it is. A Figma prototype link in presentation mode, exported PNG screens in a review tool, or a shared link they open on their phone all work. The one thing that consistently produces bad feedback: sending a PNG at 2x retina export and asking them to judge it on a widescreen monitor.
Send the Figma prototype link in presentation mode
In Figma, open your mobile prototype and go to Share → Prototype. Set the width to the device frame you designed for (375px for iPhone SE, 390px for iPhone 14) and enable 'Fit to screen' off — or your client will see it zoomed down. Copy the link. When they open it on a desktop browser it runs at whatever zoom Figma defaults to; when they open it on their phone it fills the screen at the right scale. Two things to flag upfront: commenting requires a free Figma account, and prototype links show only the connected frames — so if a flow isn't hooked up, the reviewer is stuck. For a client who isn't a Figma user, this often produces a support call before a single comment. For clients who are comfortable in a browser and just need to see the flow, it's the most faithful representation of the design without a build.
Export screens as PNG and share them — but tell clients to open on their phone
From Figma: Select all the frames → Export → PNG at 1x (not 2x for client review — 2x produces an oversized image that looks fine on a Retina display but stretches on a phone browser). Email the set or drop them in Google Drive. The critical instruction to include in your message: 'Open these on your phone — the font sizes and spacing are designed for a 375px screen. On a laptop they'll look larger than they will in the final app.' Most designers skip this line and receive feedback on proportions that only look wrong because the client is reading a phone screen blown up to 27 inches. The other limitation: a PNG set has no built-in way for the client to pin a note back. They annotate in Preview, WhatsApp you a screenshot, or send three paragraphs of email. By round two you're reconciling five different images.
Share a review link they open on their phone and annotate directly
Export the screens from Figma (PNG at 1x per screen) and drop them into a review tool that generates a shareable link. Your client opens the link on their phone — the screen renders at the right scale, they tap the element they mean (the tab bar icon, the CTA button, the error text), and leave a note pinned right there. No Figma account. No download. The feedback quality difference between this and emailing a PNG is substantial: 'the Continue button text feels hard to read at this size' pinned to the actual button on a phone is immediately actionable. 'The bottom section looks a bit cramped' in an email takes one more exchange to locate. Tools that support no-account guest commenting on uploaded images include Markup.io, Ruttl, and Drafty. The honest caveat: they're reviewing a static image, not an interactive prototype, so if the feedback is about transitions or interactions, a Figma prototype link is the right complement.
Walk through it on a screen share — and mirror your phone, not your laptop
A 30-minute call gets richer feedback per minute than any async method. The mistake most designers make: they share their laptop screen showing the Figma canvas, which means the client is reacting to the mockup surrounded by layers panels, component names, and ruler guides — not a phone screen. Mirror your phone instead. On Mac: plug in an iPhone via USB, open QuickTime → New Movie Recording → select the iPhone as the camera source. Or use AirPlay on iOS 16+. The client now sees the design on a real phone screen, at real size, responding to real touches. Ask one question per screen — 'is it obvious what this button does?' beats 'what do you think?' — and paste answers into a running doc while they're talking. Send the doc back within an hour. Screen shares surface flow and animation issues that static images miss, but the notes only exist if you capture them yourself during the call.
If your client keeps reviewing your phone screens on their laptop and commenting on spacing that only looks wrong at desktop scale — share a review link and tell them to open it on their phone. Drop your exported screens into Drafty, send the link. They tap the exact element on their actual phone screen and leave a note pinned right there. No account. Every comment lands in one thread anchored to the spot they tapped. When you push updated screens, the link stays the same.
Open a live demoQuestions
- How do I share a mobile mockup with a client who doesn't have Figma?
- Export the frames as PNG (1x scale) and either email them or drop them into a link-based review tool. The link option is better for actionable feedback — your client clicks the exact element and leaves a pinned note, rather than annotating a JPEG in Preview and sending it back. Either way, include a note asking them to open it on their phone, not their laptop: the spacing and font sizes are designed for a mobile viewport and look different at desktop scale.
- Can my client view a mobile mockup on their phone?
- Yes — a Figma prototype link opens on any mobile browser, and an exported PNG opens in any photo viewer or browser. A shared review link from a tool like Markup.io or Drafty also renders on mobile and lets them tap-to-comment directly on the screen. Viewing on a phone is genuinely important for mobile mockups: a design reviewed only on a laptop often produces feedback about spacing and text size that would never come up on a real device, because the proportions look different at full desktop width.
- What's the difference between a Figma prototype link and a design link for client review?
- A design link opens the full Figma file — frames, layers, the editor canvas. A prototype link (File → Share Prototype) opens a presentation-mode view of the connected flows only. For client review of a mobile mockup, a prototype link is almost always better: the client sees the screens in device context without the Figma UI around them, and they can't accidentally click into the editor. The downside is that only linked frames are reachable — screens that aren't wired into the flow just don't appear.
- How do I get useful feedback on a mobile design instead of vague comments?
- Ask one concrete question per screen and give clients a way to point at the exact element. 'Does the empty state on the home screen make it clear what to do next?' produces a usable answer. 'What do you think of the home screen?' produces 'looks good.' The combination of a specific question and a pinned annotation — where they click the spot rather than describe it in words — cuts the number of follow-up exchanges by roughly half.
- How do I show a mobile mockup at actual phone size?
- A Figma prototype link in presentation mode with 'fit to screen' disabled shows the design close to real size on a phone browser. An exported 1x PNG (not 2x retina) opened in a phone browser also renders at close to the right scale. The most accurate method is mirroring a real device via QuickTime during a screen share — but that only works synchronously. For async review, the prototype link is the most reliable option for approximate real-scale viewing.
- How do I collect mobile mockup feedback from multiple stakeholders?
- Send everyone the same review link rather than separate email threads or individual image files. A shared link means all comments land in one place, anchored to the same screens, visible to every reviewer. The alternative — each stakeholder annotating their own copy of the PNG — means you're reconciling four separate sets of marks on four different files, with no way to see if two reviewers flagged the same issue.
Keep exploring
Stop emailing files back and forth.
Share one link. They comment on the exact spot — no account, always the current version.