Bohr
A framework for composing iOS settings screens with built-in cell types and extensible customization.
What is Bohr?
Bohr is an iOS framework for composing settings screens in apps, providing a structured way to organize and manage user preferences. It solves the problem of building customizable and extensible settings interfaces by offering built-in cell types for common settings and allowing developers to create custom cells.
iOS developers building apps that require settings or configuration screens, particularly those using Objective-C or Swift with UIKit.
Developers choose Bohr for its ease of use, built-in cell types, and extensibility, enabling rapid development of settings screens without sacrificing customization.
Overview
Settings screen composing framework
Use Cases
Best For
- Building iOS app settings screens with common input types
- Creating customizable configuration interfaces for user preferences
- Extending settings functionality with custom cell designs
- Organizing settings into structured sections and cells
- Developing iOS apps that require dynamic or complex settings layouts
- Integrating settings screens with Carthage or CocoaPods dependencies
Not Ideal For
- Projects requiring long-term maintenance or support, as Bohr is officially abandoned
- Apps built with SwiftUI that need native integration with modern Apple frameworks
- Teams wanting a drop-in solution with minimal customization overhead for simple settings
- Large-scale applications where dependency on an unmaintained library poses integration risks
Pros & Cons
Pros
Includes ready-to-use cells for common setting types like switches, text fields, dates, and choices, as listed in the 'Built-in BOTableViewCell's' section of the README.
Allows easy creation of custom cell subclasses via the 'BOTableViewCell+Subclass.h' header, enabling support for any setting type, as demonstrated in the 'Subclassing BOTableViewCell' section.
Uses BOTableViewController and BOTableViewSection to logically group settings into sections and cells, simplifying setup as shown in the 'Basic setup' example.
Supports installation via Carthage, CocoaPods, or manual drag-and-drop, providing integration flexibility for different project workflows, per the 'Installation' section.
Cons
The README explicitly states 'THIS PROJECT IS NO LONGER MAINTAINED,' meaning no bug fixes, updates, or community support, which is a critical drawback for production use.
Does not support SwiftUI, Apple's modern UI framework, making it obsolete for new projects adopting current iOS development standards, as hinted by the suggested SwiftUI Form alternative.
While extensible, creating custom cells requires subclassing and manual implementation, which can be more time-consuming than using higher-level frameworks with pre-built components.
Frequently Asked Questions
Related Projects
SWTableViewCellAn easy-to-use UITableViewCell subclass that implements a swippable content view which exposes utility buttons (similar to iOS 7 Mail Application)
MGSwipeTableCellAn easy to use UITableViewCell subclass that allows to display swippable buttons with a variety of transitions.
SwipeCellKitSwipeable UITableViewCell/UICollectionViewCell based on the stock Mail.app, implemented in Swift.
MCSwipeTableViewCell:point_up_2: Convenient UITableViewCell subclass that implements a swippable content to trigger actions (similar to the Mailbox app).
Found a gem we're missing?
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.