A flexible iOS library for building fully customizable paging UI with interactive menus and content views.
PagingKit is an iOS library for creating paging user interfaces with interactive menus and content views. It solves the problem of rigid design in other paging libraries by offering highly customizable layout and visual components, enabling developers to implement any UI design without modification constraints.
iOS developers building apps that require tabbed navigation, onboarding screens, or any paging interface with custom visual designs, especially those who find existing libraries too restrictive.
Developers choose PagingKit for its extreme flexibility in layout and design, allowing complete customization of menu and content views while providing a familiar UIKit-like API. It stands out by decoupling behavior from layout, giving full creative control.
PagingKit provides customizable menu UI. It has more flexible layout and design than the other libraries.
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 complete control over view arrangement, enabling menus in navigation bars, floating buttons, or custom positions, as demonstrated in the sample GIFs with varied layouts.
Supports diverse visual styles like tag-like menus, underscore indicators, and App Store-like designs by subclassing PagingMenuViewCell, with examples provided in the README.
Uses data source and delegate patterns similar to UITableView and UIScrollView, making integration intuitive for iOS developers accustomed to UIKit conventions.
Decouples paging behavior from layout, giving developers full control over component structure without inheritance constraints, as outlined in the class design philosophy.
Requires creating custom cells and focus views from scratch, with multiple steps in Storyboard and code, as detailed in the lengthy Getting Started guide—no out-of-the-box styles.
Built exclusively for UIKit, lacking native SwiftUI support, which forces additional bridging work for modern iOS apps using SwiftUI.
Provides no pre-designed menus or indicators; developers must implement all visual elements themselves, increasing initial development time compared to more opinionated libraries.