Keyboard Builder
Every student has a keyboard under their hands, and almost none of them know what happens when they press a key. Keyboard Builder starts where the hobby videos start: pick a size, switches and keycaps, and type on it. Then it turns the board over. The keys sit in a grid of rows and columns that a small controller scans. Hold three keys and a fourth can light up that nobody pressed. A keyboard never sends a letter. Students find all of that by doing it.
Using this with a class? Make a free class and add your students yourself: each gets a username and password, with no email or Google account needed. Or give them one join code. Using Google Classroom? Post the link there; with a free class, the link also puts each student in your class, so you see their work. mytekDev is also available from the Google Workspace Marketplace, so your school's Google admin can install it for everyone.A first lesson: One period on the Matrix bench: count the pins, hold Q, W and A, catch the ghost key, and fix it two ways. A second period on the Keymap bench: put the arrow keys on a board that has none, and make one key type a whole line. A third for the Switch bench, two repairs and the build sheet.
Set up a free class Share to Google ClassroomWhat a student actually does
There is one keyboard and five benches, and whatever is chosen on one bench is the board on all of them. On the Build bench the student picks the size (60, 65 or 75 percent, tenkeyless or full size), the case, the plate, the mount, one of six switches, the keycaps and their colors. A price adds up as they go, and an exploded view lifts the board into its five layers. Each part says what is known about it in plain text, and what builders only say about it in a separate line that starts "Builders say".
On the Switch bench one switch is cut in half beside a graph of how hard it pushes back. The student presses it slowly and a dot rides the graph: up a hill on a tactile switch, with the click on a clicky one coming before the key is sent. On the Matrix bench the board is turned into its circuit: rows, columns, a switch at every crossing, and a scan pulse stepping across the columns. Clicking Q, W and A so they stay down lights S, in pink, with the path the current took. Diodes fix it. So does telling the controller to ignore a key it cannot be sure of, and then a real key goes missing. A panel counts how many keys the student's own keyboard is reporting, which is how they find the chords it drops.
On the Keymap bench the student decides what every key sends, on two layers, with four macros and three letter layouts. On the Type bench they type on the board with the keyboard under their hands. The key in the same place dips and sounds, and a line says the row and column, the code the board sent, and the character the computer made of it. Their keymap really runs: with Fn held on the board, a letter they turned into an arrow sends the arrow. A sound tuner sets the pitch, the ring and the click to taste, and a timed line gives words a minute, which is never saved.
Twelve orders are the puzzles. Four are builds on a budget, such as a board with a number pad and a switch you can feel without a click, for $125. Two are about ghost keys. Three are keymaps. Three are repairs: a dead switch, a column of keys that died together, and a borrowed board whose 7 sends 8. A wrong repair is counted, and the customer says why it was wrong. A build sheet shows the keyboard with ten written questions. Setup lets a teacher choose the questions, add their own, open an answer key, keep the key sounds off for the class, and leave out the timed line.
A 60 percent board has no arrow keys. This student put them on I, J, K and L on layer 1, which is on while Fn is held. The faded keys are see-through: on layer 1 they do whatever layer 0 says. On the Type bench, holding Fn and pressing I now sends the code for Up.
The tactile switch, pressed 1.3 mm. The hill on the graph is the bump a finger feels, and it comes before the key is sent at 2 mm. The key is never sent at the bottom. The dots are the numbers listed for the switch; the line between them is drawn to match one measured switch of each kind.
What they are learning while they work
Nothing here is presented as a lesson. This is what the activity is made of.
| What the student does | What it is |
|---|---|
| Switches the wiring to one wire per key and reads 61 pins against 19 | Why hardware is built the way it is. A controller has a limited number of pins. A grid of 5 rows and 14 columns reaches 61 keys with 19 of them. The design is a trade, and the trade has a cost the student is about to find. |
| Holds Q, W and A and watches S light up | Ghosting. With three corners of a rectangle closed, current can go the long way around through all three switches and reach the fourth corner. The controller reads a key nobody pressed. |
| Turns the diodes on, then tries the cheaper fix and loses a real key | Two fixes, two costs. A diode beside every switch lets current go one way only, at the cost of one more part for each key. Ignoring a doubtful key costs nothing to build and drops a real press. "Anti-ghosting" on a box can mean either. |
| Presses a key on the Type bench and reads: row 2, column 9, code 0C, your computer turned that into i | Layers of abstraction. The switch closes, the scan finds the row and column, the keymap picks a code, the code goes to the computer, and the computer's keyboard layout setting turns it into a character. Each layer hides the one under it. |
| Holds Shift and A and sees the same code with one modifier bit turned on | Encoding. A keyboard never sends a letter. Shift is one of eight on and off bits sent beside the key's number, and the capital is made by the computer. |
| Puts the arrows on I, J, K and L on layer 1, holds Fn and presses I | Firmware and layers. A keymap is a table the keyboard's own controller runs. The controller looks at the highest layer that is on and works down, and Fn is never sent to the computer at all. |
| Finds that four dead keys share one column line and repairs the line, not four switches | Troubleshooting. A fault that takes out several things at once is usually in something they share. Finding what the dead parts have in common comes before replacing anything. |
| Presses a tactile switch slowly and watches the dot go over a hill before the key is sent | Reading a graph of a real part. The graph is force against distance. The bump, the point where the key is sent and the bottom are three different places on it. |
How to tell whether it landed
Ask, and let them show you. A student who has understood it can answer these without help.
- A 60 percent board has 61 keys. How many pins does it need with rows and columns, and how many with one wire for every key?
- You held three keys and the board saw four. What do those four keys have in common?
- Name two ways a keyboard can stop ghost keys. What does each one cost?
- You hold Shift and press A. What does the keyboard send, and what turns that into a capital A?
- Does the computer ever find out you pressed Fn?
- Four keys stop working on the same day. What do you find out before you replace anything?
Use it in your subject
Not a technology class? Then the app is how students show what they learned in your unit. More projects for every subject.
Computer science, grades 9 and 10
CSTA 2017 3A-CS-01: explain how abstractions hide the underlying implementation details of computing systems embedded in everyday objects. 3A-CS-02: compare levels of abstraction and interactions between application software, system software and hardware layers. The 2026 CSTA standards ask students to demonstrate the capabilities and limitations of a physical or simulated computing device (HS-SYS-HW-30), and ghosting is a limitation they can cause with three fingers.
Computer science, grades 6 to 8
CSTA 2017 2-CS-03: systematically identify and fix problems with computing devices and their components, through the three repair orders. 2-CS-01, recommending improvements to a device from how people use it, fits the build orders, where each choice is argued for a named customer.
Computer technology and IT courses
CompTIA Tech+ (FC0-U71) 1.4, the troubleshooting methodology, and 2.4, common peripheral devices, which names the keyboard. It sits beside PC Workshop in a hardware unit as the input device.
Technology and engineering
ITEEA Standards for Technological and Engineering Literacy, STEL-2M: differentiate between inputs, processes, outputs and feedback in technological systems.
What this page does not claim
It is not a typing course, so it does not claim a keyboarding standard such as CCSS W.6.6. NGSS MS-PS4-3 is about digitized signals and its boundary leaves out the specific mechanism of any given device, so it is not claimed either.
Practical notes
- AgesGrades 6 to 10. A middle school level uses plain words. A high school level adds the eight-byte report the keyboard sends, the return line on the switch graph, and contact bounce.
- TimeOne period for the Matrix bench and its orders. One for the Keymap bench. One for the Switch bench, the repairs and the build sheet. The build sheet takes fifteen minutes.
- EquipmentA computer or Chromebook with a modern browser and its own keyboard. Nothing to install. Headphones if the class is using the key sounds, which are off until a student turns them on.
- CostFree. The app has no paid tier.
- PrepAbout fifteen minutes: close the order A letter nobody pressed and the order Arrows under my fingers yourself, then open Setup and read the answer key.
- In a groupOpen Setup in the app's header to choose which of the ten questions are on the build sheet, add up to ten of your own, keep the key sounds off for the whole class, and leave out the timed line.
For co-ops, microschools, and classrooms
Set the build sheet up once in Setup and hand the project out as the starter; the setup travels with it. The matrix follows rules, so every student who holds Q, W and A sees the same ghost, and a class can argue from the same result. Then send them to their own keyboards: the Matrix bench counts how many keys the keyboard in front of them is reporting, and which three-key chords it drops differs from one model to the next. That part is a real experiment with no answer key.
Common questions
Is it free?
Yes. Keyboard Builder has no paid tier, and it can be tried right on this page without an account.
Is the matrix real?
It is the textbook circuit: rows, columns, a switch at each crossing, one column scanned at a time. The key codes the app shows are the real ones from the USB standard, and so is the eight-byte report on the high school level. The grid follows the keys' own rows, which makes 19 pins on a 60 percent board. Real boards sometimes fold the grid another way to save pins, and a full-size board has to: laid out plainly it needs 27 pins, one more than a small controller has. The app says so.
Will my students see a ghost key on their own keyboards?
No. A laptop keyboard has no diodes, and it avoids ghosts by dropping a key it cannot be sure of. It never invents one. The ghost key is on the simulated board. What students can find on their own keyboards is which three keys will not register together, and the app counts the keys for them.
Are the switches real?
They are generic switches with real numbers: the force and distance at which the key is sent are from Cherry's pages for five of them and from sellers' listings for the sixth. The line between those numbers on the graph is drawn to match one measured switch of each kind. How long a contact bounces is a made-up typical pattern, and the app says that too.
Are the sounds real?
No. They are made by the app, not recorded. Two things about them are facts: a key makes one sound going down and another coming up, and a clicky switch adds a click before the key is sent. What the case, the plate, the mount, the foam and the cap plastic do to the sound is what builders say, with no published measurements behind it, and the app marks every such line. Sound is off until a student turns it on, and a teacher can keep it off for the class.
Does a mechanical switch make you type faster?
Nobody knows for sure. The few studies are small and do not settle it. In this app the student is still pressing the keys of the keyboard in front of them, so the timed line measures the student, not the switch. The result is never saved or shared, and there is no leaderboard.
Is it a typing course?
No. There is a short line to type and a count of words a minute, and the app does not teach where the fingers go.
Can a student build a real keyboard after this?
They will know what each part is for, what the sizes give up, and why the board needs a diode at every key, which is most of what the buying guides assume. Prices in the app are round numbers typical of 2026, not anyone's price list, and a real build needs its parts checked against each other in ways the app leaves out.
Still have a question? Ask us, and a person will write back.
Where to go next
Lesson plans
4 ready-to-teach class periods with a teacher plan, a student worksheet, an exit ticket with answers, and the standards it meets.
Start with Keyboard Builder
Trying it costs nothing and takes about five minutes. An account is what makes the work last.
Keyboard Builder is one of the making apps on the platform. The board is drawn in code and every result comes from the keyboard as built, so three keys ghost the same way on a fast laptop and a slow Chromebook, and the app's test suite checks every rectangle of four keys on two of the boards. An independent accuracy review checked every key code, datasheet number and answer key against sources before it went live.
Page last reviewed November 2026.
Google, Google Classroom and Chromebook are trademarks of Google LLC.