Project Vision and Objectives
Making the transition to an ergonomic keyboard easier
Our objective is to develop default keymaps for the MoErgo Glove80 and Go60, supporting both macOS and Windows. The primary goal is to make the transition from a conventional laptop keyboard as intuitive and frictionless as possible, allowing new users to preserve familiar typing habits, shortcuts and workflows while adapting with minimal relearning.
Ergonomic improvements and productivity enhancements should build on that familiarity, not come at the expense of it. For developers, engineers and other technical users, we also aim to provide a thoughtfully designed symbol layer that makes common programming symbols easy to access, comfortable to use and easy to remember.
Project Ignition is not about creating the most complex, customized, ergonomic or technically advanced layout. It is about creating the best default layout for the transition: familiar from day one, easy to learn, comfortable to use and productive without unnecessary relearning.
Project Ignition aims to make the transition from a conventional laptop keyboard to an ergonomic split keyboard as natural and frictionless as possible.
Our primary reference points are the built-in keyboards of Apple MacBooks and Windows laptops. The objective is to preserve the familiar typing habits, muscle memory, shortcuts and everyday workflows that users have already developed, while making thoughtful use of the additional capabilities offered by the MoErgo Glove80 and Go60.
This does not mean reproducing a conventional laptop keyboard key for key. The new keyboards offer different physical layouts, thumb clusters and opportunities for additional functionality. We should take advantage of these capabilities where they improve the experience, without introducing unnecessary relearning or complexity.
Design decisions must follow the priority hierarchy below. Higher priorities take precedence when objectives conflict.
1.1 Familiarity & Muscle Memory — Highest Priority
Preserve familiar keyboard interactions and established user habits while adapting them intelligently to the new hardware.
Prioritise:
Familiar typing behaviour and conventional letter and number assignments (possibly with minor user adjustments to thumb positions).
Familiar modifier combinations and shortcut hand movements.
Convenient and intuitive access to frequently used functions such as Tab, Enter, Space, Backspace and arrow keys.
Preservation of familiar macOS and Windows keyboard shortcuts.
Thoughtful use of the thumb cluster for frequently used functions, particularly Space, Enter and Backspace.
Familiar and predictable behaviour, even when functions move to different physical positions.
New assignments that are intuitive and easy to incorporate into existing muscle memory.
Familiarity does not require preserving the exact physical position of every key. Moving frequently used functions to the thumb cluster can be a sensible improvement, provided the resulting interactions remain intuitive and comfortable.
The objective is to preserve familiar actions, combinations and workflows rather than replicate the physical arrangement of a conventional laptop keyboard.
1.2 Learnability & Ease of Transition
Make the layouts intuitive for people moving directly from a conventional laptop keyboard, including users with no previous experience of split ergonomic or programmable keyboards.
Prioritise:
A familiar and immediately usable base typing experience.
Minimal disruption to everyday typing, navigation and shortcuts.
A small number of clearly organised and purposeful layers.
Intuitive, memorable assignments and predictable interactions.
Easy access to essential functions.
A gradual introduction of the thumb cluster and additional keyboard capabilities.
Minimal dependence on documentation or memorisation.
Layers and dual-function keys can be valuable tools for making better use of the available hardware. However, they should be introduced only when their functionality is easy to understand and their benefits justify the additional learning.
Use as few layers as reasonably practical, without sacrificing useful functionality or intuitive access to essential functions. Each layer must have a clear purpose and provide meaningful value.
Dual-function keys, such as hold-tap assignments, should follow the same principle. Use them only when they provide a clear benefit that justifies the additional learning and potential for accidental activation. Avoid assigning too many functions to individual keys or introducing behaviours that are difficult to understand, remember or use reliably.
The objective is not to eliminate layers or dual-function keys, but to avoid unnecessary complexity and ensure that every additional behaviour improves the overall experience.
hold-tap, tap-dance and mod-morph behaviors are alowed if they add value, specially on smaller boards, combining shift with double tap, tap-dance for capslock could be considered as a viable option.
Take advantage of the ergonomic characteristics of the Glove80 and Go60 to improve comfort and reduce unnecessary finger and hand movement.
Prioritise:
Comfortable and accessible thumb assignments.
Natural finger movements and reduced unnecessary stretching.
Appropriate placement of frequently used functions.
Reliable activation of keys and dual-function assignments.
Reduced awkward combinations and unnecessary hand movement.
Appropriate use of each keyboard's physical geometry.
Ergonomic improvements should complement familiar interactions and support the transition. Avoid changes that introduce significant learning costs for only marginal ergonomic gains.
1.4 Everyday Productivity
Maintain the productivity users expect from their conventional laptop keyboards while taking advantage of the additional capabilities of the new hardware.
Prioritise:
Efficient navigation and text editing.
Convenient application and window switching.
Familiar operating system shortcuts.
Accessible function keys and system controls.
Practical access to secondary functions.
Efficient use of layers and thumb keys where they improve everyday workflows.
Users should be able to remain productive throughout the transition, without having to relearn their everyday keyboard interactions.
1.5 Developer Productivity
Provide an effective and thoughtfully designed symbol layer for developers, engineers and other technical users.
Prioritise:
Convenient access to frequently used programming symbols.
Logical grouping and memorable symbol assignments.
Comfortable access to brackets, operators and punctuation.
Efficient access to common programming combinations and sequences.
Reduced awkward finger movements and unnecessary Shift combinations.
Practical optimisation for real-world programming workflows.
Unlike the base typing layer, the symbol layer does not need to reproduce conventional laptop symbol positions. It can be independently optimised for the Glove80 and Go60 based on symbol frequency, ergonomics, learnability and practical efficiency.
Remove the remaining repetitionClarify layer and dual-function limits
2. Thumb Cluster Strategy
The thumb cluster is one of the most important features of the Glove80 and Go60, and a key part of the transition from a conventional laptop keyboard but it's also very personal. Some use space with their left thumb and other on their right thumb.
Its layout and accessibility should play a central role in determining key assignments, particularly for frequently used functions such as Space, Enter and Backspace, as well as modifier and dual-function keys.
Because conventional laptop users may have little experience using their thumbs for these functions, assignments should be introduced thoughtfully. Prioritise comfortable, accessible positions and predictable interactions that are easy to learn and use reliably.
Ergonomic observations
Our initial observations suggest the following differences in thumb accessibility. These should be treated as general design assumptions rather than universal rules, as reach and comfort vary with hand size and individual anatomy.
Glove80
T4 and T5 are generally the most comfortable and accessible thumb positions.
T6 is reachable but requires additional thumb extension.
T3 is not reachable for most users
T1, T2 are generally less comfortable to reach than T4 and T5 for most users.
Go60
Design implications
Prioritise the most comfortable thumb positions for frequently used functions such as Enter, Space and Backspace.
Avoid placing essential everyday functions in positions that require excessive thumb extension.
Prioritise comfortable positions for dual-function keys, particularly hold-tap assignments:
Glove80: T4 and T5.
Go60: T1 and T2.
Consider usage frequency, thumb comfort, finger independence and activation reliability when assigning functions.
Avoid excessive use of dual-function keys, particularly where timing sensitivity or accidental activations could disrupt normal typing.
Prefer predictable and consistent behaviour that minimises unnecessary thumb movement and makes assignments easy to learn.
Validate the proposed assignments against different hand sizes and real-world use wherever possible.
An important design principle is to preserve familiar keyboard shortcuts and the hand movements associated with them. Rather than simply replicating conventional key positions, we should aim to maintain familiar shortcut combinations wherever possible. This allows users to retain established muscle memory while benefiting from the ergonomic advantages of a split keyboard. For example, keeping Tab in its conventional position while assigning Alt as a hold (hold-tap) function to a thumb key could preserve the familiar left-hand movement for Alt+Tab (application switching).
We should evaluate the impact of our keymap designs on frequently used operating system shortcuts, including:
Windows
Alt+Tab – Switch between applications.
Win+D – Show the desktop.
Win+Tab – Open Task View.
Ctrl+C, Ctrl+V, Ctrl+X and Ctrl+Z – Common editing operations.
Win+Shift+S – Capture a screen snip.
Windows does need AltGr for special characters
macOS
Cmd+Tab – Switch between applications.
Cmd+C, Cmd+V, Cmd+X and Cmd+Z – Common editing operations.
Cmd+Space – Open Spotlight.
Ctrl+Left/Right – Switch between desktops or spaces.
Cmd+Shift+4 – Capture a selected screen area.
Globe/Fn should be included
Design objective
Try to preserve familiar shortcut combinations and minimise changes to established hand movements wherever possible. Users should be able to transfer their existing muscle memory to the new keymap with minimal relearning, making the transition feel natural rather than disruptive.
Arrow Key Accessibility
Arrow keys are essential for everyday navigation, text editing and cursor movement.Where practical, they should remain directly accessible from the base layer. If this is not practical, they should be placed on an easily accessible and intuitive layer.Where possible, preserve the familiar inverted-T or diamond arrangement so users can transfer their existing arrow-key muscle memory.Avoid arrangements that require awkward combinations, excessive thumb movement or unnecessary effort to access frequently used navigation functions.
3. Symbol Layer: A Key Differentiator
The symbol layer should be one of the most important productivity features of our layouts for technical users.
Unlike the base layer, it does not need to replicate conventional keyboard arrangements. It should be designed specifically around the needs of developers and technical users.
The objective is to provide fast, comfortable and memorable access to frequently used programming symbols.
The design should consider the following groups:
Brackets and delimiters
Parentheses: ( )
Square brackets: [ ]
Curly braces: { }
Operators
Programming symbols
Underscore: _
Backslash:
Pipe: |
Ampersand: &
Caret: ^
At: @
Hash: #
Dollar: $
Punctuation and quotation
Symbol layer design principles
The following principles should guide the research and design:
Prioritise symbol frequency in real programming workflows.
Minimise finger travel and awkward finger combinations.
Place frequently used brackets close to the home row.
Arrange related symbols logically.
Optimise common symbol pairs and sequences.
Make underscore particularly accessible for snake_case.
Avoid unnecessary Shift combinations.
Keep numbers on the conventional number row.
Consider finger strength and hand balance.
Make the arrangement easy to learn and remember.
Common programming sequences
The design should be evaluated against frequently used combinations, including:
();
{}
[]
=>
->
!=
==
&&
||
+=
-=
:=
::
The objective is to facilitate comfortable rolling movements and minimise awkward transitions between keys.
The current symbol layer is a starting point. Its optimal arrangement should be established through research and validation rather than assumed.
4. Progressive Complexity
The layouts should support different levels of user experience without overwhelming beginners.
Level 1 – Immediately Familiar
Conventional base layer.
Familiar modifier positions.
Tab, Enter, Space and Backspace.
Standard operating system shortcuts.
Level 2 – Everyday Productivity
Level 3 – Developer Productivity
5. Research Sources and Methodology
The initial research has drawn on the following sources:
Apple for MacOS and macbook air and Microsoft for Windows and typical Windows laptop layouts.
Pascal Getreuer – Ergonomic keyboard layouts and symbol-layer design.
Sunaku – Glove80 layouts and ergonomic layer design.
ShelZuuz – Alternative symbol arrangements.
QMK community keymaps – Programmable keyboard conventions.
ZMK community keymaps – Layer and hold-tap implementation patterns.
MoErgo documentation and firmware – Hardware capabilities, keycodes and layer behaviour.
We should evaluate the final layouts against the following outcomes:
Measure
Desired outcome
Time to become productive
As short as possible