What do you guys make of this new wearable keyboard: http://www.tapwithus.com/
Allegedly they are going to be opening an sdk which will enable any developer to turn it into a super controller..

CimmerianX commented: Created an account to advertise this P.O.S. -2
rproffitt commented: Your only post so far? -2

Dani AI

Generated

Short update and a quick developer guide for (and a follow-up to ’s UX point).

The device marketed as Tap / Tap Strap matured from the 2016 demos into a shipping product with official developer tools. There’s an active Android SDK (and Unity/iOS tools) so you can get raw tap/gesture data instead of only treating the unit as a plain Bluetooth keyboard. (github.com)

How that matters to developers: the Tap boots in a Text Mode (it shows up like a HID keyboard) but the SDK can switch it into Controller Mode and stream an integer bitmask (1–31) representing which fingers tapped. That lets an app treat taps as button presses (games, VR, custom controllers) instead of characters. (github.com)

On Android there are two realistic integration paths. For app-specific controls use the Tap SDK callbacks inside your app (recommended for games/VR). For system‑wide text mapping build an IME (InputMethodService) and feed Tap events into the input connection (or let the device remain in HID Text Mode). Also remember modern BLE permissions: on Android 12+ you must request BLUETOOTH_SCAN / BLUETOOTH_CONNECT / BLUETOOTH_ADVERTISE (and handle runtime prompts); test across API levels. The SDK also helps by switching modes when your app backgrounds. (developer.android.com)

Practical tips and gotchas: expect a nontrivial learning curve and some finger-combo reliability issues (reviews mention this and the need to test real users/surfaces); later hardware revisions added AirMouse/gesture improvements and better battery life. If building fast prototypes, use the vendor’s examples/Unity plugin, test both HID and Controller flows, and decide early whether you need system-level injection (hard) or in-app control (much simpler). (macrumors.com)

Small IME sketch (illustrative):

@Override
public void onTapInputReceived(String id, int data, int repeat) {
    String ch = mapTapToChar(data); // map bitmask -> char or command
    getCurrentInputConnection().commitText(ch, 1);
}

Summary: the SDK exists and is usable; choose HID for simple global typing or SDK+IME for richer, app-controlled interactions. (github.com)

The goggles look totally dorky! The concept is good. If it had a display something like Google Glass it wouldn't be so bad.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.