The desktop application presents a redundant navigation issue where the core action options contained within the top application menu bar (File, Edit, Stage, Camera, Help) are duplicated across the main canvas elements and drop-down selectors, creating interface clutter and confusion[cite: 9].
Issue Description
In the main workspace view of Spiker Stack, when interacting with the interface:
Menu Duplication: The top menu bar provides standard application controls (File, Edit, Stage, Camera, Help). Simultaneously, the central empty state displays an expanded dropdown (+ Add Images...) duplicating identical functional routes such as "Import Folder...", "Open Project...", and "Capture from Camera"[cite: 9].
Visual Clutter: Having overlapping access points for the exact same core actions in both the top system bar and the central canvas leads to a redundant and cluttered user experience.
Preconditions
The application is open in desktop mode on the initial or empty project workspace (Spiker Stack)
The top menu bar and the central "No images yet" state are fully visible
Environment
Property
Value
Application
Spiker Stack
Environment
Production 10.30a
Operating System
Windows 11 - 25H2
Device
Desktop
Language
English
Steps to Reproduce
Launch the Spiker Stack desktop application
Review the top application menu bar (File, Edit, Stage, Camera, Help)
Click on the central + Add Images... dropdown button in the middle of the canvas
Observe that the expanded options (Import Folder..., Open Project..., Capture from Camera) mirror actions already accessible or handled via the top menu bar and bottom cards, causing feature redundancy
Expected Result
Application navigation and action entry points should be clearly segregated: the top menu bar should handle global system commands, while the main canvas should feature distinct, non-redundant contextual workflows.
Avoid duplicating the exact same sub-options across multiple conflicting UI layers.
Actual Result
Core actions are repetitively duplicated between the top menu bar and the center canvas dropdown menus, cluttering the workspace layout
Evidence
Top Menu Bar: Standard system menus (File, Edit, Stage, Camera, Help)
Center Canvas: Expanded + Add Images... dropdown showing duplicate import and capture options (Import Folder..., Open Project..., Capture from Camera) alongside corresponding shortcut cards below
Impact
UX Friction: Clutters the interface with redundant control paths, increasing cognitive load for the user
Frequency
Always
Reproducibility
100%
Notes & Recommendations
Streamline navigation by removing duplicated dropdown items from the central canvas if they are already standard entries within the top File / Stage menu headers.
## Summary
The desktop application presents a redundant navigation issue where the core action options contained within the top application menu bar (File, Edit, Stage, Camera, Help) are duplicated across the main canvas elements and drop-down selectors, creating interface clutter and confusion[cite: 9].
## Issue Description
In the main workspace view of *Spiker Stack*, when interacting with the interface:
1. *Menu Duplication:* The top menu bar provides standard application controls (File, Edit, Stage, Camera, Help). Simultaneously, the central empty state displays an expanded dropdown (+ Add Images...) duplicating identical functional routes such as "Import Folder...", "Open Project...", and "Capture from Camera"[cite: 9].
2. *Visual Clutter:* Having overlapping access points for the exact same core actions in both the top system bar and the central canvas leads to a redundant and cluttered user experience.
## Preconditions
- The application is open in desktop mode on the initial or empty project workspace (Spiker Stack)
- The top menu bar and the central "No images yet" state are fully visible
## Environment
| Property | Value |
|-----------|--------|
| Application | Spiker Stack |
| Environment | Production 10.30a |
| Operating System | Windows 11 - 25H2 |
| Device | Desktop |
| Language | English|
## Steps to Reproduce
1. Launch the *Spiker Stack* desktop application
2. Review the top application menu bar (File, Edit, Stage, Camera, Help)
3. Click on the central + Add Images... dropdown button in the middle of the canvas
4. Observe that the expanded options (Import Folder..., Open Project..., Capture from Camera) mirror actions already accessible or handled via the top menu bar and bottom cards, causing feature redundancy
## Expected Result
- Application navigation and action entry points should be clearly segregated: the top menu bar should handle global system commands, while the main canvas should feature distinct, non-redundant contextual workflows.
- Avoid duplicating the exact same sub-options across multiple conflicting UI layers.
## Actual Result
- Core actions are repetitively duplicated between the top menu bar and the center canvas dropdown menus, cluttering the workspace layout
## Evidence
- *Top Menu Bar:* Standard system menus (File, Edit, Stage, Camera, Help)
- *Center Canvas:* Expanded + Add Images... dropdown showing duplicate import and capture options (Import Folder..., Open Project..., Capture from Camera) alongside corresponding shortcut cards below
## Impact
- *UX Friction:* Clutters the interface with redundant control paths, increasing cognitive load for the user
## Frequency
Always
## Reproducibility
100%
## Notes & Recommendations
- Streamline navigation by removing duplicated dropdown items from the central canvas if they are already standard entries within the top File / Stage menu headers.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
The desktop application presents a redundant navigation issue where the core action options contained within the top application menu bar (File, Edit, Stage, Camera, Help) are duplicated across the main canvas elements and drop-down selectors, creating interface clutter and confusion[cite: 9].
Issue Description
In the main workspace view of Spiker Stack, when interacting with the interface:
Preconditions
Environment
Steps to Reproduce
Expected Result
Actual Result
Evidence
Impact
Frequency
Always
Reproducibility
100%
Notes & Recommendations