{"id":6077,"date":"2019-03-11T08:30:42","date_gmt":"2019-03-11T07:30:42","guid":{"rendered":"https:\/\/phraseapp.com\/blog\/?p=6077"},"modified":"2024-11-06T17:37:42","modified_gmt":"2024-11-06T16:37:42","slug":"designing-apps-in-sketch-for-ios-internationalization","status":"publish","type":"post","link":"https:\/\/phrase.com\/blog\/posts\/designing-apps-in-sketch-for-ios-internationalization\/","title":{"rendered":"Designing Global-Ready iOS Apps with Sketch: A Step-by-Step Tutorial"},"content":{"rendered":"

As designers, we want to give our iOS app users joy. We do this by conducting user research and empathizing with our users’ desires as we iterate on our apps’ designs. However, we often begin to consider iOS internationalization a bit late in the development cycle. This can lead to rushed design decisions as we, for example, fix labels that break layouts in a language we didn’t anticipate. We can do our users one better by being proactive about i18n and its impact on our designs.
\nAnd that’s exactly what we’ll do in this guide. We’ll use the popular design app, Sketch<\/a>, but we’ll be just as interested in the design problems emerging from Sketch iOS internationalization, and potential solutions to them. So even if you use Adobe XD, Illustrator, PhotoShop, Figma, Invision, or another design app entirely, come along with us. I think you may learn a couple of things about designing for i18n along the way, and that can only make you a more well-rounded mobile app designer.<\/p>\n

\ud83d\uddd2\ufe0f Note \u00bb<\/em> With the Sketch integration for Phrase Strings<\/a>, the software localization solution within the Phrase Localization Platform, we can actually use real translations<\/em> provided by real translators<\/em> in our designs. We’ll cover the integration in greater detail a little later here.<\/p>\n

\n
\n

Overview<\/p>\nToggle<\/span><\/path><\/svg><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n