Why I started building GlyPho

I started building GlyPho because I kept running into the same small problem: every product page needs visual assets, but making them takes more time than it should.

A logo idea, an empty state, a tiny illustration for docs, a few icons for a feature section. None of these should require opening five tools, searching stock sites, or exporting a flat image that nobody wants to edit later.

Most AI image tools are good at making something that looks nice for a second. But when I want to use the result in a real page, I usually need SVG. I want shapes I can inspect, copy, download, tweak, and place into a product without fighting the file.

So GlyPho is my attempt to make that workflow simpler. You write a clear prompt, describe the object and where it will be used, and get an editable SVG direction back.

It is still early, and I am still figuring out where the sharpest use case is. But the direction feels right: help makers and small teams create product visuals faster, without pretending every tiny asset needs a full design process.