google_mlkit_translation 0.6.0

A Flutter plugin to use Google's ML Kit On-Device Translation to dynamically translate text between more than 50 languages.

Google's ML Kit On-Device Translation for Flutter

A Flutter plugin to use Google's ML Kit On-Device Translation to dynamically translate text between more than 50 languages.

PLEASE READ THIS before continuing or posting a new issue:

• Google's ML Kit was build only for mobile platforms: iOS and Android apps.

• This plugin is not sponsor or maintained by Google. The authors are developers excited about machine learning that wanted to expose Google's native APIs to Flutter.

• Google's ML Kit APIs are ony developed natively for iOS and Android. This plugin uses Flutter Platform Channels as explained here.

  Messages are passed between the client (the app/plugin) and host (platform) using platform channels as illustrated in this diagram:

  

  Messages and responses are passed asynchronously, to ensure the user interface remains responsive. To read more about platform channels go here.

  Because this plugin uses platform channels, no Machine Learning processing is done in Flutter/Dart, all the calls are passed to the native platform using MethodChannel in Android and FlutterMethodChannel in iOS, and executed using the Google's native APIs. Think of this plugin as a bridge between your app and Google's native ML Kit APIs. This plugin only passes the call to the native API and the processing is done by Google's API. It is important that you understand this concept when it comes to debugging errors for your ML model and/or app.

• Since the plugin uses platform channels, you may encounter issues with the native API. Before submitting a new issue, identify the source of the issue. You can run both iOS and/or Android native example apps by Google and make sure that the issue is not reproducible with their native examples. If you can reproduce the issue in their apps then report the issue to Google. The authors do not have access to the source code of their native APIs, so you need to report the issue to them. If you find that their example apps are okay and still you have an issue using this plugin, then look at our closed and open issues. If you cannot find anything that can help you then report the issue and provide enough details. Be patient, someone from the community will eventually help you.

Getting Started

Before you get started read about the requirements and known issues of this plugin here.

Usage guidelines for ML Kit on-device translation

In order to use Google's on-device Translation API in your application, you need to comply with the following guidelines. These guidelines may change from time to time, and without prior notice from Google. Your continued use of the on-device Translation API is contingent upon your adherence to these guidelines. If you're uncomfortable with any of these branding guidelines, discontinue your use of the API and contact Google with your concerns. See more about the usage guidelines here.

Supported languages

ML Kit can translate between the following languages.

Usage

On-Device Translation

Create an instance of OnDeviceTranslator

final TranslateLanguage sourceLanguage;
final TranslateLanguage targetLanguage;

final onDeviceTranslator = OnDeviceTranslator(sourceLanguage: sourceLanguage, targetLanguage: targetLanguage);

Process text

final String response = await onDeviceTranslator.translateText(text);

Make sure you download both source and target language models before translating any text.

Release resources with close()

onDeviceTranslator.close();

Managing remote models

Create an instance of model manager

final modelManager = OnDeviceTranslatorModelManager();

Check if model is downloaded

final bool response = await modelManager.isModelDownloaded(TranslateLanguage.english.bcpCode);

Download model

final bool response = await modelManager.downloadModel(TranslateLanguage.english.bcpCode);

Delete model

final bool response = await modelManager.deleteModel(TranslateLanguage.english.bcpCode);

Example app

Find the example app here.

Contributing

Contributions are welcome. In case of any problems look at existing issues, if you cannot find anything related to your problem then open an issue. Create an issue before opening a pull request for non trivial fixes. In case of trivial fixes open a pull request directly.