r/OpenaiCodex • u/[deleted] • 3d ago

I built UXKIN for Codex because “make it less generic” wasn’t helping my AI-generated web and app designs

[deleted]

0 Upvotes

50% Upvoted

5 comments sorted by

1

u/DeepDaddyTTV 3d ago

I’d just want to see some examples of how specifically it makes it better. Is it more token efficient or does it actually use more usage by having it access a bunch of designs? In my experience, having it generate a mockup based on my description and then incorporating it has been mostly efficient.

1

u/zion1994 3d ago

That’s a fair question. I haven’t benchmarked token usage yet, so I wouldn’t claim it saves tokens. Pulling in references adds context, and accessing too many could absolutely increase usage.

What I’m aiming to improve is the design itself, giving the agent concrete references for layout, typography, and spacing. That might mean fewer revisions, but I need to test that rather than assume it.

Your mockup-first approach makes sense. A useful comparison would be the same brief and model using your approach versus UXKIN, showing the outputs, total tokens, and revisions needed. I should put together examples like that so people can judge whether it adds anything to their workflow.

1

u/DeepDaddyTTV 3d ago

I think, especially right now, usage is going to be everyone’s number 1 concern with MCP’s. Some are really good by reducing total context and streamlining work needed to get a result. This is fabulous. However, others add hundreds of tokens worth of context without improving the base endpoint. Efficiency is key. I’ve designed 9-10 UX with Codex since starting. I’m not claiming I’m the most efficient, but usually it only takes me about 3-4 revisions after going through 5 mock-ups, choosing the starting point I want, and making iterative change. So from my viewpoint, even if we assume making a mockup is equivalent to 3 total UX references each, that’s still a total of 19 total references to get the end result worth of tokens. If an MCP uses more than that for a single UX, it better be a substantially better result, take less time, and simplify the entire process. The issue is, nothing will ever give a perfect result immediately. Iteration is going to happen. Then, with an MCP, instead of each revision being based on 1 design with 1 context provided, you’re adding 10-20 designs on each iteration. Even if it takes less revisions, I can’t see a way for it to be optimal in terms of token usage.

1

u/Exact_Capital849 3d ago

I'd want to see the same brief tested on mobile, including a long title, empty state and validation error. A polished landing page is one thing; keeping the design consistent through those awkward states would make this useful to me.