kando-menu/kando

🌸 Do things with utmost efficiency.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 38 minutes ago
Added to GitGenius on September 10th, 2026
Created on April 16th, 2023
Open Issues & Pull Requests: 68 (+0)
GitHub issues: Enabled
Number of forks: 210
Total Stargazers: 6,328 (+1)
Total Subscribers: 30 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Issue API getrepoissuespagesummary failed: 429 Rate limit exceeded. Please try again later.

Detailed Description

Kando is a cross-platform marking menu application that provides gesture-based command execution through an Electron-based interface.

The tool solves the problem of inefficient command access by implementing marking menus, a gesture-driven UI paradigm where users draw strokes to invoke actions. Rather than navigating nested menus or memorizing keyboard shortcuts, users can draw simple patterns on screen to trigger commands. The application runs on Linux, macOS, and Windows, making gesture-based workflows accessible across platforms. It allows customization of menu structures and bindings so users can tailor the gesture vocabulary to their own workflows.

Kando suits users who value speed and muscle memory in repetitive tasks and those working across multiple applications where consistent gesture commands reduce context switching. It works best for power users comfortable learning gesture patterns and those seeking an alternative to traditional menu navigation or hotkey systems. The project positions itself as a marking menu implementation rather than comparing itself to other gesture or menu systems in the README.

The project shows active development with regular commits addressing features and fixes. The codebase demonstrates attention to cross-platform compatibility, with platform-specific considerations reflected in the implementation. Development activity includes ongoing refinement of the gesture recognition and menu rendering systems. The project maintains a public homepage separate from the repository, indicating sustained effort toward user-facing documentation and presentation. TypeScript is used throughout, suggesting a focus on type safety in the application logic.