Supported platforms

Platform and APIs

The following table lists the platforms and architectures that are qualified for the iink SDK 1.3 release:

Platform	Min version	Max version¹	Architectures	APIs
Android²	5.0	9.0	`armeabi-v7a`, `arm64-v8a`, `x86`, `x86_64`	Java Android
iOS	9.0	12.0	`armv7`, `arm64`	Objective-C (Swift-compatible)
Windows UWP³	Build 10240⁴	Build 17763⁴	`x86`, `x64`	WinRT
Windows Desktop³	Windows 7⁵	Build 17763⁴	`x86`, `x64`	.NET⁶
Web				Web component, JavaScript, WebSocket, REST

If your requirements extend to other platforms, please contact our sales team.

The answer depends on your requirements.

You should probably use the native version if:

You cannot allow or ensure your users the access to an Internet connection.
You need to provide end users with content types that are not yet supported in the web, such as diagram or text document.
You want to have a fine control over the types of devices you consider or want to make use of specific hardware features linked to the stylus.
You want to avoid sending data to a remote server.

You should probably use the web version if:

You are developing a web or an hybrid application.
You prefer off-loading the recognition overhead to a remote server to spare resources on the local device.
You have data confidentiality constraints but you are ready to host the iink SDK server.

If you are interested in the on-premise version of the iink SDK server, please contact our sales team for more information and pricing.

Last qualified version for the current release. Theoretically, newer versions of the platforms should be compatible. ↩
Can be embedded into Android applications running on Chrome OS as well ↩
Visual Studio 2015 and 2017 ↩ ↩²
Windows 10 versions ↩ ↩² ↩³
Development shall be done on a Windows 10 machine ↩
Comes with a WPF UI reference implementation ↩