A playground system for iOS development that supports both Objective-C and Swift, enabling rapid prototyping with live code reload.
KZPlayground is an open-source playground system for iOS development that supports both Objective-C and Swift. It enables developers to write, test, and visualize code in real-time with live reloading, eliminating the need for the traditional edit-compile-run-debug cycle. It provides interactive controls, animations, and timeline snapshots to prototype UI and logic quickly.
iOS developers working with Objective-C or Swift who want to accelerate prototyping and experimentation in their projects. It's particularly useful for those building interactive UI components, animations, or testing production code in a sandboxed environment.
Unlike Apple's Swift Playgrounds, KZPlayground supports Objective-C and offers faster performance, along with advanced features like interactive controls, auto-animations, and IDE-agnostic live reloading. It integrates seamlessly into existing projects via CocoaPods and provides full access to iOS simulator capabilities.
Better playgrounds that work both for Objective-C and Swift
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Supports both Objective-C and Swift, with the README claiming faster performance for Objective-C than Apple's Swift Playgrounds, making it versatile for legacy and modern iOS projects.
Enables live code reload via tools like Dyci or injectionforxcode, allowing instant application of changes without full recompilation cycles, as demonstrated in the demo videos.
Provides a rich domain-specific language for controls, animations, and snapshots, such as KZPAdjustValue for tweaking values and KZPShow for visualizing objects, speeding up UI experimentation.
Offers full iOS simulator access and integrates via CocoaPods, so developers can prototype with the same code used in production apps, reducing context switching.
Requires installing multiple third-party tools like Dyci, injectionforxcode, and the kicker gem, plus configuring build phases and subclassing, which can be time-consuming and error-prone.
Relies on external code injection tools that may not be updated for new Xcode versions, as noted in the README for Dyci installation, risking compatibility breaks and support issues.
Kicker processes need to be manually started and killed, and the setup involves editing build phases without automatic cleanup, adding operational overhead and potential for forgotten processes.