FeaturesUX review
A designer's eye on this interface
Before the review, before the release, before you show it to anyone: what would a senior product designer say about this screen?
Runs on the Balanced tier — 2 credits per run.
What you get back
At most five findings, one line each, ranked by how much damage the problem does: the problem in a few bold words, what a user would actually do wrong because of it, then the concrete fix. It looks for an unclear primary action, hierarchy that fights the task, hit targets under 44px, text contrast that will fail WCAG AA, state that is not visible, error copy that blames the user, density that hides what matters, and controls whose consequence is not obvious before clicking. It skips what it cannot see. A genuinely good design gets told which two decisions carry it — and its one weakest link anyway.
When to reach for it
Your own work, before someone else reviews it. A competitor's flow you want to learn from. A mockup in a design tool, a live page, a native app — anything you can put on screen.
What leaves your machine
Exactly one image, once, when you press the lens — plus the capture's window title and dimensions, nothing else. It is read by a private model under zero data retention, the answer streams back as text and is saved onto the capture in your local library, and the image is not kept anywhere.
How to use it
- Capture — PrtScn for a region, Alt+PrtScn for a window, Ctrl+PrtScn for the whole screen.
- Pick the lens in Studio. The answer streams in and stays attached to that capture.
- Copy it, rerun it, ask a follow-up, or come back to it later from the Library.
Every lens on every plan
The free plan runs every lens, with a monthly credit allowance and nothing to configure. Capture, editing, redaction, the library and the presenter tools need no account at all.