Fact-checked by Grok 2 weeks ago

Menu bar

A menu bar is a graphical user interface (GUI) element consisting of a thin, horizontal bar that typically appears at the top of a window or screen, displaying labels for pull-down menus that organize and provide access to commands, functions, and settings within software applications. It serves as a primary navigation tool in desktop environments, allowing users to interact with features like file operations, editing tools, and help resources through hierarchical submenus. The concept of the menu bar emerged in the late 1970s during early development at PARC, where researchers like William Newman experimented with on-demand pop-up menus in programs such as Markup. It was first implemented as a persistent row of menu labels in the system in 1981, positioned initially at the bottom of windows before being relocated to the top for better based on user feedback. This design was further refined and popularized by Apple in the computer (1983) and Macintosh (1984), which introduced a single, global menu bar at the top of the screen with pull-down menus, a feature patented by William D. Atkinson. In modern operating systems, menu bar implementations vary to align with platform conventions. On macOS, the menu bar is a fixed, global element at the top of the screen that displays an app's top-level menus (such as , , and ) when the app is active, ensuring consistent access to commands and supporting standard keyboard shortcuts. On iPadOS, the menu bar appears centered at the top when the app is active and the user moves the pointer to the top edge or swipes down, displaying the app's top-level menus and supporting keyboard shortcuts, though it is hidden by default. In Windows, menu bars are typically embedded within individual application windows at the top, providing per-window for commands while adhering to guidelines for horizontal layouts and flyout submenus. Linux distributions, depending on the , often feature menu bars per application window in environments like or , though emphasizes a top bar for system status with app-specific menus integrated via hamburger icons or menus for a more streamlined interface. These variations reflect ongoing evolution toward touch-friendly and minimalist designs while preserving the menu bar's role in efficient command organization.

Overview

Definition and Purpose

A menu bar is a (GUI) element consisting of a that displays a collection of menu titles, each leading to pull-down or expandable menus containing commands and options. These menus organize application functions hierarchically, such as under categories like , , and View, allowing users to access a wide range of features without overwhelming the main workspace. The primary purpose of a menu bar is to provide an efficient structure for applications by grouping related commands into logical hierarchies, thereby reducing visual clutter and enabling quick of less frequently used functions. This facilitates user interaction by presenting top-level options persistently at the top of a or screen, promoting while conserving space compared to displaying all commands as individual buttons or icons. Unlike toolbars, which offer direct, icon-based access to frequently used actions, or ribbons, which integrate menus with contextual tabs for broader command exposure, the menu bar emphasizes a menu-driven approach focused on depth and organization rather than immediate visual shortcuts.

Historical Origins

The concept of the menu bar traces its roots to the pioneering research conducted at Xerox PARC in the 1970s. , leading the Learning Research Group, developed Smalltalk starting in 1972, which introduced key elements like overlapping windows and pop-up menus controlled by a , laying foundational ideas for menu-based in dynamic environments. , a key researcher at PARC, contributed to modeless interface designs through projects like the Gypsy (1974–1977), emphasizing seamless command access without modal shifts, which influenced early menu systems. These innovations built on the workstation (1973), the first system to demonstrate and -driven interactions, though menus remained contextual pop-ups rather than persistent bars. This evolved into the system, released commercially in 1981 as the Xerox 8010 Information System. The Star featured the first persistent row of menu labels, initially positioned at the bottom of windows, providing consistent access to commands across applications. Based on user feedback during development, the menu bar was relocated to the top of the screen for improved usability and visibility. Apple's adoption and refinement of these ideas occurred during the development of the project, initiated in 1978 and heavily inspired by a 1979 demonstration of PARC technologies to . By August 18, 1980, —now at Apple—proposed experimenting with menus positioned at the top or right edge of the screen to centralize access across applications, moving away from per-window attachments. On September 22, 1980, software engineer implemented the global menu bar at the top of the screen in a single overnight session, transforming it from experimental sketches into a fixed, screen-wide element that replaced bottom-anchored or window-specific menus for improved . This design evolved through user testing with non-experts, confirming its intuitive benefits over earlier PARC-style pop-ups. The , released on January 19, 1983, was the first commercial to popularize this global menu bar at the top of the screen, integrating it with pull-down menus, icons, and a one-button for office productivity. Priced at $9,995, the Lisa's interface marked a shift from the Star's property sheets and contextual menus to a unified, always-visible bar that simplified multi-application workflows. This innovation directly influenced the Macintosh, launched in January 1984, which retained the top-mounted global menu bar as a core element of its , enabling rapid adoption by general users. The design's emphasis on centralized, hierarchical menus soon extended to other platforms, including Windows 1.0 in 1985, which incorporated a similar persistent menu bar to standardize command access in graphical environments.

Design Principles

Key Components

A menu bar typically consists of a horizontal row of menu titles positioned at the top of a window or application, serving as the primary navigation structure for accessing commands and functions. These menu titles, such as "," "," and "Help," act as entry points to pull-down menus that expand downward upon selection, revealing organized lists of options. Pull-down menus are a core element, designed to display hierarchical content without occupying persistent screen space, and they often include submenus for nested categories to maintain logical grouping of related actions. Menu items within these menus are selectable entries, frequently accompanied by accelerators—keyboard shortcuts like Ctrl+S for saving—that provide alternative access methods. Standard menu categories follow conventional patterns to promote user familiarity across applications. The "File" menu commonly contains operations for document management, including New, Open, Save, Save As, and , which handle file , retrieval, and output. The "Edit" menu typically includes text and content manipulation tools such as , Redo, , Paste, and Delete, enabling efficient editing workflows. Other frequent categories like "View" manage display preferences (e.g., levels or toolbars), "Insert" adds elements (e.g., images or tables), "Format" adjusts styles (e.g., font or alignment), and "Help" provides documentation or support resources, ensuring a consistent framework for command organization. Variations in menu bar layout allow flexibility while preserving , such as fixed menus that remain static across the versus contextual menus that appear dynamically based on the active or . Separators—horizontal lines within —divide groups of related items for better visual scanning, while icons alongside menu items can enhance recognition without text overload, though their use is often limited to avoid clutter. These components collectively form a structured yet adaptable system for command access.

Interaction Mechanisms

Users primarily interact with the menu bar through mouse-based actions, where clicking on a menu title opens the corresponding dropdown or pull-down menu, revealing a list of selectable items. Once opened, hovering the mouse over items within the menu can trigger submenus to expand automatically, providing previews of nested options without requiring an additional click; this behavior allows for fluid navigation across related commands. In certain systems, users can also drag the mouse pointer over menu items to select them, with the menu persisting open during the drag operation to facilitate selection of distant or multiple options. Keyboard navigation provides an alternative interaction pathway, enabling access without relying on the mouse. On platforms like Windows, pressing the activates the menu bar by highlighting the first title, after which (left/right for top-level menus, up/down for items within an open menu) allow traversal, and the executes the selected item. Similarly, in macOS, the Control-F2 (or Fn-Control-F2) shortcut focuses the menu bar for access, with navigating titles and items, while Command-key combinations serve as direct shortcuts for common actions like . Submenus opened via follow the same arrow-key logic, with the right arrow key entering nested levels and the left arrow or Escape key retreating. Menu bars adhere to consistent behavioral rules to ensure predictable interactions. Menus typically persist on screen until the user explicitly dismisses them—via a outside the menu, pressing , or selecting an item that closes the —preventing accidental closure during . Nested submenus maintain this persistence independently, remaining open for selection even if parent items change state, though they are limited to shallow depths (often one or two levels) to avoid overwhelming users. These mechanisms, rooted in early standards, balance discoverability with efficiency by responding dynamically to user input without requiring constant re-activation.

Platform-Specific Implementations

macOS

In macOS, the menu bar is a persistent, global element positioned at the top of the screen, shared across all applications to provide unified access to system and app controls. This design has been a core feature since the original , released in , where it centralized menus for the active application while allowing seamless switching between programs without relocating interface elements. The concept traces its origins to the project in 1983, which first implemented a static menu bar at the screen's top edge for shared application access. Unlike per-window menus in other systems, this global placement emphasizes a consistent, screen-wide navigation paradigm that integrates deeply with macOS's . The leftmost item in the macOS menu bar is the Apple menu, represented by the Apple logo, which offers essential system functions such as viewing hardware details via "About This Mac," accessing , restarting or shutting down the computer, and managing software updates. To its right are application-specific menus like , , , and others, which vary by the foreground app and provide context-sensitive commands for tasks such as saving documents or adjusting preferences. This structure ensures that core operations remain readily available regardless of the active , promoting efficient in a multi-app environment. The right side of the menu bar hosts status and utility icons known as menu bar extras, including the clock for time and display, battery indicator for portable Macs showing charge level and estimated remaining time, signal strength, and volume controls. Users can customize these extras through > Control Center, enabling or disabling items like search or Do Not Disturb status to tailor the bar's utility. For instance, the menu allows quick access to power-saving options and detailed usage history. Over time, the menu bar has evolved with visual and functional enhancements, such as enhancements to the translucent effect in (version 13) in 2022, which applies a subtle translucent effect to blend the bar with the desktop wallpaper while maintaining readability. This update, accessible via settings to reduce or adjust transparency for better visibility, enhances the aesthetic integration of the interface. Additionally, on models equipped with the Touch Bar (introduced in 2016), the menu bar integrates with the Touch Bar by dynamically updating its contextual controls—for example, displaying app-specific buttons like playback controls when a media menu is selected—allowing haptic feedback and touch gestures to complement traditional menu interactions.

Microsoft Windows

In Microsoft Windows, the menu bar has been a per-application feature since the operating system's with in , where it appeared as a simple, text-based row of drop-down menus positioned directly below each window's title bar to provide access to commands like , , and . This design allowed individual applications to maintain their own localized navigation, distinguishing Windows from global menu paradigms and enabling tiled or overlapping windows to each host independent controls. Over time, this per-application approach integrated seamlessly with title bars, supporting keyboard activation via the for users to toggle visibility and access menus efficiently. The evolution of the menu bar in Windows reflected broader visual and functional shifts, particularly with the introduction of the interface in in 2009, which applied glass-like transparency and subtle depth effects to menu bars, enhancing their integration with window frames for a more immersive, three-dimensional aesthetic while preserving the traditional drop-down structure. In parallel, applications underwent a significant redesign starting with Office 2007, where the interface—a tabbed, contextual toolbar—replaced conventional menu bars to streamline command discovery, reduce nesting levels, and adapt dynamically to tasks, thereby improving productivity by exposing frequently used options more prominently without overwhelming the interface. This change influenced broader Windows ecosystem trends, as elements of the Ribbon appeared in native apps like and , prioritizing visual hierarchy over static menus. By in 2021, the menu bar embraced minimalism, with reduced visual prominence in favor of centered taskbar elements and simplified window aesthetics, aligning application interfaces with a cleaner, more modern layout that de-emphasizes layered controls in favor of touch-friendly and adaptive designs. System-level menu elements, such as the and taskbar notifications, further shaped this progression by providing centralized access to applications and alerts, indirectly influencing how per-app menu bars handle overflow and integration with OS-wide navigation.

Linux and Unix-like Systems

In Linux and Unix-like systems, the menu bar's implementation draws from the foundational , developed in 1984 at , which provided low-level support for graphical elements including menu bars managed by window managers to handle user interactions like pulling down menus upon clicks. This heritage enabled early Unix graphical interfaces to incorporate menu bars as standard components for application navigation, with the X protocol specifying facilities for rendering and event handling in bitmap displays. Subsequent widget toolkits built on X extended menu bar functionality for broader Unix compatibility. The toolkit, widely used in environments, includes the GtkMenuBar class as a core subclass of GtkMenuShell, allowing developers to create horizontal menu bars containing GtkMenuItems for pull-down menus in applications. Similarly, the toolkit, prevalent in , offers the QMenuBar class to construct menu bars with addMenu() methods for integrating pull-down items, ensuring cross-platform rendering on Unix systems including . Desktop environments in exhibit varied menu bar approaches rooted in their design philosophies. , since its version 2 release in June 2002, integrates application menus into a top that serves as a global navigation bar, featuring items like the Applications menu alongside system status indicators, diverging from traditional per-window placements to emphasize a unified experience. In contrast, KDE Plasma employs per-window menu bars by default, where each application window includes its own menubar for , , and other common operations, complemented by customizable widgets that can incorporate global menu elements or shortcuts. The transition to compositors in modern distributions has influenced menu bar rendering, as Wayland's lacks native X11-style global menu support and relies on compositor-specific extensions for features like app menus. For instance, uses the KDE AppMenu extension to enable global menus in Wayland sessions, allowing menu bars to detach from windows and integrate into panels, while leverages Mutter's extensions for similar top-bar menu adaptations, though compatibility varies across applications and requires explicit .

Other Systems

In , introduced in 1985 with the computer, the graphical user interface featured a menu bar positioned at the top of the screen, activated by pressing the right mouse button to support multitasking operations. This design integrated gadgets—interactive elements like sliders and buttons—directly into the interface, allowing users to manage multiple applications simultaneously through pull-down menus for tasks such as file operations and window control, a pioneering aspect of preemptive multitasking in personal computing GUIs. The system's emphasis on efficient enabled seamless gadget interactions without halting other processes, distinguishing it from contemporary environments. NeXTSTEP, released in 1988 for NeXT workstations, employed object-oriented menu bars as part of its Application Kit framework, built on to facilitate reusable and modular interface components. The menu bar, typically located at the top of the screen in the upper left corner, supported submenus, keyboard shortcuts, and detachable panels, with rendering handled by for consistent, high-quality across displays and printers. This approach influenced subsequent object-oriented designs by enabling dynamic updates and event handling through a responder chain, where menu items sent action messages to target objects for efficient command execution. Atari TOS, launched in 1985 with the Atari ST series, utilized the GEM (Graphics Environment Manager) AES for menu bars that appeared at the top of the screen for the active application, supporting per-window interactions through resource-defined menus loaded via .RSC files. These menus allowed developers to create application-specific drop-down options, with functions like MENU_BAR for display control and MENU_IENABLE for item toggling, adapting to the focused window's context in a single-tasking environment. Similarly, , debuting in 1987 on computers, introduced an icon-driven bar at the bottom of the screen—known as the Icon Bar—for , featuring context-sensitive pop-up menus activated by the middle and extensive drag-and-drop support for file and application operations. This bar represented running tasks as icons, enabling users to drag objects onto them for actions like launching programs or appending data, a novel paradigm for intuitive navigation in resource-constrained hardware.

Usability and Accessibility

Ease of Use

The top placement of menu bars in desktop graphical user interfaces exploits by positioning the menu along the screen's upper edge, which serves as an infinite boundary that prevents overshooting and minimizes cursor movement time for frequent access. This ergonomic advantage is particularly beneficial in traditional monitor setups, where users' hands rest near the and , allowing rapid upward flicks to initiate commands without precise aiming. Hierarchical organization within menu bars reduces by grouping related commands into logical categories, enabling users to scan and select from smaller subsets rather than scanning extensive lists. Human-computer interaction studies demonstrate that this structure facilitates faster task completion compared to flat toolbars, as it limits efforts and leverages users' ability to recognize familiar groupings, with empirical models showing performance gains for command sets exceeding simple linear arrangements. Keyboard shortcuts can further enhance this efficiency by providing direct access to nested items, bypassing mouse navigation when needed. However, deep nesting in menu bars can lead to disorientation and increased , as users struggle to track their position across multiple levels. Best practices recommend limiting items per menu to approximately 7 ± 2, drawing from on capacity, to prevent overwhelming users and maintain quick decision-making. This constraint, applied judiciously, balances hierarchy depth with usability, as evidenced by trade-off analyses favoring shallower structures for optimal retrieval speed.

Accessibility Features

Menu bars incorporate various accessibility features to support users with visual, motor, and cognitive impairments, ensuring navigable and perceivable interfaces in alignment with established standards such as WCAG 2.2. Screen reader compatibility is a core aspect, particularly through the use of (Accessible Rich Internet Applications) labels in cross-platform applications and web-based menu implementations. These labels provide descriptive names for menu elements, enabling screen readers to announce menu structures and items clearly to users who rely on auditory feedback for navigation. On macOS, integrates seamlessly with the menu bar, allowing users to open menus with VO-Space bar and navigate items using VO-Down Arrow or VO-Up Arrow commands, which verbalize menu hierarchies and options for blind or low-vision users. To accommodate visual impairments, menu bars support high-contrast modes that enhance text and background differentiation, meeting WCAG 2.2 Success Criterion 1.4.3 for a minimum of 4.5:1. Resizable text options allow users to scale menu fonts up to 200% without loss of functionality, adhering to WCAG 2.2 Success Criterion 1.4.4, which improves for those with low vision. For motor impairments, functionality enables sequential key presses for menu shortcuts—such as +F for file menus—rather than simultaneous combinations, reducing physical strain and supporting users with limited dexterity as outlined in guidelines for physical disabilities. Platform-specific implementations further enhance these features. In Microsoft Windows, Narrator supports menu bar navigation by reading aloud menu items and submenus, with users employing plus to move through options and Enter to select, facilitating access for users. On Linux systems using , the supports menu bar navigation in GTK-based applications, providing verbal announcements of menu contents for visually impaired users. These adaptations collectively promote inclusive interaction with menu bars across diverse assistive technologies.

Modern Developments and Alternatives

Evolution in Contemporary Interfaces

In the shift toward touch-centric interfaces, mobile operating systems like and have largely supplanted traditional menu bars with gesture-based since the late 2000s. Apple's , launched with the original in 2007, pioneered a full-screen paradigm without persistent menu bars, relying instead on gestures—such as swiping from the edge to return or pinching to —for intuitive interaction across apps. Similarly, evolved from hardware navigation buttons in its 2008 debut to optional gesture by in 2019, which eliminates the bottom navigation bar to maximize screen immersion while supporting swipes for back, home, and recent apps functions. This transition prioritized natural hand movements over static UI elements, enhancing usability on touchscreens but challenging users accustomed to visible controls. In web and cross-platform applications, responsive design principles have accelerated the replacement of full menu bars with compact alternatives like the hamburger menu, particularly for mobile and hybrid environments. The hamburger icon—three stacked horizontal lines—collapses navigation options into a slide-out panel, conserving screen space in fluid layouts that adapt to device size. This approach is prevalent in web apps and those built with , a for apps using web technologies; for instance, Slack's Electron-based client employs a hamburger-style sidebar to streamline access to channels and settings without a traditional top menu bar. Such designs facilitate seamless cross-platform consistency, though they can obscure options until activated, prompting ongoing debates about discoverability. Recent desktop OS updates reflect a partial revival of menu bar concepts to accommodate hybrid input methods blending mouse, keyboard, touch, and remote access. In Windows 11, Microsoft announced refinements to context menus—which extend menu bar functionalities via right-click—in November 2025, introducing nested sub-menus and a "Split Context Menu" design expected to reduce visual clutter by up to 38% in WinUI apps while better supporting touch gestures alongside traditional inputs. Likewise, macOS Sonoma (2023) enhanced remote access through Screen Sharing with low-latency audio, high frame rates, and support for up to two virtual displays to enable hybrid workflows; menu bar customization options, including rearranging status menus and auto-hiding the bar, allow for more streamlined interfaces. These adaptations aim to balance legacy desktop paradigms with modern, versatile interaction models.

Alternative Navigation Paradigms

In contemporary user interfaces, particularly in and applications, several paradigms have emerged as alternatives to the traditional menu bar, emphasizing visual, gestural, or verbal interactions to streamline access to commands and reduce hierarchical depth. These approaches prioritize , , and adaptability to input methods like touch and voice, often supplanting menu bars in favor of more direct or contextual controls. One prominent alternative is the ribbon interface, introduced by in Office 2007, which organizes commands into tabbed panels with icons and grouped tools for immediate visual exposure. This design replaces the conventional menu bar and toolbars by surfacing frequently used features in a contextual, glanceable format, thereby minimizing the need to drill down through cascading menus and enhancing productivity for visual learners. The ribbon's adoption in applications like and Excel demonstrated a shift toward command-centric layouts, where tabs adapt to the active context, such as document editing or , fostering quicker task completion without relying on hidden menu structures. Gesture and voice controls represent non-hierarchical alternatives, particularly in mobile operating systems, where swipe gestures and commands bypass traditional menus altogether. Apple's , launched in 2011 with the , enables users to navigate and perform actions via spoken queries, such as setting reminders or controlling device settings, using voice as the primary interface instead of on-screen hierarchies. Similarly, Amazon's , introduced in 2014 alongside the device, integrates voice commands for seamless control of apps and smart home functions, allowing direct invocation of tasks without menu traversal and promoting hands-free interaction in diverse environments. Swipe gestures in and further exemplify this paradigm, enabling fluid transitions like pulling down for notifications or swiping up for home screens, which provide intuitive, body-relative navigation suited to touch devices and reducing dependence on persistent menu elements. Bottom navigation bars, as standardized in Google's Material Design guidelines since their 2016 update, offer thumb-friendly access on touch-enabled devices by placing 3-5 key destinations at the screen's bottom edge. This pattern facilitates one-handed use on smartphones, where users can tap icons for primary sections like , search, or , avoiding the reach challenges of top-placed menus and promoting persistent, low-commitment . Unlike menu bars, which often require precise cursor or finger targeting higher on the screen, bottom bars align with ergonomic thumb zones, improving in mobile contexts by keeping essential controls within easy reach during natural holding postures.

References

  1. [1]
    What Is a Menu Bar? - Computer Hope
    Sep 7, 2025 · A menu bar is a thin, horizontal bar containing the labels of menus in a GUI (graphical user interface).
  2. [2]
    What is a Menu Bar? - GeeksforGeeks
    Jul 23, 2025 · A menu bar is a horizontal bar that displays menu labels in a graphical user interface (GUI). The menu bar provides the user with a location in ...
  3. [3]
    How the Graphical User Interface Was Invented - IEEE Spectrum
    Sep 1, 1989 · The production Xerox Star, in 1981, featured a further advance: a menu bar, essentially a row of words indicating available menus that could be ...<|control11|><|separator|>
  4. [4]
    The menu bar | Apple Developer Documentation
    On a Mac or an iPad, the menu bar at the top of the screen displays the top-level menus in your app or game.
  5. [5]
    Menu flyout and menu bar - Windows apps | Microsoft Learn
    Feb 26, 2025 · To show a set of multiple top-level menus in a horizontal row, use menu bar (which you typically position at the top of the app window).Create A Menu Flyout · Icons · Create A Menu Bar
  6. [6]
    Menus | Apple Developer Documentation
    A menu reveals its options when people interact with it, making it a space-efficient way to present commands in your app or game.
  7. [7]
    User-Interface Elements: Glossary - NN/G
    Feb 28, 2025 · Menu Bar. A type of menu in which the collection of options is visible at all times and displayed in a horizontal or vertical list (bar).
  8. [8]
    [PDF] Improving Command Selection with CommandMaps
    Designers of GUI applications typically arrange commands in hierarchical structures, such as menus, due to screen space limitations.<|control11|><|separator|>
  9. [9]
    Expandable Menus: Pull-Down, Square, or Pie? - NN/G
    May 8, 2016 · Originally developed at PARC back in the 1970s, menus are lists of options in a graphical user interface (GUI). ... Internet Explorer menu bar ( ...
  10. [10]
    Windows 7 Toolbars - Win32 apps | Microsoft Learn
    Feb 7, 2022 · Toolbars present only the most frequently used commands, whereas menu bars catalog all the available top-level commands within a program.
  11. [11]
    Introducing the Smalltalk Zoo - CHM - Computer History Museum
    Dec 17, 2020 · The Smalltalk Zoo, created by Dan Ingalls, is a collection of historical versions of the revolutionary graphical programming and user environment Smalltalk.
  12. [12]
    The Xerox Alto, Smalltalk, and rewriting a running GUI
    Oct 22, 2017 · We succeeded in running the Smalltalk-76 language on our vintage Xerox Alto; this blog post gives a quick overview of the Smalltalk environment.
  13. [13]
    Of Modes and Men - IEEE Spectrum
    Browser: When Tesler was developing his page-paste-up system at Xerox PARC, researcher Alan Kay would repeatedly complain that no one had found a good way to ...Missing: origins | Show results with:origins
  14. [14]
    Xerox Parc's Engineers on How They Invented the Future
    Alan Kay, whose “Smalltalk” group created overlapping windows, is perhaps PARC's most famous alumnus. After spending 10 years at PARC, he became chief scientist ...Missing: origins | Show results with:origins
  15. [15]
    [PDF] Origins of the Apple human interface : Larry Tesler and Chris Espinosa
    Oct 28, 1997 · In one night he invented the entire mechanism of the menu bar at the top of the screen. To me it was just a place to put what he already had ...
  16. [16]
    Memories of Lisa - CHM - Computer History Museum
    Jan 30, 2025 · Moving the menu bar to the top of the screen. Atkinson also recounts how he was recruited to Apple by Steve Jobs to help “change the world.Missing: global | Show results with:global
  17. [17]
    The Lisa: Apple's Most Influential Failure - Computer History Museum
    Jan 19, 2023 · The invention of the GUI, especially in the form of windows, icons, menus, and pointer (WIMP), controlled by a mouse, occurred at Xerox PARC in ...
  18. [18]
    GUIdebook > Articles > “The Lisa user interface”
    Apple's Lisa, introduced in January 1983, was the bridge between the first commercial graphical desktop system, the Xerox Star (April 1982), and the Apple ...Missing: global | Show results with:global
  19. [19]
    A History of the GUI - Ars Technica
    May 4, 2005 · I'll be presenting a brief introduction to the history of the GUI. The topic, as you might expect, is broad, and very deep.
  20. [20]
    About Menus - Win32 apps | Microsoft Learn
    Aug 19, 2020 · The user makes the menu bar active by pressing the ALT key to highlight the first item on the menu bar. A menu is active when it is displayed.Missing: navigation | Show results with:navigation
  21. [21]
    [PDF] LECTURE 6, INTERACTION STYLES - LIACS
    Sep 22, 2014 · The five primary interaction styles are: direct manipulation, menu selection, form filling, command language, and natural language.
  22. [22]
    A glimpse into the history of Windows design
    Mar 27, 2025 · Harold Gomez, Jeremy Knudsen, and Kim Sealls are three designers at Microsoft who have contributed to Windows design since 2000 and witnessed its design ...
  23. [23]
    Designing the Ribbon — Jensen Harris
    The Ribbon eventually made its way elsewhere within Microsoft. Notably, it showed up in several of the Windows built-in apps, adorning Paint, WordPad, and File ...
  24. [24]
    How the Windows Start menu has evolved in Microsoft's 50 years
    Mar 24, 2025 · The menu was originally introduced in 1995, and it has undergone significant transformations, adapting to user needs and advances in technology.
  25. [25]
    [PDF] The X Window System
    When the user clicks on a menu bar item with any button, the manager unilaterally grabs the mouse. The user then uses the mouse to execute the specific ...
  26. [26]
    [PDF] X Window System Protocol - X Consortium Standard - X.Org
    Scheifler. X Consortium, Inc. Page 9. 1. Chapter 1. Protocol Formats. Request Format. Every request contains an 8-bit major opcode and a 16-bit length field ...
  27. [27]
    Gtk.MenuBar
    The GtkMenuBar is a subclass of GtkMenuShell which contains one or more GtkMenuItems. The result is a standard menu bar which can hold many menu items.Missing: documentation | Show results with:documentation
  28. [28]
    QMenuBar Class | Qt Widgets | Qt 6.10.0
    A menu bar consists of a list of pull-down menu items. You add menu items with addMenu(). For example, assuming that menubar is a pointer to a QMenuBar and ...Missing: Unix | Show results with:Unix
  29. [29]
    GNOME at 20: Four reasons it's still my favorite GUI | Opensource.com
    Aug 15, 2017 · The top panel included the GNOME Applications menu, an Actions menu, and shortcuts to frequently used applications. The bottom panel provided ...
  30. [30]
    Chapter 3. Finding Your Way Around - KDE Documentation -
    KDE uses widgets, common menus, and elements like the menubar, titlebar, and toolbar. Windows have a central widget, and menus are accessed via menubars or  ...
  31. [31]
    Wayland - ArchWiki
    Wayland solves this by adding protocol extensions for Wayland and Xwayland. Support for these extensions is needed to be added to the Wayland compositors.
  32. [32]
    Wayland Explorer: Wayland Protocol Documentation
    The most popular Wayland protocols all in one place and without having to sift through different repositories and XML files. Start by reading the core Wayland ...Core Wayland protocol · Workspace protocol · Fifo protocol · KDE AppMenu
  33. [33]
    The history of the AmigaOS Graphic User Interface (GUI): Release 1.1
    Release date: December 1985. Shipped with: Amiga 1000, available as a stand-alone update. Media: Kickstart on disk (256 KB), new software.
  34. [34]
    Historical Operating Systems – AmigaOS | A Technophile's Indulgence
    May 26, 2010 · By providing full pre-emptive multitasking in 1985, AmigaOS was even further ahead of its contemporaries than it had been with its lauded ...Missing: implementation | Show results with:implementation
  35. [35]
    Discover AmigaOS: The First Multitasking OS for PCs
    Oct 21, 2025 · Launched in 1985 for the Commodore Amiga line, AmigaOS marked a significant leap forward in personal computing. It introduced true preemptive ...
  36. [36]
    [PDF] NeXTstep Concepts - Bitsavers.org
    A presentation of the principles that define NeXTstep, including user interface design, object-oriented ... Display PostScript and PostScript are ...Missing: 1988 | Show results with:1988
  37. [37]
    MacUser, January 1997: NeXTSTEP Technical Review - Paul Lynch
    NeXT worked with Adobe to develop a version of Postscript, called Display Postscript, that was optimised to drive both printers and displays. Sun had done ...
  38. [38]
    [PDF] Programmer's Guide Volume 2: AES - Bitsavers.org
    An application's menu bar is controlled by the GEM AES Screen. Manager; the application is not responsible for user interaction with the menu bar. The ...Missing: TOS | Show results with:TOS
  39. [39]
    History of the GEM Desktop Environment
    Sep 13, 2025 · Atari 520 ST, soon nicknamed “Jackintosh”, was introduced at the 1985 Consumer Electronics Show in Las Vegas and became an immediate hit. GEM ...
  40. [40]
    GUIdebook > GUIs > Featured interfaces
    Since in 1987 RISC OS was still not ready for prime time, and the new Acorn ... menus and interesting use of drag and drop throughout the GUI. RISC OS ...
  41. [41]
    The RISC OS Products Directory - RISCOS Ltd
    There are two types of drop with regard to applications - dropping on the icon bar opens a new window whilst dropping on an open window appends the data. There ...
  42. [42]
    Fitts's Law and Its Applications in UX - NN/G
    Jul 31, 2022 · Fitts's law clearly says that people will be faster to click, tap, or hover on bigger targets. Not only that, but error rates go down as target sizes increases.
  43. [43]
    http://www.riscos.com/the_archive/rol/productsdb/admin/riscos.htm
  44. [44]
    Few Guesses, More Success: 4 Principles to Reduce Cognitive ...
    structure, transparency, clarity, and support — minimize users' cognitive load and improve usability.Missing: deep nesting HCI<|control11|><|separator|>
  45. [45]
    Why it's quick to be square: modelling new and existing hierarchical ...
    We consider different hierarchical menu and toolbar-like interface designs from a theoretical perspective and show how a model based on visual search time ...Missing: completion | Show results with:completion
  46. [46]
    Menu-Design Checklist: 17 UX Guidelines - NN/G
    Jun 7, 2024 · Summary: People rely on menus to find content and use features. Use this checklist to make sure your menus do their job.
  47. [47]
    How to Overcome Disorientation in Mobile Phone Menus
    Aug 6, 2025 · The current study was concerned with the basic question of how to overcome users' disorientation when navigating through hierarchical menus ...
  48. [48]
    Miller's Law | Laws of UX
    The average person can only keep 7 (plus or minus 2) items in their working memory. Takeaways. Don't use the “magical number seven” to justify unnecessary ...Missing: HCI | Show results with:HCI
  49. [49]
    The depth/breadth trade-off in the design of menu-driven user ...
    An experiment is reported investigating the role of depth and breadth of menus and tree structures in user interfaces for information-retrieval systems.Missing: 1989 | Show results with:1989
  50. [50]
    Navigation Menubar Example | APG | WAI - W3C
    Aug 12, 2025 · Defines an accessible name for the menu . Helps assistive technology users understand the purpose of the menu and distinguish it from any other ...
  51. [51]
    Navigate menus with VoiceOver on Mac - Apple Support
    Navigate a menu · Open any menu: Press VO-Space bar. · Move down or up a menu: Press VO-Down Arrow or VO-Up Arrow, or drag a finger down or up on the trackpad.
  52. [52]
    https://www.w3.org/WAI/ARIA/apg/patterns/menubar/examples/menubar-navigation/
  53. [53]
    https://support.apple.com/guide/voiceover/menu-bar-mchlp2748/mac
  54. [54]
    Physical | Web Accessibility Initiative (WAI) - W3C
    Jun 25, 2024 · They may need more time to type, click, or carry out other interactions, and they may type single keystrokes in sequence or use sticky keys ...
  55. [55]
    How to Enable and Use Windows Narrator - YuJa Help Center
    Aug 29, 2024 · Use Caplocks + Navigation keys to navigate between selectable options of the selected item. Use Enter to choose a selectable menu option.<|control11|><|separator|>
  56. [56]
    Structural Navigation Commands - Orca
    The following commands can be used to navigate by headings, links, and other elements found in applications for which Orca provides structural navigation ...
  57. [57]
    Gesture Navigation: A Backstory - Android Developers Blog
    Aug 8, 2019 · By moving to a gesture model for system navigation, we can provide more of the screen to apps to enable a more immersive experience. We wanted ...
  58. [58]
    https://help.gnome.org/users/orca/stable/index.html.en
  59. [59]
    https://android-developers.googleblog.com/2019/08/gesture-navigation-backstory.html
  60. [60]
    Creating a custom menu bar in Electron - Sai Sandeep Vaddi
    Feb 2, 2020 · This tutorial gives details about how to build a hamburger type menu bar in electron apps similar to slack's menu bar.
  61. [61]
    How the Hamburger Menu Simplifies Ecommerce Navigation - Shopify
    Apr 10, 2025 · The tidy size of the icon is the hamburger menu's reason for being, conserving precious screen real estate and decluttering the web design.
  62. [62]
    https://saisandeepvaddi.com/blog/how-to-create-custom-menu-bar-in-electron
  63. [63]
    How to Customize Your Menu Bar in macOS Sonoma | Badgeify
    Aug 6, 2024 · Users can customize the menu bar by choosing which items to show, rearranging status menus, and setting an option to automatically hide it when not in use.
  64. [64]
    macOS Sonoma brings new capabilities for elevating productivity ...
    Jun 5, 2023 · Enhancing Hybrid and Remote Pro Workflows. Leveraging the advanced media engine in Apple silicon, macOS Sonoma brings a new high performance ...
  65. [65]
    An Alternative Voice UI To Voice Assistants - Smashing Magazine
    Jun 18, 2021 · A voice assistant is a piece of software that uses natural language instead of icons and menus as its user interface. Assistants typically ...
  66. [66]
    Windows 7 Ribbons - Win32 apps - Microsoft Learn
    Feb 8, 2022 · A ribbon can replace both the traditional menu bar and toolbars. ... Ribbons were originally introduced with Microsoft Office 2007. To ...
  67. [67]
    10 years of Siri: the history of Apple's voice assistant - TechRadar
    Oct 4, 2021 · The Apple voice assistant was originally integrated into the iPhone 4S way back in October 2011, and we're now here to wish Siri a very happy 10th birthday.
  68. [68]
    Amazon surprises with new device, a voice assistant - CNBC
    Nov 6, 2014 · Amazon surprises with new device, a voice assistant. Published Thu, Nov 6 2014 ... "Introducing Amazon Echo. Always ready, connected, and fast.
  69. [69]
    Navigation bar – Material Design 3
    A new flexible navigation bar was introduced to replace the original navigation bar. It's shorter and supports horizontal navigation items in medium windows.Missing: 2014 | Show results with:2014
  70. [70]
    Bottom Tab Bar Navigation Design Best Practices - UX Planet
    Apr 2, 2024 · A bottom navigation bar is easier to reach with the thumb on mobile devices and hence becomes the more user-friendly approach. Press enter ...