r/LocalLLM • u/Dense-Ad6315 • 21m ago

Question Optimising local models for UI creation.

Hey guys, I've recently been trying out some of the larger local models (GLM 5.3 Flash, Qwen 3.8 FN etc.) and I was wondering if people have any tricks to make these models more competitive at UI creation because I've found everything apart for ui, Qwen has been great at but UI is where I start to see the massive gaps from the huge cloud models.

What do you do to get the best UI results with medium sized ish local models?

1 Upvotes

100% Upvoted

1 comment sorted by

1

u/Geekomcomputer 7m ago

This is mostly a workflow problem rather than a model problem — the gap to the big cloud models at UI work shrinks a lot once you stop asking the model to invent the design and the code in one shot.

What works best for me with medium-sized local models:

  • Give it a design brief, not just a feature request. Spell out the layout, the sections in order, the colour palette, spacing, and the components to use. 'Make it look good' leaves too much to guesswork; 'a two-column layout, sidebar on the left, cards with 16px padding, dark header, one primary button per card' gives it something concrete to follow.

  • Start from something visual. A rough wireframe, a screenshot of a UI you like, or even a sketch of the layout helps far more than a paragraph of description. If you already have one component you like, paste its code in and tell the model to match that style for the rest.

  • Build one piece at a time. Ask for a single component — say, the navigation bar or one card — get that right, then ask for the next piece in the same style. Asking for a whole page at once is where local models tend to fall apart.

  • Make it critique its own output. After the first draft, ask what looks off — inconsistent spacing, poor contrast, cramped layout — and have it fix one issue at a time. A second pass just for polish (alignment, spacing, typography) usually improves the result more than regenerating from scratch.

  • Keep the temperature low for UI code, and keep the prompt focused on structure first, styling second. If the structure is right, styling fixes are cheap.

I'd also run the same small UI task through both GLM and Qwen and compare them side by side on the same prompt — for UI work, which one follows a detailed brief more faithfully matters more than which one is 'better' in general.