Getting started — load your keymap and start practicing

Step 1: Prepare your keymap file

Grab your current config from your firmware repository (zmk-config / qmk_firmware):

• ZMK: config/<board>.keymap
• QMK: keyboards/<board>/keymaps/<you>/keymap.json

See supported keyboards and formats for details.

Step 2: Upload the keymap

Click the “Load keymap” button on the home page and pick the file. Layers and key tables appear once parsing succeeds. The file is stored in your browser's LocalStorage and never sent to a server.

Step 3: Choose a physical layout

daken renders your keymap on the actual split layout when one is selected.

• JSON upload: load a ZMK / QMK layout JSON for any board.

Without a layout JSON, daken shows the base layer on a standard keyboard.

Step 4: Pick a practice mode

• Speed drill: timed Japanese romaji / English / code drills. Romaji accepts both Hepburn and Kunrei forms (chi, ti, etc.).
• Layer switch drill: prompts like “hit % on Layer 2” — perfect for training mo keys and home-row mods.

Step 5: Review your results

At the end of the session you see answer count, total WPM, average accuracy, and the top 5 most-missed keys so you can focus on weak spots.

Tips for a faster keymap migration

The first week or two after switching keymaps is the hardest part. Based on the operator's own migration to a split keyboard, here is what actually helps:

• Stabilize the base layer first: don't try to learn every layer at once. Run timed drills until letters come out without thinking — layer practice is pointless while basic typing still stumbles
• Drill layers daily, briefly: the goal is fingers that move on their own, not recall. Five minutes every day beats an hour on the weekend
• Start from your top-5 missed keys: a key that stays weak after practice is often a keymap problem — it may simply be in a hard-to-reach spot worth remapping
• Keep your usual romaji habits: daken accepts both Hepburn and Kunrei spellings, so the only thing you need to learn is the keymap itself

FAQ

Q. My keymap file fails to load

daken supports two formats: ZMK .keymap (DTS) and QMK keymap.json. QMK keymap.c is not supported — export keymap.json from QMK Configurator or convert with qmk c2json. Load the file as-is, without editing; files straight from your zmk-config repo or a Configurator export work best.

Q. Is my keymap sent to a server?

No. Parsing and storage happen entirely in your browser, and data lives only in LocalStorage. On a shared computer, you can wipe it via your browser's site-data settings.

Q. Are Kunrei-style spellings (ti / si / tu) marked wrong?

No. Both Hepburn (chi / shi / tsu) and Kunrei spellings count as correct, along with doubled consonants or ltu / xtu for っ, n / nn for ん, and loanword spellings like fa / va. If a mainstream IME accepts it, daken accepts it — practice with whatever you type day to day.

Q. The layer view doesn't follow my key presses

Layer tabs and live key highlighting activate once a physical layout (layout JSON) is loaded — check that first. Also note that mo / lt switch the displayed layer only while held. If it still doesn't follow, the binding order in your keymap may not match the physical key order.

Q. Does daken work in Firefox or Safari?

Yes. daken relies only on the standard KeyboardEvent API — no special APIs or extensions — so current versions of Chrome, Edge, Firefox, and Safari all work.

Q. Are my results saved?

Results are shown for the current session only and disappear when you close the browser. Persistent practice history is planned. For now, jot down the WPM and accuracy from the session summary if you want to track progress.

Q. Can I practice on a phone or tablet?

daken is designed for typing on a physical keyboard, so a PC is recommended. A tablet with an external keyboard works, but the layout is optimized for desktop screens.