A simple AutoLayout-friendly keyframe animation framework for iOS, written in Swift, perfect for scrolling app intros.
RazzleDazzle is a keyframe-based animation framework for iOS, written in Swift, designed to create smooth, scroll-driven animations. It solves the problem of building complex app intro sequences and paging scroll view layouts by providing an AutoLayout-friendly API that simplifies animation management and ensures proper responsiveness across different device orientations and screen sizes.
iOS developers building scrolling app introductions or paging interfaces in Swift, particularly those who need AutoLayout-compatible animations that work seamlessly with modern iOS features like split-screen multitasking.
Developers choose RazzleDazzle for its simplicity, AutoLayout integration, and extensive animation types, offering a Swift-native alternative to JazzHands with easy extensibility for custom animations and reliable performance in scrolling contexts.
A simple keyframe-based animation framework for iOS, written in Swift. Perfect for scrolling app intros.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
The keep(view: onPage:) function ensures paging layouts adapt seamlessly to device rotations and split-screen modes, as highlighted in the README for iOS9 compatibility.
Supports over a dozen built-in animation types including alpha, scale, rotation, and constraint animations, covering most common UI effects for scroll-driven interfaces.
Written in Swift with protocol-oriented design, it offers a modern and type-safe interface for iOS developers, building on the legacy of JazzHands.
Allows creating custom animation types by conforming to Animatable and extending Interpolatable, enabling developers to tailor effects to specific needs.
Requires Swift 3.0 and Xcode 8, making it incompatible with older projects or those on different Swift versions without significant migration work.
Primarily designed for scroll-driven animations, so it lacks support for other animation contexts like user interactions or timeline-based sequences, limiting its versatility.
Uses an imperative keyframe-based approach that can lead to verbose and hard-to-maintain code compared to more modern declarative frameworks.