Posts

Showing posts with the label internationalization

A New Collection of Thoughtful Learning Apps — Now Available on iOS & Android

Image
I’m excited to share a set of mobile apps I’ve recently completed and published on both the Google Play Store and the Apple App Store. These apps are designed with a simple goal in mind: to make meaningful, structured content more accessible, whether you’re studying theology or improving your English vocabulary. 📱 Now Available on Both Platforms All apps are live and available for download: Google Play Developer Page: https://play.google.com/store/apps/dev?id=5835943159853189043 Apple App Store Developer Page: https://apps.apple.com/ca/developer/q-z-l-corp/id1888794100 📖 Theology & Confession Study Apps For those interested in Reformed theology and classical Christian teachings, I’ve developed a series of apps that present foundational texts in a clean, focused reading format: The Belgic Confession Canons of Dort Heidelberg Catechism Westminster Shorter Catechism Each app is designed to provide a distraction-free experience, making it easier to read, reflect, and revisit these im...

How We Added Internationalization and Multi-Language Support to Our macOS App

Image
How We Added Internationalization and Multi-Language Support to Our macOS App   Supporting multiple languages is essential for reaching a global audience. In this post, we’ll walk through how we added internationalization (i18n) and Chinese localization to our macOS app, iTrans , using Swift and Xcode. 1. Audit All User-Facing Text The first step was to identify all user-facing strings in our codebase. We searched through our SwiftUI views, models, and operators for any hardcoded text that would be visible to users. 2. Extract Strings for Localization We replaced all hardcoded strings with localization-friendly APIs: For SwiftUI, we used LocalizedStringKey in Text views. For other strings, we used NSLocalizedString . Text(LocalizedStringKey("Unlock your iPhone")) // or NSLocalizedString("Untitled", comment: "File with no name") 3. Create Localization Files We created Localizable.strings files for each supported language: en.l...