The following table lists the platforms and architectures that are qualified for the MyScript iink SDK 4.1 release:
Platform | Min version | Max version1 | Architectures | APIs |
---|---|---|---|---|
Android2 | 5.0 | 15.0 |
armeabi-v7a 3, arm64-v8a 4, x86 , x86_64 4
|
Java Android |
iOS | 15.0 | 18.2 |
x64 4, arm64 4, M1 4
|
Objective-C (Swift-compatible) |
Windows UWP5 | Win 10 build 177636 | Win 11 build 26100 |
x64 , arm64
|
WinRT |
Windows Desktop | Win 10 build 17763 | Win 11 build 26100 |
x64 4
|
.NET7 |
Web | JavaScript, WebSocket, REST |
The answer depends on your requirements.
You should probably use the native version if:
You should probably use the web version if:
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. ↩
Requires Neon support. ↩
Supports Math and Raw Content Recognizers, and latest math and Raw Content analyzer bundles for Editor and OffScreenEditor. ↩ ↩2 ↩3 ↩4 ↩5 ↩6
Support for UWP / WinUI 2 in iink SDK is deprecated and may be removed in a future release. ↩
Comes with a WPF UI reference implementation and examples. ↩