News and research

Kapybara development

8 May 2025  <- Previous

Kapybara development starts now

Kapybara (finnish spell for Capybara) is the name for Input Labs' second reference design, a single hand controller more focused on accessibility usecases. We had plans to make the Kapybara as early as 2022 when Input Labs was founded, but the development of the Alpakka (our first controller) forced us to delay its development until now.

We are setting a development framework for the Kapybara that will be very different than what we did for the Alpakka. When we developed the Alpakka we had a strong vision for how a gyro-first controller should be, and how it should fit into the classic gamepad layout, therefore when we published the project and started getting feedback, such "late" feedback was mostly about how to nail the final design, but there were no radical re-designs.

On the contrary, with the Kapybara we are going to start gathering ideas from the community when we are still on the drawing board, and we hope to get insights that only players with disabilities could give us. The concept is completely open at the moment, everything about it can be influenced by the feedback from the workgroup.

In the new workgroup, we want testers to have a closer relationship with the developers, and more interaction in the process. This might include 1on1 interviews and video-sharing when using the prototypes (more on the expectations below). For this reason the number of testers will be much more limited (5~10) and more focused on the disability aspect.

The research will focus on solving accessibility issues related with motor disabilities (limb difference, amputation, neuromuscular and musculoskeletal disorders), and will not be trying to solve problems derived from cognitive disorders, such as attention disorders nor intellectual disabilities; although the resulting solution could also be helpful in these cases.

Design goals (not final)

• The controller should be usable with a single hand.
• All games that are playable with an Alpakka should be playable with a Kapybara, without losing any core functionality.
• The Kapybara could complement other devices (see use-cases below).
• The external case should be compatible with as many hand sizes and different grips as possible.
• The Kapybara will use the Marmota module as core, reducing the development complexity (as if it was an Alpakka with different form factor).
• Project structure will be similar to Alpakka, with open 3D-printed models and PCB schematics.
• Firmware and Ctrl app will support both Alpakka and Kapybara.

Open questions (so far)

• Should the controller be symmetric and usable with either hand?, or should we have dedicated left-hand and right-hand versions? Is there any clever solution that have the benefits of an asymmetric case without the tradeoffs?.
• Should the controller have a strap? It would keep the controller in position without requiring the ring and pinky fingers to be used to held the controller. Can we 3d-print straps with rubber materials such as TPU?.
• Should the ring and pinky fingers be used for inputs (buttons)? They are the less dexterous fingers, and some people may have issues pressing buttons with them. Are the other 3 fingers (thumb, index, middle) enough for all the inputs required in complex games?.
• Should the thumb be used for the thumbstick? this is the obvious solution, but the thumb is the most dexterous finger and maybe would be better to use the thumb for ABXY and the index finger for the thumbstick?.
• What about the second thumbstick? should be placed in the back? in the front in a double stick arrangement? or not placed at all?.
• Compared to an Alpakka, a Kapybara could have reduced stability while pressing buttons/triggers, which could lead to increased actuation motion or "gyro shake" (unintended rotation while pressing buttons).
• Given the complex arrangement of buttons, can the PCB be designed with a single board / without requiring submodules nor flex PCBs?.

Use-cases

Kapybara only

Player has restricted motion or pain in one hand. Player has limb difference or amputation. Player is able to play any game with a single hand. Will require higher button density than in most other single-hand controllers. Controller could have a jack 3.5mm connector, so a pedal can be attached for additional inputs.

Kapybara + Mouse

Player has restricted motion or pain in one hand, preventing the usage of keyboard / WASD. Kapybara replaces the keyboard in the KB&M combo. Also for enthusiasts without disabilities, because analog movement and better ergonomics. Unclear purpose of gyro in this configuration.

Keyboard (WASD) + Kapybara

Player has restricted motion or pain in one hand, preventing the usage of a mouse. Kapybara replaces the mouse in the KB&M combo.

Kapybara + Kapybara

Player has restricted motion or pain, preventing usage of a traditional controller (with both hands in proximity). Unclear how communication between devices would work. Combined profiles? Able to join them with a bracket? (contradicts 1st point). This is the most complicated use case, and might need additional research.

Other usages that will NOT be implemented on the reference design

• Kapybara(s) as VR controller(s).
• Kapybara on a joystick base.
• Kapybara as a 3D mouse.
• Kapybara as a MIDI controller.

Grip / Main body shape candidates

TV remote grip

T-shape / pistol grip

Brick with strap

Workgroup roles

Organizer role

• Members: Michael and Marcos. Maybe additional coordinators.
• Expectations:
  • Organize the development / Implement the core solutions.
  • Coordinate and moderate the workgroup communication channels.
  • Facilitate feedback gathering via interviews and/or surveys.

Tester role

• Members: Between 5 and 10 approved testers.
• Prototypes: Provided by Input Labs.
• Requirements / Expectations:
  • Having disabilities relevant to the use-cases.
    • Limb difference.
    • Limb / hand / finger amputation.
    • Neuromuscular disorder (dystrophy, sclerosis, palsy...).
    • Musculoskeletal disorder (arthritis, carpal syndrome, strain injury...).
  • Being able to share details (privately) about their mobility-related disabilities.
  • Being able to make videocall interviews if required.
  • Being able to pay for prototypes shipping costs. (Shipping is around 15 euros per parcel).
  • Having a pro-active attitude, and communicate often in Discord.
  • NOT required: 3D printer nor DIY skills.
  • Apply to become a tester.

Collaborator role

• Members: Everyone is welcome.
• Hardware: Self-sourced according to schematics.
• Requirements / Expectations:
  • Having a 3D printer and basic DIY skills.
  • Follow up with latest mockups and prototypes, build and test them.
  • Share feedback and ideas in Discord.
  • Maintain basic etiquette, avoid heated arguments, and respect the opinions of other testers.
  • No need to sign up.

Development phases

Additional notes

• We won't define a final deadline for the development, it will be ready when is ready.
• It is unclear if Input Labs will sell Kapybara parts in the shop. We will evaluate it in the future.
• Tester channels in Discord will be reworked.

Thanks for the support! 🤍
- Michael and Marcos