awesome-ios: a seventy-six category link list with no version, date, or license per entry

One Markdown file is the entire product

There is nothing to install and nothing to compile. The deliverable is a single README.md on the master branch, published at http://awesomeios.dev, and the top level holds little else: .gitattributes, .gitignore, .travis.yml, CNAME, CODE_OF_CONDUCT.md, Dangerfile, LICENSE, five PNG images, one Swift file, and a .github/ directory. The license is MIT and there are no GitHub releases, so no tagged snapshot of the list exists. The last push is dated 2026-08-27. Consequence: there is no way to pin a version of the list, and no diff between releases to inspect when a category changes. If you need to know what changed since your last visit, the commit history on master is the only record you have, and a category can lose an entry between two visits without any announcement in the README.

helloworld.swift is the file that makes the repo read as Swift

The recorded primary language for this repository is Swift, and the tree contains a single Swift file at the top level, helloworld.swift, sitting in a project whose actual content is Markdown. Consequence: the language label describes that one file, not any of the frameworks the list points at. A developer filtering search results by language will pull this repository up as a Swift codebase and find one placeholder file inside it. The same caution applies to any claim that a listed library is maintained: this repository does not carry that library's code, only a hyperlink, so nothing here can tell you whether the target project is alive.

The contents block runs past seventy categories, and UI alone has thirty-two

The taxonomy is the real content, and it is uneven. UI is the widest branch, carrying more than thirty subcategories from Alert & Action Sheet through UIPageControl and Web View, with a third level under Table View / Collection View for Table View, Collection View, Expandable Cell, Header, Placeholder, and Collection View Layout. Hardware splits into Bluetooth, Camera, Force Touch, iBeacon, Location, and Other Hardware. Alongside those sit ARKit, Machine Learning, Concurrency, and GCD. Consequence: the list spans several generations of iOS vocabulary in one flat structure, so a category name tells you how the author grouped something, not whether what sits under it is current. The nesting depth is also the reason search inside the page is hard on a phone.

Every entry is a name, a URL, and one sentence

The format never varies, and that is the constraint worth understanding before you rely on it.

- [Sentry](https://sentry.io/) - Sentry provides self-hosted and cloud-based error monitoring that helps all software teams discover, triage, and prioritize errors in real-time.
- [Matomo](https://github.com/matomo-org/matomo-sdk-ios) - The MatomoTracker is an iOS, tvOS and macOS SDK for sending app analytics to a Matomo server.

No entry records a version, a minimum iOS target, a license, a maintainer, a stars count, or a date. Consequence for a reader: every one of those has to be checked in the linked project, and a link that once resolved to the current release may now resolve to an archived repository, a renamed package, or a paid product with a free tier. The list tells you the library existed in the author's sense of the word, nothing more, and an entry stays in place for years unless somebody opens a pull request to remove it.

The analytics category separates itself by hosting, not by capability

Analytics is the section whose entries the list spells out in most detail, and the blurbs carry the only comparisons it ever makes between candidates. Sentry is described as self-hosted and cloud-based, Measure as open source and self-hostable with error tracking, performance tracing, and session timelines, Matomo as an iOS, tvOS and macOS SDK that sends analytics to a Matomo server, and Countly as open source across mobile and web with crash reports and push notifications. Against those sit Bugsnag with a free tier and MOCA Analytics labelled a paid cross-platform backend. Embrace is described as built on OpenTelemetry, and Emerge Tools as blocking app size and performance regressions on every pull request. Consequence: hosting and cost are the axes the blurbs expose, and a privacy or self-host requirement is the one decision the section can actually help with.

Link rot is the failure mode the tree half-acknowledges

A list of external project links fails in one specific way: a project is renamed, archived, or discontinued and the entry keeps working while pointing at nothing useful. The tree shows what exists for that problem without describing it: a .travis.yml, a Dangerfile, a CONTRIBUTING file under .github/, and a CODE_OF_CONDUCT.md at the top level. Those are the places where pull request review and link checking would be configured, and the README does not say which of them check external URLs or how often they run. Consequence: you should assume no entry has been re-verified recently, including the analytics section, and confirm that a project still ships an iOS SDK before you plan around it.

Ko-fi and three banner images are the whole funding story

The README opens with a donation anchor to a Ko-fi page, and the top level carries buy_me_a_coffee.png, sponsor_banner.png, sponsor_banner_2.png, header.png, and example.png. Combined with the Contributing and Collaborating heading that points at CONTRIBUTING and CODE_OF_CONDUCT, this is a volunteer list: content arrives as pull requests, and the money side of it is a tip link and some banner artwork. Consequence for a reader: nobody is paid to check whether a listed library is maintained, still builds against current Xcode, or matches its description, so curation quality tracks whoever happened to submit an entry. It also means the list's incentives are visibility for submitters rather than neutrality between candidates, so an entry reads closer to a self description than to a review.

Nothing in the format answers which one you should pick

There is no ranking, no badge, no recommended marker, and no comparison between two libraries in the same category. Categories like Other Awesome Lists and Reference exist for orientation, and the list spans Analytics, App Store, Payments, Passbook, Localization, Streaming, Security, Testing, and Xcode, but the structure is a filing system, not an argument. Consequence: questions of the form which charting library should I use get no answer here, and the Server category plus Other Awesome Lists means the iOS boundary is drawn by topic rather than by a stated scope. If you need a decision, this list hands you the candidates and the decision stays yours, along with the compatibility checking the entries never did.

Editorial conclusion

Use it as a starting index, never as a dependency decision. It suits a developer who already knows the category they need and wants ten candidates to skim; it does not suit anyone who needs a ranked recommendation, a compatibility matrix, or a vetted shortlist, because the entries record none of that. Before you adopt a library you found here, open its own repository and check its Swift version, its license, its last commit, and whether the list still points at the current tag, then follow the CONTRIBUTING process if you want an entry added.

Frequently asked questions

Official sources

1. Official documentation
2. Official README
3. Project repository