Page Proxy v0.2.x: the boring "polishing" work and why I think it matters

This is the second devlog for my Chrome/Firefox userscript manager extension, Page Proxy ! Here I'm gonna cover v0.2.x, where I'm still trying to figure out what direction I'm planning to take the extension in. Refining and QOL work This is what I would normally call "polishing" work. It gives the extension much-needed features and fixes long-standing bugs. This stage, I would say, comes after the "minimum viable product" stage, where you just need to get something working as idea validation. After you get your initial users who are interested in your idea, keeping them becomes very important. This is where usability comes in, and to make a product with good usability, it must have adequate features and minimal bugs. Extension early stage At this point, I had a solid main idea of what I wanted the extension to do: turn page interactions into reusable userscripts. But the extension was lacking a lot of features, so I had to find the order which I wanted to implement them in. Roadmap Web