New Categories for Web Development in Code Arena

This category includes prompts that ask for a website or app inspired by a known product, company, website, or interface. These prompts often test whether models can capture a recognizable layout, interaction pattern, or visual style.

An example from our user:

“Build a Windows 95 desktop with draggable windows, start menu, taskbar with clock, desktop icons, and proper z-index stacking.”

This category includes prompts for websites that present information, products, brands, people, events, or organizations. It covers landing pages, company sites, portfolios, blogs, documentation sites, launch pages, etc.

An example from our user:

“Create a Padel-Animation (the sport commonly referenced as a mix between squash and tennis) on the main website.”

This category includes prompts for dashboards, admin panels, internal tools, CRMs, trackers, and other apps built around structured data or workflows. The focus is usually managing, reviewing, tracking, or analyzing information.

An example from our user:

“Build a crypto tracker with coin values, sparkline charts, portfolio allocation pie chart, and 24h changes. Pre-populated with sample holdings.”

This category includes user-facing apps where people browse, communicate, shop, book, post, transact, or consume content. It covers marketplaces, social apps, chat apps, booking products, streaming apps, e-commerce sites, and similar platforms.

An example from our user:

“create a google chrome extensions, make a fully animated cyberpunk UI for whole Google Drive, include a Gmail addon to make the important email highlighted in one group .Add a button to download full extension file .zip for upload in store .Also make a editor to select the neon light colors, adjust the brightness”

This category includes browser games and gameplay-first experiences. These prompts usually involve rules, objectives, player actions, scoring, levels, obstacles, or win/loss conditions.

An example from our user:

“Create a chess game with legal move highlighting, piece capture, check/checkmate detection, move history, and optional computer opponent”

This category includes interactive models where users change inputs and observe how a system behaves. It covers physics demos, educational simulations, scientific models, financial calculators, engineering models, and other explorable systems.

An example from our user:

“Create a web app that allows me to visualize the first and second derivative of an original function. there can be some presets but also a way for me to input my original function or the first or second derivative function. then the graphs would appear correctly showing the derivatives. i can drag a little point on the graph and see where it coresponds to on the other graphs. make it simple and easy to use and fit everything onto the screen with no scrolling needed.”

This category includes tools for creating, generating, customizing, or editing an output artifact. Examples include SVG generators, logo makers, drawing tools, diagram editors, image editors, layout builders, and design tools.

An example from our user:

“Create a color theory app with interactive wheel, harmony demonstrations, contrast checker, and colorblind simulator.”

Category-level leaderboards give us a clearer signal for understanding how web development use cases are evolving in Code Arena. By analyzing prompt distribution across categories over time, we can see that practical, real-world tasks — such as brand marketing and informational websites, data and analytics applications, and consumer product and platform applications are becoming a larger share of web development prompts over time.

At the same time, categories like gaming and simulations are declining in relative share, yet their absolute volume may remain meaningful as overall usage grows. This distinction is important: category-level views help separate changes in user demand from changes in total platform volume.

Together, these trends show why category-specific leaderboards are valuable. They do not just break down model performance more precisely; they also help track how real user needs shift over time, making the leaderboard more aligned with the applications people are actually building.

Category leaderboards reveal how much model rankings can change once web development is broken into concrete use cases. To illustrate this, we compare flagship models from several leading labs using both their overall Code Arena --webdev rank and their ranks across seven web development categories using the most recent leaderboard snapshot.

Among proprietary models, Claude Opus 4.7 Thinking shows broad strength across categories, with consistently high rankings throughout the radar plot. GPT-5.5 High also performs strongly overall, with especially visible strengths in interactive tasks such as simulations and gaming. Muse-Spark from Meta stands out in practical website and product-building scenarios, including brand marketing and informational websites, reference-based design, and consumer product and platform applications.

The open-source leaderboard shows a similarly rich picture. GLM-5.1 and Kimi-K2.6 both achieve strong category coverage, while their shapes highlight different areas of emphasis across web development tasks. Google’s Gemma-4-31B also shows why category views are useful: its profile is especially competitive in consumer product and platform applications relative to several other categories, making its strengths easier to see than in an aggregate ranking alone. Other open-source models also show meaningful category-level strengths, such as Mimo-V2.5 Pro in creative and interactive categories including gaming, simulations, and content creation and editing tools.

Code Arena is still evolving quickly. As models improve and tools evolve, we expect the category taxonomy to evolve as well. These seven categories provide a clearer way to understand how models perform across the kinds of web development tasks users actually ask for. Future directions include introducing finer-grained subcategories, analyzing tool-use patterns, and breaking down performance by interaction complexity, execution success, and visual quality.