Pyosi

Write the message. Pyosi does the marking on the screenshot. Problem Statement: A message alone often can't show which part of a screenshot is meant, so people attach an image and mark the part by hand, usually in a snipping tool, or in PowerPoint for neater marks. I do this myself: as a product manager I highlight screenshots before sending them, and earlier, as a machinery engineer at a shipbuilding company, I marked photos in slides for vendors and stakeholders. Marking by hand was the tedious part, and that is where the idea for Pyosi started. Of five people I asked, all use screenshots daily; three mark them regularly and said marking needs a separate program or looks untidy. Target Users: Anyone who sends a screenshot with a message asking for a change or a check, often an engineer, a designer or a product manager (bug reports, design reviews, incident threads). Solution: The sender adds a screenshot and the message they would send with it. Pyosi works out which parts the message refers to and marks them with numbered boxes and short explanations, or highlights the distance when the message is about the space between two elements. The sender no longer marks by hand: they check the marks, move, resize or edit what is off, and export a PNG to send with the message. The reader sees exactly which part is meant instead of relying on the message alone. Because Pyosi starts from the message, not from the picture, it also checks the message: it says "not found" when it cannot find a part and "ambiguous" when several parts could be meant, instead of guessing, so the sender can update the message before sending.