03:10Mobile apps

Mobile app localization QA

Loqalit checks your iOS and Android app screens in every language you ship. It catches text that no longer fits, strings nobody translated, broken placeholders and right-to-left layout bugs, scores each finding with MQM, and routes fixes into Crowdin or Phrase.

9:41
Konto
LF
Lena Fischerlena@beispiel.de
  • Bestellungen
  • Account settings3
  • Zahlungsarten
{count} Artikel im Warenkorb1
Jetzt kostenlos registrieren2
de-DE
9:41
الحساب4
ل
ليلى أحمدlayla@example.com
  • الطلبات
  • الإعدادات
  • طرق الدفع
٣ منتجات في السلة
تسجيل الدخول
ar
Tonight’s app scan4 findings · MQM-scored
  • 1Critical

    Raw {count} in the cart line

    de-DE
  • 2Major

    Sign-up button text is clipped

    de-DE
  • 3Major

    “Account settings” left in English

    de-DE
  • 4Minor

    Back arrow not mirrored

    ar

What breaks in a localized app

Phone screens leave the least room for longer languages. These are the bugs that reach your users first.

Text that no longer fits

Buttons, tabs and labels that clip or wrap once the translation is longer than the English.

Strings nobody translated

English left behind on a German screen, including text that never entered your TMS.

Broken placeholders

A raw {count} or %s where a number or a name belongs.

Right-to-left layouts

Arabic and Hebrew screens that aren’t mirrored, with icons and arrows pointing the wrong way.

Glossary terms

Your term list, enforced on every screen.

Formats that don’t match

Prices, dates and numbers in the wrong style for the locale.

How it works on your app

The same crew that checks your website: Scout finds, Editor drafts, you decide, Verifier checks again.

01

Add your app

Choose the app and the languages to check.

02

Scout checks every language

Scout opens your app’s screens in each language and reads the rendered text the way your users see it.

03

Editor drafts the fix

Each finding gets an MQM category, a severity and a screenshot. Editor drafts wording that fits the space and your glossary.

04

You approve

Accepted fixes go to the string in Crowdin or Phrase as a comment with a screenshot. Verifier checks the screen again once the fix ships.

One crew for your site and your app

The same checks on your website, web app and mobile app.

Findings from your site and your app use the same MQM categories and severities, so you can compare quality across platforms and languages. Accepted fixes reach your translators the same way, in Crowdin or Phrase.

Frequently asked questions

Can Loqalit check mobile apps?

Yes, on iOS and Android. Loqalit checks your app’s screens in every language, with the same checks it runs on websites and web apps.

What does Loqalit catch in a mobile app?

Text that no longer fits, strings nobody translated, broken placeholders, text in the wrong language, glossary terms, formats that don’t match the locale, and right-to-left layout bugs.

Are mobile findings scored with MQM?

Yes. Every finding gets an MQM category and severity, with a screenshot of the screen where it appears.

Do fixes for my app go to Crowdin or Phrase?

Yes. Accepted fixes are posted to the string in Crowdin or Phrase as a comment with a screenshot, the same as for your website.

How do I get started?

Request a demo to see Loqalit on your app.

Give your app the night shift.

Every screen your users tap, checked in every language you ship.