Our product suite consists of two components: the DRIFTTM circuit, and the API that enables your tablet to read and write from DRIFTTM.

Duplex Response Interface for TouchscreensTM
bitrate (touch)
40 bits/s/channel
bitrate (VLC)
40 bits/s/channel
Nintendo Switch
operating voltage
1.65v to 3.6v
standyby battery life
10 years
operating battery life
600,000 transactions
2 Kb
latency (nominal)
8 ms
production lead time
3 months
+/- 2 mm


nameDuplex Response Interface for TouchscreensTM
bitrate (touch)40 bits/s/channel
bitrate (VLC)40 bits/s/channel
compatibilityNintendo Switch
operating voltage1.65v to 3.6v
standyby battery life10 years
operating battery life600,000 transactions
EEPROM size2 Kb
latency (nominal)8 ms
production lead time3 months
precision+/- 2 mm


What are the differences between your KCardTM/KTagTM and DRIFTTM product lines?

KCardsTM and KTagsTM are statically encoded identification tags each containing an internally stored serial number, which users can use to create fascinating gaming and identification-based business applications.

DRIFTTM is an all-purpose communication transceiver that users can use to transmit and receive any arbitrary message from a touchscreen device. Think of the DRIFTTM like an antenna that can enable your consumer electronic device to talk to a smart device simply by touching the touchscreen and interacting with the on-screen contents. It is currently designed more for businesses, developers and hobbyists to create their own application projects.

Are smartphones supported?
What platforms is DRIFTTM supported on?
We have SDKs for the Nintendo Switch, iOS, Android, Windows, and Unity, which means that most platforms are supported. There is also a hardware quality consideration. Please see compatible devices for reference.
How do I get started trying out DRIFTTM?
We have a complete SDK for developers and hobbyists to develop creative projects. Contact us here to request for a set.
Why doesn’t DRIFTTM work on my tablet?
Certain tablets and smartphone models come with a palm rejection “feature” that interprets certain touch signal pattern as “palms” and would refuse to react to protect the device from accidentally activated by a palm landing on the screen, even when this feature is “turned off” from the settings menu. We are working on a solution (for our App-based solution) to get around this problem. There is currently no known solution to address this issue to use our Web-based solution yet.
Why does my DRIFTTM not work with my tablet with a screen protector?
Certain screen protectors, especially with thick ones, may block signals transmitted from DRIFTTM onto the screen. An analogy would be you wearing gloves and trying to use the tablet — most of the times this wouldn’t work. Hence we do not recommend using DRIFTTM on tablets on screen protectors.
Does DRIFTTM need batteries or need to be recharged?
DRIFTTM is battery-powered to bring to the world the first-ever seen communication capability directly with a touchscreen. It is designed to be long lasting with an estimated shelf life of 5 years and can clock more than 600,000 communication transactions. In other words, there is very little need for battery replacement.
Will DRIFTTM still work if the user updates to newer Android / iOS / Windows versions?
Our DRIFTTM SDK was written using the most fundamental function calls in these operating systems. We are confident that they will work with newer OS versions.
Can you make DRIFTTM smaller?
Yes. In fact, we are currently working with our enterprise customers closely to produce customized shapes and sizes for our DRIFTTM product. Contact us here and let us know your needs.