AIToday
Large Language ModelsAI Coding AssistantsOpen-Source AIr/artificialPublished: Aug 20, 2026, 01:03 JST2 min read

Three AI models tackle web design task—local Qwen outbuilds cloud rivals

Three AI models tackle web design task—local Qwen outbuilds cloud rivals

Key takeaway

  • A developer ran a direct comparison test, asking three AI models—Qwen 3.8 27B (local), GPT‑5.6 Terra (ChatGPT subscription), and Grok 4.6—to build the same premium web experience for a fragrance launch site.

  • Qwen produced the largest and most modular codebase, with over 3,000 lines across 16 files and rich interactive features including particle systems, timeline animations, and accessibility modes, suggesting that local open-source models can match or exceed cloud-based alternatives on complex development tasks.

3 Key Points

  1. What happened

    A developer gave Qwen 3.8 27B (running locally), GPT‑5.6 Terra (ChatGPT), and Grok 4.6 the same brief—build a premium Three.js fragrance launch site from an identical Git baseline. Qwen produced the most architecturally extensive result, with 16 files and over 3,000 added lines, including modular components for scene, bottle, particles, backdrop, timeline, camera, section, and form.

  2. Why it matters

    The test surfaces real differences in how AI models approach complex web development tasks. Qwen's local implementation generated approximately 740 particles, a five-stage scroll timeline, drag-to-orbit interaction, note-driven color changes, persistent waitlist, WebGL fallback, and reduced-motion mode—demonstrating that open-source local models can produce feature-rich output competitive with subscription cloud services.

  3. What to watch

    Qwen's production JavaScript bundle is about 545 KB uncompressed; the article notes the agent could not verify WebGL pixels programmatically, flagging a verification gap. The full comparison includes GPT‑5.6 Terra and Grok 4.6, though their implementations are not detailed in the available excerpt.

Ask the AI about this article →

Context & Analysis

This direct comparison test reveals a meaningful data point in the ongoing debate over local versus cloud-based AI for software development. By constraining all three models to the same task, baseline code, and objective requirements, the developer created conditions that isolate each model's capabilities rather than relying on anecdotal impressions. Qwen 3.8 27B, despite running on consumer hardware via Ollama, produced the most architecturally sophisticated result—splitting concerns across eight distinct modules (scene, bottle, particles, backdrop, timeline, camera, section, form) and delivering a feature set that includes particle systems, temporal animation logic, user interaction layers, and accessibility considerations. The 3,000+ line codebase and 16-file structure suggest the model understood not just the immediate requirement but also long-term maintainability patterns. The production bundle size (545 KB uncompressed) and the gap in WebGL pixel verification point to real trade-offs: Qwen's feature density may come at a performance or debuggability cost. The comparison also implicitly positions GPT‑5.6 Terra and Grok 4.6 alongside a local open-source alternative, a framing that invites users to evaluate whether subscription pricing is justified by output quality for this class of task.

FAQ

What models were compared in this test?
Qwen 3.8 27B (running locally on Ollama), GPT‑5.6 Terra (via ChatGPT subscription), and Grok 4.6. All three were given the same brief to build a premium Three.js fragrance launch site from an identical Git baseline.
What features did Qwen's implementation include?
Qwen's output featured a modular Three.js architecture with a procedurally generated transmitted-glass bottle, inner liquid and resin cap, approximately 740 particles, a five-stage scroll timeline, drag-to-orbit interaction, note-driven color changes, persistent waitlist, WebGL fallback, and reduced-motion mode across 16 files and over 3,000 added lines of code.
What was a limitation of Qwen's output?
The production JavaScript bundle is about 545 KB uncompressed, and the agent could not verify WebGL pixels programmatically, indicating a potential constraint in automated validation of the rendered output.

Get the latest Large Language Models news every morning

For example, today's edition would include:

  • Nvidia revives Rubin CPX chip with major redesignYahoo Finance AI · 2h ago
  • AI advice followed by 79%, but well-being unchangedITmedia AI+ · 5h ago
  • Enterprises face agent governance gapSiliconANGLE AI · 8h ago

AI-summarized, only the topics you pick — one digest a day via Email, Slack, or Discord.

Free · takes 30 seconds · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. Q&As are published on this page for other readers too.

Related Articles

Next articleVentureBeat hires first Lead Analyst to deepen enterprise AI research