A category on WKInterfaceTable that simplifies configuring Apple Watch tables with multi-dimensional data using a UITableView-like data source pattern.
IGInterfaceDataTable is an open-source Objective-C category that extends WKInterfaceTable for watchOS, providing a UITableView-like data source pattern to simplify configuring tables with multi-dimensional data. It solves the problem of having to flatten complex data structures into arrays when building Apple Watch interfaces, making table management more intuitive and maintainable.
watchOS developers building Apple Watch apps with complex, sectioned table views, particularly those familiar with UITableView patterns on iOS.
Developers choose IGInterfaceDataTable because it brings the familiar and powerful UITableViewDataSource API to watchOS, reducing boilerplate code, improving data structure handling, and enabling more sophisticated table layouts with minimal effort.
A category on WKInterfaceTable that makes configuring tables with multi-dimensional data easier.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Enables configuring tables with sections without flattening data structures, as highlighted in the README for handling complex layouts similar to Instagram's Apple Watch app.
Implements a protocol mirroring UITableViewDataSource, reducing boilerplate and easing the transition for iOS developers, with methods for rows, sections, and headers.
Provides delegate methods like didSelectRowAtIndexPath to respond to taps using index paths, avoiding manual row index mapping as described in the handling selection section.
Includes helpers such as indexPathFromRowIndex and scrollToSection to bridge WKInterfaceTable with data structures, saving development time per the README.
The project is marked as not actively maintained, posing risks for bugs, compatibility with new watchOS versions, and lack of updates, as warned in the README banner.
Requires Objective-C or bridging headers in Swift projects, which can be cumbersome and out of step with modern Swift-first development workflows.
Unit testing is manual and impractical due to WKInterfaceTable's storyboard dependency, as admitted in the testing section, hindering automated quality assurance.