How to Capture and Upload Screenshots to the Applanga Dashboard using an Integration
This article will show users how to automatically upload screenshots to the Applanga dashboard. To learn how to upload new or edit existing screenshots manually see the Uploading & Editing Screenshots documentation.
On Applanga, regular screenshots can be turned into Smart Screenshots to provide even more context for translators and reviewers. Smart Screenshots are a combination of the screenshot itself with a specific set of metadata that informs Applanga about which strings are present on a screen as well as the string’s position.
The main ways to upload screenshots via an integration include:
Screens uploaded via the Applanga SDK or design plugin automatically capture the string/screen pairing and the string’s position. For screens uploaded via the API, users can send the metadata of the screen association (tag) and string positions along with the upload call.
For the Draft Mode option:
See the Draft Mode and On-Device Testing page for more details about the Applanga Draft Mode.
This option is only available for Applanga API integrated apps. See the Applanga API documentation for additional details. The API screenshot upload process allows Applanga users to send the string position as metadata along with the screenshot upload API call.
This option is only available to users with an Adobe XD, Figma, or Sketch integrated project using the Applanga plugin. See the Localization at the Design Stage article and the Adobe XD, Figma, or Sketch Documentation for more information.
The Applanga design plugin will import the strings as well as the strings’ position for each screen. Applanga Design Plugin users can easily upload base language screens, translate within the Applanga dashboard, then download translated strings to generate translated screens.
If an app already has automated UI tests, users can simply add one line of code to the test scripts at the point where screenshots uploads are needed.
Follow the instructions outlined in the integration documentation to implement this option: