A few days ago I shipped Fix My UI, a browser tool that reviews HTML components and tells you what is wrong. The core idea was simple: paste HTML, get structured feedback, move on.
It worked. But after using it myself for a couple of weeks I kept hitting the same friction points. So I fixed them.
The friction points and what I did about each one
Too many issues at once.
When I reviewed a complex component I would sometimes get nine or ten issues back. I did not want to see all of them at the same time. I wanted to handle the critical ones first and come back to suggestions later.
I added a severity filter. After a review runs, you can toggle critical, warning, and suggestion on and off independently. It sits in a thin bar below the result tabs and stays out of the way until you need it.
Re-pasting the same HTML over and over.
When I was iterating on a component, fixing one issue, then reviewing again, I kept copying and pasting the same HTML back into the input. On the third or fourth pass it got annoying.
I added session history. The last five reviewed components are stored in memory during the session. Each entry shows the first line of the HTML and the overall score. Click it to load the HTML back into the input instantly. Nothing is stored after you close the tab.
Sharing the review was awkward.
The review output lives across four tabs. When I wanted to share it with someone else, copying tab by tab and pasting into a message was clunky.
I added a Markdown export. One button downloads the complete review as a .md file: issues, improved code, quick fixes, and UX reasoning all in one clean document. I paste it straight into PR comments now.
None of these changed what the tool does
It still does one thing. You paste a component, you get a structured review. These three additions just made the workflow around that less frustrating.
Demo: roynick365.github.io/fix-my-ui
GitHub: github.com/roynick365/fix-my-ui
Top comments (0)