At the moment, our flagship KCard solution can support up to 1000 unique IDs, calibrated using Apple iPads as the benchmark. Note that this number can vary depending on the build quality of your touchscreen device. Because of the sheer number of Android device brands, please check with us if you expect to deploy on a variety of target devices.
Please see our Compatiable Devices section.
KCards are not supported on iPhones, however we have a supported product for them; the KTag, which is a smaller version of the KCard and supports up to 30 different unique IDs
See our KCard vs KTag section
We have SDK for iOS, Android, Windows and Unity, which means most platforms are supported. There is also a hardware quality consideration. Please see compatible devices for reference.
As with any OEM hardware solution, the higher the quantity ordered, the lower the price it will be. For a typical card gaming project where 10,000+ cards are needed, the cost per card (before printing) will be no more than US$1. Contact us for a more accurate quote.
Yes, but we strongly advise that you consult us before going for this option as we have experience in the exact printing method that works best on our card materials.
Our manufacturing process is currently set at thickness of 0.70mm. If there’s a specific project that requires a different thickness, please contact us.
Our KCard SDKs were written using the most fundamental function calls in these Operating Systems. We are fully confident that they will work with any newer OS versions.
Certain Samsung 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, however.
The short answer: unlimited. Think of the KCard is a unique ID. Once the app on your touchscreen device identifies it, it retrieves information from either within the App or via our Cloud Server. In other words, the KCard can be used to retrieve video, audio, graphics, text etc. Also, such a solution is secure — losing a card does not lead to information leakage, for one just needs to void the record on the cloud server for the lost KCard ID, and then no one else would be able to retrieve any information
Nope. KCards do not need power to operate.
Certain screen protectors, especially with thick ones, may block signals transmitted from KCard 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 recommend not using KCards on tablets on screen protectors.
Our Web-based solution first registers signals recorded in your tablet browser, and sends this information back to our API server for interpretation, after which the results are sent back to your tablet. As you can see, this process could be affected by the Internet latency between your tablet location and our server. We recommend developing an App-based solution for situations where response time is of high importance.
We have solutions to get around this issue but this may mean restricting the touchscreen devices to a certain small number of brands and models. Hint: Stay tuned and subscribe to our newsletter to get informed of our development.
Send us a request for an Evaluation Kit here.