I have been working on a small portfolio of browser tools. They look unrelated at first: a real-world Minecraft map generator, two music workflows, a map-poster studio, an invoice maker, and a logo-motion editor.
The common thread is narrower than the categories suggest. Each product starts with a task that is easy to describe but surprisingly easy to overcomplicate. The most useful product decisions were usually not new features. They were constraints: deciding what the tool should ask, what it should hide, and what a successful export should look like.
Here are six examples and the product lesson behind each one.
1. A map generator should start with a boundary, not a settings panel
Turning a real place into a Minecraft world sounds like a data problem. It is also a scope problem.
