A Swift layout library for iOS and tvOS that simplifies creating complex, responsive UICollectionView layouts.
BrickKit is a layout library for iOS and tvOS that enables developers to build complex and responsive user interfaces using a declarative, object-oriented approach. It abstracts the intricacies of UICollectionView, allowing for dynamic layouts that adapt to screen size, orientation, and content changes with minimal code.
iOS and tvOS developers building apps with complex, responsive layouts such as grids, nested sections, or interactive behaviors like sticky headers and cover flow effects.
Developers choose BrickKit for its declarative API that simplifies UICollectionView management, built-in advanced behaviors like sticky headers and cover flow, and support for dynamic sizing and nested sections without extensive boilerplate code.
DEPRECATED - BrickKit For IOS
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Allows defining complex UICollectionView layouts using simple Swift objects like Brick and BrickSection, reducing boilerplate code as shown in the README examples with minimal setup.
Supports dynamic widths and heights based on ratios, fixed values, auto-layout, and rules combining size classes and orientation, enabling adaptive UIs that change with screen size.
Includes behaviors like sticky headers, cover flow, and spotlight effects with minimal configuration, demonstrated in the README GIFs with just a few lines of code.
Enables hierarchical layouts by nesting BrickSections, facilitating intricate UI structures without manual management, as illustrated in the multi-sections example.
The README explicitly states BrickKit is being phased out and will not be maintained, posing risks for future compatibility, bug fixes, and iOS updates.
Introduces its own terminology (e.g., Brick, BrickSection, BrickDimension) and conceptual model, which can be complex and time-consuming to master compared to native APIs.
Tied to UIKit without SwiftUI support, making it less future-proof as Apple pushes modern frameworks, and requiring bridges for integration that add complexity.