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

By -
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...
Post a Comment

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

By -


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.lproj/Localizable.strings for English
  • zh-Hans.lproj/Localizable.strings for Simplified Chinese
Each file contains key-value pairs for all user-facing text.

Example (English): 


"Unlock your iPhone" = "Unlock your iPhone";
Example (Chinese): 

"Unlock your iPhone" = "解锁你的 iPhone";

4. Add Localization Files to the Xcode Project

To ensure Xcode recognizes the localization files:

  • We added both Localizable.strings files to the project via the Project Navigator.
  • In the File Inspector, we enabled localization for each file and checked all supported languages.

5. Test Localization

Xcode makes it easy to test your app in different languages:

  • In the scheme editor, we set the Application Language to Chinese (Simplified) and ran the app.
  • We also verified that all UI text appeared correctly in both English and Chinese.

6. Results

With these steps, our app now fully supports both English and Chinese. All user-facing text is localized, and switching languages is seamless for users.

Conclusion:
Internationalization in Swift and Xcode is straightforward when you follow best practices: extract all user-facing text, use localization APIs, maintain .strings files for each language, and test thoroughly. This approach ensures your app is ready for a global audience.

❤️ Support This Blog

If this post helped you, you can support my writing with a small donation. Thank you for reading.

Coffee ☕ Thanks 🙏 Extra Support ❤️

Comments

Post a Comment

Popular Posts

2026 Begins: Choosing to Stay on the Path as a Blogger

By -
Image
  Today is January 1st, 2026 . Before rushing into new goals, I spent some time looking back at the past 12 months of data for this blog — the quiet numbers that tell a very honest story. Looking Back at the Numbers Over the past year: 📈 Total views: ~44,600 👀 Daily average visits: ~200 💬 Comments: 19 💰 AdSense income: about $0.01 per month At first glance, these numbers may look small — especially the income. But when I zoom out, I see something more meaningful. This blog has been quietly read every single day . No viral posts. No aggressive promotion. No paid traffic. Just consistent readers arriving through search, bookmarks, and curiosity. That consistency matters. What the Traffic Graph Tells Me The graph over the last 12 months shows something important: Early months were quiet and uneven Mid-year brought steady growth Toward the end of the year, traffic became more stable , with clear spikes when certain posts resonated This tell...
Read more

Health Checks and Scaling Strategies for Next.js in Kubernetes

By -
Image
Health Checks and Scaling Strategies for Next.js in Kubernetes This is Part 6 and the final post of the series: Self-Hosting Next.js in Kubernetes (Without Vercel) . At this point, your Next.js standalone app: Builds cleanly Runs in a minimal Docker image Deploys correctly on Kubernetes / OpenShift Serves static assets properly Uses runtime configuration and secrets Now let’s make it resilient and scalable . Why Health Checks Matter Kubernetes relies on health checks to: Know when a pod is ready to receive traffic Restart unhealthy containers Safely roll out new versions Without proper probes, traffic can be sent to a pod that isn’t ready yet. Readiness Probe A readiness probe tells Kubernetes: “This pod can accept traffic.” For most Next.js apps, the root path works well: readinessProbe: httpGet: path: / port: 3000 initialDelaySeconds: 10 periodSeconds: 5 If your app depends on downstream services (APIs, d...
Read more