New in 2.0

MyScript iink SDK 2.0 comes packed with improvements and several noticeable new features. This page provides an overview of the changes.

MyScript iink SDK 2.0 novelties listed on this page are available with our native APIs only.

If you upgrade from 1.5, please take a look at the migration guide.

Two new tools ready to integrate

MyScript iink SDK v1.x API used to consider that pen events were dedicated to write or edit content (text, math or shape content, edit gestures, etc.) and touch events to manipulate content (select, drag & drop, scroll, etc.). MyScript iink SDK 2.0 introduces two new tools that can be mapped to your inputs:

Lasso selector

The lasso selector tool lets you draw a lasso to select some content: MyScript Interactive Ink analyses the captured strokes to determine the selection surrounded by the lasso, so that you can interact with it. Depending on the context and the content, you can move or scale the selected items, apply some formatting, copy or typeset them, etc.


The highlighter tool allows you to emphasis content by adding transparent color anywhere in a page, regardless of the type of content. In addition, you can enable it as a coloring tool: with a long press you can color shapes or change ink, lines, arcs or text colors.

New ToolController object

The ToolController object was added to MyScript iink SDK to support those new tools. It lets you control what you want to do with your captured inputs by associating input sources with interaction tools, such as pen, eraser, highlighter and selector. For instance, a pen input can now be used to select content with the selector (lasso) tool.

➤ To support the new tools, we had to refactor the editor and break some APIs. We have made some small configuration adjustments too. We also took advantage of this update to remove the deprecated APIs and merge some Java interfaces. So make sure to check the migration guide!

More flexibility with “Raw Content”

Interactive features support in “Raw Content”

With MyScript iink SDK 2.0, we introduce the support of interactive features in “Raw Content” content types. Combined to our new tools, this allows you to write and draw freely on a wide canvas and interact with the content: you can select some content with the hand or lasso tool to apply actions on it, such as copying it or exporting it for further use, converting it, or transforming it.

Note that by default, these features are not activated for the “Raw Content” type, so you should tune your configuration to benefit from them.

➤ For further details on what is supported and how to configure it, refer to the interactive features page.

➤ Applications running on interactive white boards are typical use cases for which you should consider using a “Raw Content” combined with interactive features. Integration advice for interactive white boards are given in this dedicated page.

Adding images in “Raw Content” part

In addition, it is now possible to add images within a “Raw Content” part.

Fresh Demo code examples integrating our new tools

Our GetStarted examples have been kept as simple as possible to offer you an MyScript iink technology first taste.

Our Demo examples, in contrast, have been fully refreshed to integrate the new lasso and highlighter tools. In the Demo, we have also added the use of the MyScript Inter and STIX fonts to illustrate the use of customized fonts.

On Android, the Demo refresh was also the good opportunity to move to Kotlin.

➤ The Demo examples have been designed to make your integration easier and more intuitive, and offer you a reference implementation you can cherry pick from.

Other changes

Update to the latest MyScript technology

MyScript iink SDK 2.0 is based on the latest version of MyScript’s core recognition SDK, resulting in recognition performance and accuracy improvements. In math, it brings the support of the “mod” symbol and progress in the recognition of fractions.

While recognition assets provided with MyScript iink SDK 1.5 will stay compatible, you may want to update your users to the latest assets if you migrate them to 2.0.

Import using a specific configuration

An import function has been introduced in 2.0 that lets you temporarily “override” the current editor configuration for the need of a specific import. For instance, in the case of “Diagram” and “Raw Content” parts, it might be convenient to momentarily modify the current editor configuration for the need of changing the text candidates, without impacting your global or your editor configurations. For more details check the Import and export page.

Formatting text

A new method has been added to the editor that lets you programmatically format the text blocks that are contained in the selection of a “Text Document” like you would do with an underline decoration gesture.

Retrieving your Content Part language

We have added a new getLanguage method on ContentPart that lets you know which language is configured on a Content Part.

Deprecation of 32-bit architectures

32-bit platforms are being progressively replaced by 64-bit ones. iOS already requires applications to be 64-bit only, with Android enforcing the provision of a 64-bit version of any app since August 2019. Following this accelerating trend, MyScript iink SDK 32-bit binaries were deprecated and may be removed in a future release.

Deprecation of bitcode build on iOS

As starting with Xcode 14, Xcode no longer builds bitcode by default, building with bitcode is deprecated. So, the ability to build with bitcode will be removed in a future release.

We use cookies to ensure that we give you the best experience on our website Read the privacy policy