Software feature launch · Production guide
Zoom a screen recording and check the smallest UI label
Choose the smallest button label needed to understand the demo, inspect it in the capture, then compare the edited zoom with the final encoded mobile frame.
Input and decision
Pick one essential label in the recording. Compare it in a native-size still, an enlarged crop and a frame extracted after final compression.
Set up the comparison
Use a real phone or a matched viewport for the final review. If the viewer can identify a control only because of your subtitle, the UI evidence is weak.
Make the comparison
Save the same control as three stills: native capture, cropped master and final encoded phone frame. Mark the first still in which its label breaks down.
Worked record
The downloadable worksheet includes the records below and a blank row for your own project.
| Item to check | Source material | Crop requirement | Delivery check | Acceptance |
|---|---|---|---|---|
| Control label | Native capture | Only needed region | Phone viewport | Review on export |
| Account corner | Masked publication cut | Do not reveal | Final encode | Privacy check |
| Result thumbnail | Original and variants | Keep comparison | Full frame | Review on export |
Check the result
If the label is already unreadable in the original, record at a better scale. Enlarging soft pixels in an edit cannot recover the actual characters.
Hand off the revision
Deliver the original frame and the final phone-size crop together so the reviewer can locate any loss of text clarity.
Review question
How do I find where a UI label first became unreadable?
Compare the same letters in the native capture, the edited crop and the final encoded phone frame. Mark the first version where the lettering stops being legible.
Use the task on your own brief
Use a copy of the worksheet to keep the project’s source files, reviewed options and decisions together.