A realtime dynamic localization and translation delivery system for iOS and macOS apps, enabling text updates without recompiling or redeploying.
LocalizationKit is a dynamic localization framework for iOS and macOS that allows developers to manage and update app translations in realtime without needing to recompile or redeploy. It connects to a free web service where text changes are made and instantly reflected in the app, solving the problem of frequent text updates and language additions requiring developer intervention.
iOS and macOS developers who need to manage multilingual apps with frequently changing text, or teams where non-developers (like product managers or translators) need to update app content without coding.
Developers choose LocalizationKit because it eliminates the traditional localization workflow of rebuilding and resubmitting apps for text changes, offering realtime updates, inline editing, and a seamless integration with Interface Builder, all while being free to use.
Realtime Dynamic localization translation delivery system for iOS and Mac OSX in Swift. Create and update texts from localization.com without needing to recompile or redeploy. Cocapod for iOS devices (iPad, iPhone, iPod Touch and Mac)
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Text changes made in the web UI appear instantly in the running app as you type, enabling immediate feedback without rebuilds.
Update localized strings without recompiling or resubmitting to app stores, reducing developer overhead for frequent changes.
Enable long-press on UI elements like UILabel and UIButton to edit translations directly in the app, facilitating quick adjustments.
Set localization keys directly in Xcode's attribute inspector for supported components, streamlining design workflows.
Relies on LocalizationKit.com, introducing vendor lock-in and a single point of failure if the service changes or goes down.
Only supports specific UIKit components with no mention of SwiftUI, restricting use in modern iOS development.
The README admits a TO DO for a build phase script to pull first versions, indicating gaps in offline readiness and setup complexity.