A Swift framework that simplifies building forms and static content using UIStackView and view controller composition.
StackViewController is a Swift framework that simplifies building forms and other static list-based user interfaces on iOS. It replaces the cumbersome use of UITableView for static content by leveraging UIStackView's layout strengths while adding missing features like scrolling, separators, and keyboard management. The framework encourages cleaner code through view controller composition and better separation of responsibilities.
iOS developers building forms, settings screens, or other static content interfaces who want to avoid UITableView boilerplate and leverage UIStackView effectively. It's ideal for those adopting modern iOS design patterns and view controller containment.
Developers choose StackViewController because it provides a purpose-built solution for static content that eliminates UITableView's complexity for such tasks. Its unique selling point is combining UIStackView's simplicity with essential UITableView features and promoting maintainable code through view controller composition.
A controller that uses a UIStackView and view controller composition to display content in a list
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Automatically embeds UIStackView in a UIScrollView and handles autoscroll when the keyboard appears, eliminating the need for manual UITableViewController-style boilerplate.
Supports adding content via both UIView and UIViewController instances, promoting cleaner MVC separation and reducing massive view controller anti-patterns.
Provides toggleable separator views between content views that are managed automatically during insertions and removals, a feature missing from plain UIStackView.
Designed specifically for static content like forms, avoiding complex UITableView data source and delegate methods for non-dynamic lists.
Relies on UIStackView, making it incompatible with older iOS versions and limiting use in legacy apps without upgrades.
As a niche framework, it has less community support and fewer resources compared to UIKit standards, with potential risks if updates stall.
Lacks built-in support for swipe actions, reordering, or section headers/footers, requiring custom implementations for such needs.