Best of UI Design — February 2026

  1. 1
    Article
    Avatar of zedZed·14w

    Introducing Theme Builder — Zed's Blog

    Zed launches Theme Builder, a visual editor for creating custom editor themes without editing JSON. The tool features live preview, an inspector to identify which tokens control specific UI elements, color linking to maintain consistency across related elements, and Tree-sitter-powered syntax highlighting that matches Zed exactly. Users can import existing themes, make changes with instant visual feedback, and export as theme overrides or extensions. The interface uses CSS custom properties for instant updates and includes undo/redo support with local storage persistence.

  2. 2
    Article
    Avatar of infoqInfoQ·14w

    Shadcn Releases Visual Project Builder

    Shadcn launched a visual project builder accessible via `npx shadcn create` that lets developers customize their entire project setup—including themes, component libraries, icon sets, and design systems—before writing any code. The tool supports Next.js, Vite, and TanStack Start frameworks, offers real-time design previews with options for Radix UI or Base UI foundations, and generates a custom command with all selected parameters. This design-first approach eliminates repetitive manual setup work and aligns with shadcn's philosophy of giving developers complete code ownership by copying components directly into projects rather than distributing them as npm packages.

  3. 3
    Article
    Avatar of hordeHorde·14w

    I built Warcraftcn – a Warcraft-styled React UI library (fully open source)

    Warcraftcn is a free, open-source React component library with a Warcraft/RTS game aesthetic, built on shadcn/ui. Currently includes 7 components (Badge, Button, Card, Dropdown Menu, Input, Skeleton, Textarea) with plans to expand coverage and add faction-specific themes (Orc, Elf, Human, Undead). Uses image assets generated with AI for rapid development rather than CSS/SVG implementation.

  4. 4
    Article
    Avatar of dartdevsDart Developers·15w

    Flutter ScreenUtil: Mastering Responsive Font Sizing Across All Devices

    A Flutter developer encountered broken text layouts when their app was displayed on tablets after testing only on phones. The solution involves using the fontSizeResolver parameter in ScreenUtil library to ensure fonts scale properly across different device sizes and screen densities.

  5. 5
    Article
    Avatar of scl7luejySuraj Vishwakarma·13w

    What’s the Hardest Part of Generating UI as a Frontend Developer?

    A frontend developer reflects on the challenges of using AI to generate UI, noting that while AI accelerates development, it tends to produce generic, repetitive designs—SaaS-style hero sections, predictable card grids, and inconsistent design systems. The post raises questions about when to trust AI-generated UI versus taking manual control, and invites community discussion on maintaining design consistency and uniqueness when relying on AI tools.

  6. 6
    Article
    Avatar of lobstersLobsters·13w

    Death to Scroll Fade!

    A developer rant against the ubiquitous 'scroll fade' web design trend, where page elements fade in as they scroll into view. The author argues it's tacky, often demanded last-minute by stakeholders, and raises real concerns: accessibility issues for users with vestibular disorders, cognitive overload, cross-platform inconsistency, and negative impact on Core Web Vitals like LCP. The post crowdsources practical arguments to push back against scroll fade requests, while humorously suggesting developers collectively pretend the technique is now illegal.

  7. 7
    Article
    Avatar of netguruNetguru·14w

    How to Create Design System Documentation: A Step-by-Step Guide

    Design system documentation serves as the foundation for team alignment and consistent UI design. The guide covers five essential steps: understanding your audience (designers, developers, product managers), planning documentation structure (task-based vs. structural formats), documenting foundations and components (colors, typography, spacing, accessibility), selecting appropriate tools (Figma, Storybook, Supernova), and maintaining the system through feedback loops and regular updates. Successful documentation bridges design and development teams, provides clear usage guidelines beyond component lists, and integrates naturally into existing workflows. The Silk design system exemplifies this approach for commerce and marketplace products.

  8. 8
    Article
    Avatar of lobstersLobsters·16w

    Microsoft Has Killed Widgets Six Times. Here's Why They Keep Coming Back.

    Windows widgets have been implemented and killed six times since 1997, each iteration failing due to performance, security, screen space, or engagement issues. Active Desktop crashed systems, Vista Sidebar consumed too much screen space, Windows 7 gadgets had catastrophic security flaws, Windows 8 Live Tiles disrupted workflow, and early Windows 11 attempts felt invasive. The current Widget Board uses declarative Adaptive Cards with native WinUI 3 rendering, eliminating code execution vulnerabilities while maintaining interactivity. Every architectural constraint in today's platform exists as a direct response to a specific past failure.

  9. 9
    Article
    Avatar of theregisterThe Register·14w

    Why is Windows 11 taskbar like that? Ex-Windows man explains

    Former Microsoft CVP Mikhail Parakhin revealed that Windows 11's locked taskbar position resulted from a design vision to create symmetric panes with widgets on the left and system controls on the right, pushing the Start menu to center. This decision removed Windows 10's taskbar customization options, including the ability to move it to different screen edges—a feature present since Windows 95. Parakhin acknowledged fighting against removing customization options, though Microsoft prioritized the widget-centric design over user flexibility.

  10. 10
    Article
    Avatar of androiddevAndroid Developers Blog·14w

    Prepare your app for the resizability and orientation changes in Android 17

    Android 17 removes the developer opt-out for orientation and resizability restrictions on large screens (>600dp). Apps targeting API level 37 must adapt to various display sizes and orientations, with manifest attributes like screenOrientation and maxAspectRatio being ignored. The post provides practical solutions for common issues including camera preview distortion (using CameraX or CameraViewfinder), stretched UI elements (using widthIn modifiers), inaccessible buttons (adding vertical scrolling), and state preservation during configuration changes. Google Play will require API level 37 targeting by August 2027.

See all UI Design archives