The SpellCheckerSession interface provides the per client functionality of SpellCheckerService.

Applications

• Properly set the NoType:android/R$attr;Href=../../../../reference/android/R.attr.html#inputType in your editable text views, so that the spell checker will have enough context to help the user in editing text in them.

Security

• Only the system is allowed to directly access a spell checker framework's Android.Service.Textservice.SpellCheckerService interface, via the NoType:android/Manifest$permission;Href=../../../../reference/android/Manifest.permission.html#BIND_TEXT_SERVICE permission. This is enforced in the system by not binding to a spell checker service that does not require this permission.
• The user must explicitly enable a new spell checker in settings before they can be enabled, to confirm with the system that they know about it and want to make it available for use.

In most cases, applications that are using the standard Android.Widget.TextView or its subclasses will have little they need to do to work well with spell checker services. The main things you need to be aware of are:

For the rare people amongst us writing client applications that use the spell checker service directly, you will need to use SpellCheckerSession.GetSuggestions(TextInfo, System.Int32) or SpellCheckerSession.GetSuggestions(TextInfo[], System.Int32, System.Int32) for obtaining results from the spell checker service by yourself.

There are a lot of security issues associated with spell checkers, since they could monitor all the text being sent to them through, for instance, Android.Widget.TextView. The Android spell checker framework also allows arbitrary third party spell checkers, so care must be taken to restrict their selection and interactions.

Here are some key points about the security architecture behind the spell checker framework:

[Android Documentation]