Supported resource types
What makes a screenshot easier to recognize?
SnapAction works best when a screenshot has one clear primary resource: a visible title, URL, repo name, product, place, event, invoice, or booking detail. It intentionally tries to ignore app chrome, nav bars, timestamps, comments, and unrelated text.
Consecutive screenshot grouping can help when a single article, booking flow, chat, or document spans multiple screenshots. Ambiguous screenshots may still produce less useful results.