“Piny doesn’t try to be all-in-one visual editor that would cover layout creation, styling, data, logic… That is no longer relevant in the age of AI coding agents.”
Looks like in Pinegrow where this came from you have a brilliant CSS Editor. We as developers and frontenders who use IDE's are still heavily revising through traditional methods even beyond the use of AI. So the described detached mindset concerning AI still seems pretty distant into the future. AI and the industry are not there yet to void the need for further edits. A visual CSS tool inside an IDE like that would be a powerful integrated solution for all developers and frontenders.
“IDE, where you already work”
Exactly, most of us want to be inside full fledged IDE's vs an apps like Pinegrow or similar. It’s odd you didn’t choose to first set the foundation with your core CSS Editor then build out from there regarding frameworks and libraries. Development is vast but the the core is common. Hope it’s not too late to go back and rectify this, maybe through various user modes or something. You would then literally match your statements of tools designed to compliment with easier iteration past AI.
“visual tools should be designed to complement AI assisted development.” + “it is often much easier to directly change a visual property than to go back and forth about it with your AI agent.”
You got the CSS editor and we have the IDE’s. Definitely a concept with big potential to keep an eye on. Especially if you are willing to consider the feedback as you move forward.