A fast, declarative view layout library for iOS, macOS, and tvOS designed as a performant alternative to Auto Layout.
LayoutKit is a fast view layout library for iOS, macOS, and tvOS applications. It provides a declarative API for building user interfaces, designed to solve performance issues encountered with Auto Layout in complex, scrollable view hierarchies. The library enables asynchronous layout computation and caching to maintain smooth user interactions.
iOS, macOS, and tvOS developers building high-performance applications with complex, scrollable UIs who need a more efficient alternative to Auto Layout.
Developers choose LayoutKit for its superior performance over Auto Layout, its declarative and immutable design that improves code quality, and its seamless integration with UIKit components like UITableView and UICollectionView.
LayoutKit is a fast view layout library for iOS, macOS, and tvOS.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
LayoutKit is as fast as manual code and significantly faster than Auto Layout, with benchmarks documented on layoutkit.org to support claims of superior speed in scrollable UIs.
Enables layout computations on background threads, preventing interruptions to user interactions on the main thread, which is critical for smooth scrolling in complex interfaces.
Uses immutable data structures for layouts, making code easier to develop, test, debug, and maintain, as highlighted in the README for improved developer experience.
Produces UIViews and provides adapters for UITableView and UICollectionView, ensuring seamless integration with existing UIKit workflows without major refactoring.
No longer maintained by LinkedIn, posing significant risks for long-term support, bug fixes, and compatibility with future iOS versions, as explicitly stated in the README.
Lacks a constraint system, requiring custom logic for dynamic view relationships, which can be cumbersome compared to Auto Layout's flexible constraint model.
Being unmaintained and niche, it has a smaller community and fewer resources compared to Auto Layout or SwiftUI, making troubleshooting and adoption harder.