arabickbd

The thesis

The keyboard we use was not designed for Arabic. QWERTY was born for the English typewriter, and the Arabic 101 layout was added afterwards. The result is that our fingers learn a foreign arrangement and are then asked to produce another language.

arabickbd is an experiment in building a keyboard that starts from Arabic: from letter frequency, from the shape of words, and from the constant need to switch between Arabic and code.

What we are exploring

• Letter order: an arrangement based on Arabic letter frequency and hand alternation, not on the legacy of the typewriter.
• Arabic-specific keys: hamza forms, tatweel, shadda, and tanween in positions reachable without leaving the home row.
• Arabic and code together: a symbols layer close to a programmer’s fingers, not buried behind arrow keys.
• Physical form: 60%, split, or ortholinear — and what each does to an Arabic typing session.
• Firmware: multiple layers, editable layouts, and configuration stored on the device itself.

Constraints

• Muscle memory: millions of people type on layout 101. Any alternative has to offer a possible transition, not a clean break.
• Standards: some software assumes fixed keys and positions.
• Manufacturing: every physical change adds cost and complexity.
• Evidence: a layout being elegant is not enough; it has to be faster or less tiring in a real test.

Where it stands

Work in progress. We are in the layout-study and early-prototype stage. The interface below is not the final product; it is a tool for comparing the three layers: Arabic, Latin, and code.

Follow along

Design notes and test results will be published in the journal and on this page. If you type in Arabic every day and want to try an early prototype, write to us.