• Add visionOS support

• AddGitHubAPIto get licenses from GitHub API
• UpdateAcknowListViewControllerandAcknowListSwiftUIViewto get missing licenses from GitHub API, with newcanFetchLicenseFromGitHubproperty to disable this behavior
• AddURLextension withopenWithDefaultBrowser()function to fix opening URLs on macOS with SwiftUI

• UpdateAcknowListSwiftUIViewto fix navigation to repository URL
• AddAcknowListRowSwiftUIView

• AddAcknowListstruct to represent list model
• AddAcknowPackageDecoderto parse “Package.resolved” files (Swift Package Manager)
• Refactor plist file parser intoAcknowPodDecoder
• RefactorAcknowParserto manage parsing different file types
• Refactor file paths parameters (String) into file URLs (URL) instead
• UpdateAcknowListViewControllerto load acknowledgements from “Package.resolved” by default

• Follow readable content guides
• Fix Swift Package Manager warning (exlude DocC folder)

• Add SwiftUI interface (supports iOS/tvOS/watchOS/macOS) (#83)
• Add DocC resources (#86)
• Fix Xcode 13 support (#85), by Thomas Mellenthin (@melle) and Francesc Bruguera (@ifrins)
• Update CocoaPods and Swift Package Manager support to require iOS 13/tvOS 13, necessary to support SwiftUI

• UpdateAcknowListViewControllerdefault initializer implementatoin to fix Xcode 13 support (#89,#91)

• UpdateAcknowListViewControllerto remove Objective-C compatibility, fi xing Xcode 13 support (#89,#91)

• UpdateAcknowListViewControllerto make initializers available with Objective-C (#81)
• Fix header/footer layout when resizingAcknowListViewController(#82)

I’m very happy to finally release the AcknowList “2.0” update.

This projectstarted in 2013,and, on the surface, it hasn’t changed much. It’s still parsing the same data, presenting it with the same interface. And I believe it’s still as useful today as ever, to help us promote all the amazing libraries that power our mobile applications.

Under the hood, there have been a lot of improvements. Labels are localized with more than 10 languages, licenses are nicely formatted, views support all the accessibility features, Dynamic Type, Dark Mode, Safe Area, and so on.

This “2.0” update introduces automatic link detection in headers and footers (thanks toNSDataDetector) and customizable table view style. It’s also the right time to break backward-compatibility. We get rid of superfluous methods and rename some parameters. The goal is to make this library easy-to-use, customisable, and future-proof.

So what happens next?

I currently still maintainSwiftandObjective-Cversions of this library. They both have their merits, but I think we’re past the point of diminishing returns. It will soon be time to deprecate the Objective-C project, to focus on just one version.

I never got around to offer an AppKit implementation... but the most obvious path forward is SwiftUI. Would that be a different library, or just a new option? Does the model need to change too, and offer a Combine API? I’ve created aGitHub issue,so feel free to join the discussion.

• UpdateAcknowListViewControllerto detect URLs in header and footer
• UpdateAcknowListViewControllerto makeacknowledgementsproperty non-optional
• UpdateAcknowListViewControllerinitializers
  • Add optional table view style parameter (#69), by Matt Croxson (@Lumus)
  • Add initializer with array ofAcknow(#75)
  • Rename plist path parameter (#75)
  • Remove initializer with multiple plist paths (#75)
• Improve Swift Package Manager support
  • Support SPM localized resources (#72), by Patrick (@iDevelopper)
  • Add SPM test target (#73)
  • Add SPM example project
  • Move sources, tests, and resources to follow SPM guidelines (#74)
• Add CocoaPods example project
• Update supported platforms to iOS 9 and more recent