app-shortcuts-taskbar

byFaisal

An app for Windows 10/11: Interface: Just an icon on the task bar that when clicked pops a menu up with user specified app names in it which when clicked opens the selected app The Linked Apps: To be saved as app shortcuts in a folder on any user specied drive and folder Taskbar Icon: Must be customizable from Windows icon options Loading: Must load on Windows startup

No preview

Comments (0)

No comments yet. Be the first!

System Requirements

System Requirements Document for Linked Apps

1. Introduction

Linked Apps is a small Windows 10/11 utility whose entire interface is a single taskbar icon. Clicking that icon pops up a menu of user-specified app names; clicking a name opens that app. The linked apps are stored as ordinary app shortcuts in a folder on a drive and folder the user chooses, the taskbar icon is customizable from Windows icon options, and the utility loads automatically on Windows startup.

The product intent is exactness and speed: one icon, one menu, one click to the app the user wants, with the shortcut folder remaining a plain, inspectable folder on the user's own disk. The audience is a single Windows user who wants a personal, always-available launcher that stays out of the way.

Page 1 of 22

2. System Overview

Linked Apps is delivered as a Windows 10/11 desktop utility with a taskbar presence and a small set of first-party configuration surfaces. The utility runs in the background after Windows startup, exposes one taskbar icon, and opens a pop-up menu listing the user-specified app names. Selecting a name launches the corresponding app. The linked apps are persisted as app shortcuts (.lnk files) inside a user-selected drive and folder, so the folder itself is the durable record of what the menu contains.

Actors:

  • Windows user — the single active human persona. Adds app names to the menu, chooses the shortcut drive and folder, customizes the taskbar icon, and opens apps from the menu.
  • Windows shell / operating system — provider-owned surface that hosts the taskbar icon, supplies the Windows icon options used for customization, and runs the utility at startup.
  • Linked Apps background process — system process that keeps the taskbar icon present, reads the shortcut folder, and launches the selected app.

Current delivery covers: Windows 10 and Windows 11 support; one taskbar icon; a click-opened pop-up menu of user-specified app names; click-to-open of the selected app; shortcut storage in a user-specified drive and folder; taskbar icon customization from Windows icon options; and automatic load on Windows startup.

Narrow exclusions: there is no multi-user account system, no cloud sync, no cross-device sharing of the shortcut folder, and no interface beyond the taskbar icon and its pop-up menu plus the configuration surfaces described below.

Removed from scope

Page 2 of 22
  • None. No concept from the authoritative requirement thread was removed.

2a. Product Interpretation and Delivery Boundary

Linked Apps is a local, single-user Windows utility. Its primary working surface is the Windows taskbar: one icon, owned by the application, that opens a pop-up menu. The menu is the product's main interaction; everything else exists to keep that menu correct.

The linked apps are not stored in an opaque application database. They are stored as app shortcuts in a folder on a drive and folder the user selects. That folder is the authoritative record of the menu's contents: adding an app to the menu creates a shortcut there, and the menu reflects the shortcuts present. This keeps the user's data inspectable, movable, and independent of the utility.

Configuration is deliberately small and lives in first-party surfaces reachable from the taskbar icon: a Menu Apps surface for adding an app name to the menu, and a Settings surface for choosing the shortcut drive and folder and for customizing the taskbar icon from Windows icon options. A Landing surface introduces the utility and leads into the menu. The Menu itself is the pop-up surface opened by the taskbar icon.

Access is local and unauthenticated: the utility runs as the signed-in Windows user, and no account, sign-in, or remote identity is part of the product. The Windows shell owns the taskbar, the icon-options dialog, and startup execution; Linked Apps owns the menu, the configuration surfaces, and the shortcut folder contents.

Future boundaries are not part of current acceptance; nothing beyond the requirements above is committed.

Page 3 of 22

2b. Source Content Inventory

Not applicable — no reference directive declares content_source.

2c. Page Content and Component Coverage

Landing

  • Information/state: product name "Linked Apps"; hero headline "One icon. Every app you need."; subline "Linked Apps puts your chosen apps in one taskbar menu and keeps their shortcuts in your folder."; a rendered taskbar menu specimen; a ruled row of folder paths in JetBrains Mono tabular numerals; current shortcut-folder path and linked-app count when configured, and an unconfigured state prompting the user to choose a folder.
  • Primary action: "See the menu" — opens the Menu surface.
  • Supporting actions: open Settings to choose the shortcut drive and folder; open Menu Apps to add an app name.
  • Domain entities: shortcut folder path; linked app (name, shortcut file); linked-app count.
  • Component responsibilities: taskbar strip pinned to the top edge with one tangerine icon button; hero two-panel split (type left, menu specimen right); ruled folder-path row; section headings on a full-width 1px ink rule with a small mono number.
  • States: loading (reading the shortcut folder); empty (no folder chosen or no shortcuts yet, with a prompt to choose a folder or add an app); success (path and count shown); error (folder unreadable or drive unavailable, with the failing path and a retry plus a link to Settings); recovery (re-choose the folder in Settings and return).
Page 4 of 22

Menu

  • Information/state: the pop-up panel opened by the taskbar icon; the list of user-specified app names read from the shortcut folder; the hovered row marked with a tangerine left marker; app count in JetBrains Mono tabular numerals.
  • Primary action: click an app name to open the selected app.
  • Supporting actions: open Menu Apps to add an app name; open Settings to change the shortcut folder or taskbar icon; dismiss the menu.
  • Domain entities: linked app (name, shortcut file, target); shortcut folder path.
  • Component responsibilities: menu panel with hairline border and one soft lift; hairline rows; tangerine left marker on the hovered row; short scale-and-fade open transition (120–200ms).
  • States: loading (reading the shortcut folder on open); empty (no shortcuts present, with a prompt to add an app); success (rows listed, selected app launched); error (shortcut missing or target unavailable, with the failing app named and the menu remaining open); recovery (re-add the app in Menu Apps or fix the folder in Settings).
Page 5 of 22

Menu Apps

  • Information/state: ruled label-and-value rows listing the app names currently in the menu; an input for the app name to add; the shortcut folder path the new shortcut will be written to.
  • Primary action: add an app name to the taskbar menu, writing its shortcut into the selected folder.
  • Supporting actions: remove an app name from the menu; open Settings to change the shortcut folder.
  • Domain entities: linked app (name, shortcut file, target); shortcut folder path.
  • Component responsibilities: ruled rows; name input; add and remove controls; inline validation messages; mono path display.
  • States: loading (reading the folder); empty (no apps yet, with a prompt to add the first); success (new row appears and the shortcut exists in the folder); error (no folder chosen, folder not writable, duplicate name, or invalid name, with the reason shown and input preserved); recovery (choose a folder in Settings or correct the name and retry).
Page 6 of 22

Settings

  • Information/state: the current shortcut drive and folder path; the current taskbar icon; startup status.
  • Primary action: select the drive and folder where app shortcuts are saved.
  • Supporting actions: customize the taskbar icon from Windows icon options; confirm that the utility loads on Windows startup.
  • Domain entities: shortcut folder path (drive and folder); taskbar icon selection.
  • Component responsibilities: ruled label-and-value rows; folder picker; Windows icon-options entry point; mono path display; save confirmation.
  • States: loading (reading current settings); empty (no folder chosen yet); success (folder saved and confirmed, icon updated); error (drive unavailable, folder not writable, or icon selection rejected, with the reason shown and the previous value retained); recovery (choose another folder or icon and save again).
Page 7 of 22

3. Functional Requirements

FR-1 — Windows 10/11 support (explicit) As a Windows user, I should run Linked Apps on Windows 10 and Windows 11 so that the utility works on my machine.

  • Trigger: launching the utility on a Windows 10 or Windows 11 system.
  • Observable result: the utility runs and its taskbar icon is present.
  • Failure/recovery: on an unsupported Windows version the utility does not present the taskbar icon and reports the unsupported platform.
  • Continuation: the user proceeds to configure the shortcut folder and add apps.

FR-2 — Single taskbar icon (explicit) As a Windows user, I should see exactly one Linked Apps icon on the taskbar so that the interface stays out of the way.

  • Trigger: the utility running.
  • Observable result: one icon appears on the taskbar; no other persistent interface is shown.
  • Failure/recovery: if the icon cannot be registered, the utility reports the failure and retries registration.
  • Continuation: the user clicks the icon.
Page 8 of 22

FR-3 — Click opens the pop-up menu (explicit) As a Windows user, I should click the taskbar icon and get a pop-up menu so that I can reach my apps in one click.

  • Trigger: click on the taskbar icon.
  • Observable result: the Menu surface opens as a pop-up panel with a short scale-and-fade transition.
  • Failure/recovery: if the shortcut folder cannot be read, the menu opens in its error state naming the failing path, with retry and a link to Settings.
  • Continuation: the user selects an app name or opens Menu Apps or Settings.

FR-4 — Menu lists user-specified app names (explicit) As a Windows user, I should see my user-specified app names in the pop-up menu so that I can pick the app I want.

  • Trigger: the Menu surface opening.
  • Observable result: the menu lists the app names corresponding to the shortcuts in the selected folder, with the hovered row marked by a tangerine left marker.
  • Failure/recovery: with no shortcuts present the menu shows its empty state with a prompt to add an app.
  • Continuation: the user clicks a name.
Page 9 of 22

FR-5 — Click an app name opens the selected app (explicit) As a Windows user, I should click an app name in the menu and have that app open so that launching is one click.

  • Trigger: click on an app name in the Menu surface.
  • Observable result: the selected app launches and the menu dismisses.
  • Failure/recovery: if the shortcut is missing or its target is unavailable, the menu stays open, names the failing app, and offers recovery through Menu Apps or Settings.
  • Continuation: the user opens another app or dismisses the menu.

FR-6 — Shortcuts saved in a user-specified drive and folder (explicit) As a Windows user, I should have my linked apps saved as app shortcuts in a folder on a drive and folder I specify so that my launcher data lives where I choose.

  • Trigger: the user selecting a drive and folder in Settings, and adding an app name in Menu Apps.
  • Observable result: each linked app exists as an app shortcut file inside the selected folder, and the menu reflects the shortcuts present.
  • Failure/recovery: if the drive is unavailable or the folder is not writable, the save fails with the reason shown and the previous folder retained.
  • Continuation: the user chooses another folder or fixes access and retries.
Page 10 of 22

FR-7 — Taskbar icon customizable from Windows icon options (explicit) As a Windows user, I should customize the taskbar icon from Windows icon options so that the icon matches my setup.

  • Trigger: the user opening icon customization from Settings.
  • Observable result: the Windows icon options are presented and the chosen icon becomes the taskbar icon.
  • Failure/recovery: if the selection is rejected, the previous icon is retained and the reason is shown.
  • Continuation: the user returns to Settings with the icon confirmed.

FR-8 — Loads on Windows startup (explicit) As a Windows user, I should have Linked Apps load on Windows startup so that the icon is available without launching it manually.

  • Trigger: Windows startup for the signed-in user.
  • Observable result: the utility starts in the background and its taskbar icon is present.
  • Failure/recovery: if startup registration is missing or disabled, Settings shows the startup status so the user can restore it.
  • Continuation: the user clicks the icon as usual.

FR-9 — Startup registration is established (required_inference) As a Windows user, I should have the utility registered to load at Windows startup so that FR-8 is executable.

  • Trigger: first run of the utility.
  • Observable result: the startup registration exists for the signed-in user and Settings reports it as active.
  • Failure/recovery: if registration fails, Settings reports the inactive status.
  • Continuation: the user relies on the icon being present after the next startup.
Page 11 of 22

FR-10 — Shortcut folder selection (required_inference) As a Windows user, I should select a drive and folder for the app shortcuts so that FR-6 has a destination.

  • Trigger: first use, or the user opening Settings.
  • Observable result: the selected drive and folder are saved and displayed as the shortcut folder path; the menu and Menu Apps read and write that folder.
  • Failure/recovery: an unavailable drive or unwritable folder is rejected with the reason shown and the previous value retained.
  • Continuation: the user adds app names in Menu Apps.

4. User Personas

Page 12 of 22

Windows user

  • Product context: a single person working on their own Windows 10 or Windows 11 machine who wants a personal launcher pinned to the taskbar rather than a Start-menu search or desktop clutter.
  • Primary goal: reach any of their chosen apps with one click on one taskbar icon, while keeping the shortcuts in a folder they control.
  • Distinct accepted responsibilities: choosing the drive and folder where app shortcuts are saved; adding user-specified app names to the menu (and removing them); customizing the taskbar icon from Windows icon options; clicking the taskbar icon to open the menu and clicking an app name to open that app; relying on the utility loading at Windows startup.
  • Relevant inputs or decisions: the drive and folder path; the app names to include; the icon choice from Windows icon options.
  • Interactions with other accepted participants: the Windows shell hosts the taskbar icon, supplies the icon options, and runs the utility at startup; the Linked Apps background process reads the shortcut folder and launches the selected app. The user is the only human participant.
  • Observable success: the icon is on the taskbar after startup, the menu lists exactly the chosen app names, clicking a name opens that app, and the shortcut files are visible in the chosen folder.

5. Core User Flows

Page 13 of 22

Flow A — First run: choose the shortcut folder

  1. The Windows user starts Linked Apps for the first time on Windows 10 or Windows 11. The utility registers itself to load at Windows startup (FR-9) and places its single taskbar icon (FR-2).
  2. The user opens Settings from the taskbar icon.
  3. Settings shows no shortcut folder chosen yet and prompts the user to select a drive and folder.
  4. The user picks a drive and folder. Linked Apps validates that the drive is available and the folder is writable.
  5. On success, Settings shows the saved folder path in JetBrains Mono tabular numerals and confirms the save. On failure, Settings shows the reason and keeps the previous value; the user picks another folder and retries.
  6. Next step: the user adds app names in Menu Apps (Flow B).

Flow B — Add an app name to the menu

  1. The user opens Menu Apps from the taskbar icon.
  2. Menu Apps lists the app names currently in the menu (empty on first use) and shows the shortcut folder path the new shortcut will be written to.
  3. The user enters an app name and confirms.
  4. Linked Apps writes an app shortcut for that app into the selected folder and the new row appears in Menu Apps.
  5. If no folder is chosen, the folder is not writable, the name is a duplicate, or the name is invalid, Menu Apps shows the reason, preserves the input, and offers the route to Settings or a corrected retry.
  6. Next step: the user opens the Menu (Flow C) or adds another app.
Page 14 of 22

Flow C — Open an app from the taskbar menu

  1. The user clicks the Linked Apps icon on the taskbar.
  2. The Menu panel opens with a short scale-and-fade transition and lists the user-specified app names read from the shortcut folder; the hovered row carries a tangerine left marker.
  3. The user clicks an app name.
  4. Linked Apps launches the selected app and dismisses the menu.
  5. If the shortcut is missing or its target is unavailable, the menu stays open, names the failing app, and offers recovery through Menu Apps (re-add) or Settings (fix the folder).
  6. Next step: the user opens another app or dismisses the menu.

Flow D — Customize the taskbar icon

  1. The user opens Settings from the taskbar icon.
  2. The user opens icon customization, which presents the Windows icon options.
  3. The user chooses an icon.
  4. Linked Apps applies the choice and the taskbar icon updates; Settings confirms the current icon.
  5. If the selection is rejected, the previous icon is retained and the reason is shown; the user chooses again.
  6. Next step: the user returns to the menu or dismisses Settings.
Page 15 of 22

Flow E — Startup availability

  1. The user signs in to Windows.
  2. Windows runs Linked Apps from its startup registration; the utility starts in the background and its taskbar icon appears.
  3. The user clicks the icon and proceeds with Flow C.
  4. If the startup registration is missing or disabled, Settings shows the inactive startup status so the user can restore it.

Flow F — Landing introduction

  1. The user opens the Landing surface.
  2. Landing shows the headline "One icon. Every app you need.", the subline, a rendered taskbar menu specimen, and a ruled row of folder paths with the current shortcut folder and linked-app count (or an unconfigured prompt).
  3. The user selects "See the menu" to open the Menu, or opens Settings or Menu Apps from the supporting actions.
  4. If the shortcut folder is unreadable, Landing shows the failing path with retry and a link to Settings.
Page 16 of 22

6. Visuals Colors and Theme

Muse: Rasmus Andersson. Headline: Systematic product craft with an opinion — exact, fast, out of the way.

Light mode tokens

RoleValue
Background (warm paper)#F6F3EE
Surface#FFFFFF
Text / ink#141517
Primary (tangerine, primary action only)#E4572E
Accent (green, open and saved states)#1F7A5C
Muted#6E6A63

Typography

  • Headings: Space Grotesk, 700 weight, tight tracking, sentence case.
  • Body: Inter Tight.
  • Paths and counts: JetBrains Mono, tabular numerals.
  • Modular scale (1.25): 72 / 56 / 40 / 28 / 18 / 16 px.

Shape and surface

  • Hairline 1px borders; 6px control radii; sharp section edges.
  • No shadows except one soft lift on the open menu panel.

Layout

Page 17 of 22
  • 12-column grid with compact controls.
  • Hero: wide two-panel split — type on the left across 6 columns, a large menu specimen on the right.
  • Settings and Menu Apps use ruled label-and-value rows.
  • Section headings sit on a full-width 1px ink rule with a small mono number at the left.

Imagery

  • The interface is the image: a rendered taskbar menu panel, schematic folder paths, and monospace data rows. No stock photos.

Avoid

  • No blue or indigo primary colour; no gradient blobs or glass panels; no identical hover-lift card grid; no centred headline with subtext and a rounded button.

7. Signature Design Concept

The public entry is a full-width warm paper field (#F6F3EE). A taskbar strip is pinned to the top edge carrying one tangerine icon button; clicking it opens the menu panel specimen on the right half of the hero. The left half holds the 72px Space Grotesk headline "One icon. Every app you need." flush left across 6 columns, with the subline beneath and the "See the menu" action. The right half holds one large open taskbar menu panel with a hairline border, hairline rows, and a tangerine left marker on the hovered row. A ruled row of folder paths in JetBrains Mono tabular numerals runs under both halves, showing the current shortcut folder and linked-app count. The composition recomposes only accepted content and controls: the icon button opens the Menu surface, and the folder-path row reflects the configured shortcut folder.

Page 18 of 22

8. Interaction Model & Motion Direction

Interaction Model: Animated Motion Tempo: restrained Hero Dimensionality: flat

Landing Hero Motion Brief

  • Focal subject: the taskbar strip with its single tangerine icon button, and the large open menu panel specimen beside the headline.
  • Input → transformation → outcome thesis: clicking the tangerine icon button opens the menu panel with a short scale-and-fade (120–200ms); the hovered row receives the tangerine left marker; the outcome is the Menu surface presented, matching the accepted click-to-open behavior.
  • Motion vocabulary: fast functional transitions only — 120–200ms scale and fade on the menu panel, immediate marker placement on row hover. No decorative loops.
  • Composed first frame: warm paper field; taskbar strip pinned top with one tangerine icon button; 72px headline flush left across 6 columns; menu panel specimen on the right with hairline rows and one marked row; ruled folder-path row beneath both halves.
  • Reduced-motion state: the menu panel appears without scale or fade, the marker is placed without transition, and all content remains fully readable in a static arrangement.
Page 19 of 22

9. Non-Functional Requirements

  • Platform: the utility must run on Windows 10 and Windows 11 (explicit).
  • Interface minimalism: the persistent interface is only an icon on the taskbar (explicit).
  • Startup: the utility must load on Windows startup (explicit).
  • Shortcut storage: linked apps must be saved as app shortcuts in a folder on a user-specified drive and folder (explicit).
  • Icon customization: the taskbar icon must be customizable from Windows icon options (explicit).
  • Responsiveness: menu open and row interactions complete within 120–200ms functional transitions (creative direction).
  • Readability: headlines, labels, numbers, and controls remain whole and inside the viewport and their container at 375px, 768px, and 1280px, wrapping or scaling to fit (creative direction).
  • Reduced motion: with prefers-reduced-motion, a usable static arrangement is provided (creative direction).
  • Local-only data: shortcut data lives in the user-selected folder; no cloud sync or cross-device sharing is part of the product (explicit boundary).
Page 20 of 22

10. Tech Stack

  • Frontend: React application UI for the Landing, Menu, Menu Apps, and Settings surfaces.
  • Backend: shared FastAPI process for application APIs and domain modules (shortcut folder validation, shortcut creation and listing, settings persistence).
  • Database: MariaDB for application-owned persistent data (selected shortcut folder path, taskbar icon selection, startup registration status).
  • Desktop shell: Windows 10/11 taskbar integration providing the single taskbar icon, the pop-up menu host, Windows icon options, and startup registration.
  • Deployment: Docker / docker-compose for the backend and database services.

11. Assumptions and Constraints

  • A-1: The utility runs as the signed-in Windows user; no account, sign-in, or remote identity is part of the product (explicit boundary).
  • A-2: The shortcut folder is the authoritative record of the menu's contents; the menu reflects the shortcuts present in it (required_inference).
  • A-3: The Windows shell owns the taskbar, the icon-options dialog, and startup execution; Linked Apps owns the menu, configuration surfaces, and shortcut folder contents (explicit).
  • A-4: Startup registration is established on first run and its status is shown in Settings (required_inference).
  • A-5: The shortcut folder must be selected before app names can be added (required_inference).
  • A-6: No multi-user, cloud sync, or cross-device capability is in scope (explicit boundary).
Page 21 of 22

12. Glossary

  • Linked app: an app the user has added to the menu, stored as an app shortcut in the selected folder.
  • Shortcut folder: the drive and folder the user selects where app shortcuts are saved.
  • Taskbar icon: the single Linked Apps icon on the Windows taskbar that opens the menu.
  • Menu: the pop-up panel opened by the taskbar icon listing user-specified app names.
  • Menu Apps: the surface for adding and removing app names in the menu.
  • Settings: the surface for choosing the shortcut folder and customizing the taskbar icon.
  • Landing: the public entry surface introducing the utility and leading into the menu.
  • Windows icon options: the Windows-provided icon selection dialog used to customize the taskbar icon.
Page 22 of 22

No completed page designs yet.

Completed design pages will appear here when they are ready to preview.

Rendering diagram...

No completed page designs yet.

Completed design pages will appear here when they are ready to preview.

Rendering diagram...