Platform and APIs

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

Platform	Min version	Max version¹	Architectures	APIs
Android²	5.0	14.0	`armeabi-v7a`, `arm64-v8a`³, `x86`, `x86_64`³	Java Android
iOS	15.0	18.0	`x64`³, `arm64`³, `M1`³	Objective-C (Swift-compatible)
Windows UWP⁴	Win 10 build 17763⁵	Win 11 build 22621	`x64`, `arm64`	WinRT
Windows Desktop	Win 10 build 17763	Win 11 build 22621	`x64`³	.NET⁶
Web				JavaScript, WebSocket, REST

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

Should I go native or web?

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 MyScript iink SDK server.

If you are interested in the on-premise version of the MyScript 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. ↩
Supports Math and Raw Content Recognizers. ↩ ↩² ↩³ ↩⁴ ↩⁵ ↩⁶
Comes with a UWP UI reference implementation and examples. ↩
Windows versions ↩
Comes with a WPF UI reference implementation and examples. ↩