Open-source project
dkhamsing/open-source-ios-apps avatar
dkhamsing/open-source-ios-apps

Open-Source iOS Apps: A Curated Index, Not a Codebase

:iphone: Collaborative List of Open-Source iOS Apps

53,277 stars6,183 forksUnknownCC0-1.0

At a glance

What is it?
dkhamsing/open-source-ios-apps is a community-maintained directory of open-source iOS, iPadOS, watchOS, tvOS, and visionOS apps. It is a reference list, not a project you run, and its value depends on the quality of its entries and the freshness of its data.
Who is it for?
Adopt this repository if you are an iOS developer or technical evaluator looking for a single, browsable index of open-source apps across Apple platforms, especially if you want to find reference implementations for specific frameworks like SwiftUI, Core Data, or React Native. Do not use it if you need a maintained codebase or a package manager; it is a list of links, not a collection of code.
Can I use it commercially?
Yes. CC0-1.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository received new commits within the last day.
What is it written in?
GitHub does not report a main language for this repository.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • dkhamsing/open-source-ios-apps53,277 ★ · +1,542
Star history
Repository2026-08-182026-11-15
dkhamsing/open-source-ios-apps51.7k53.3k

1,542 Stars in the last 89 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

What This Repository Actually Is

The dkhamsing/open-source-ios-apps repository is a collaborative, categorized list of open-source applications for iOS, iPadOS, watchOS, tvOS, and visionOS. The README states it is a "collaborative list" and invites contributions. It is not a codebase you clone and build. There is no source code to compile, no framework to import, and no binary to run. Instead, it is a data file, contents.json, that generates a README with links to many external projects. The repository is licensed under CC0-1.0, which means the list itself is public domain, though each linked app retains its own license. For an engineer evaluating open-source options, this is a discovery tool, not a dependency. Its purpose is to save you from trawling GitHub search results by organizing apps into categories like Apple TV, Apple Vision, Browser, Finance, and Health, with subcategories such as Contact Tracing and SwiftUI.

The Mechanism: contents.json Drives Everything

The README carries an HTML comment that says: "This README is generated, please do not update. To contribute, make changes to contents.json." That is the core mechanism. The repository stores its data in a structured JSON file, and the README is produced from it, likely by a script or a GitHub Action. This design keeps the list consistent and prevents contributors from editing the rendered output directly, which would lead to formatting drift. Each entry in the JSON presumably contains fields for the app name, URL, a description, tags for language and framework, a screenshot link, and an optional App Store link. The README example shows entries with fields like `2026`, `swift`, `swiftui`, and star counts, though those star counts are not evidence of quality and the README itself warns nothing about them. The generated format means the list is only as accurate as the data in contents.json, and any error in that file propagates to the README. If you want to add an app, you must edit the JSON, not the Markdown, which is a specific workflow that contributors must follow.

How to Get It Running (or Rather, How to Use It)

Since this is a list, "getting it running" means either browsing the README on GitHub or cloning the repository to inspect the data. To clone, you would run `git clone https://github.com/dkhamsing/open-source-ios-apps.git`. Once cloned, you can open the `contents.json` file in any text editor or JSON viewer. There is no build step, no package manager, and no installation command. If you want to contribute, the README points to a CONTRIBUTING.md file, which you would read before submitting a pull request. The workflow is: fork the repository, edit `contents.json` to add or modify an entry, and submit a pull request. The README explicitly says contributions are welcome. For a user, the practical command is simply `open README.md` after cloning, or just visit the GitHub page. There is no API to query the list programmatically, at least not documented here, so if you need machine-readable access, you would parse the JSON file yourself.

Categories and Coverage: What You Can Find

The README lists a wide range of categories, from Apple TV and Apple Vision to Weather and Misc, with subcategories like GitHub, Terminal, Content Blocking, and ResearchKit. This breadth is the repository's main strength. For example, under Apple TV you get BiliBili, Moonlight Game Streaming, and VLC. Under Apple Vision, there are visionOS-specific apps like Beatmap AR and Destination Video. The Misc section includes framework-specific tags such as Core Data, Firebase, Flutter, React Native, and SwiftUI, which is useful if you want to see how a particular technology is used in real apps. The list also has dedicated Official and Clone categories. However, the coverage is not exhaustive, and the presence of an app does not mean it is actively maintained. The year tags, like `2026` or `2025`, likely indicate the last update year, but that is not stated explicitly in the README, so you should not infer maintenance status from them alone.

The Limitations: A List Is Not a Vetting Process

The most significant limitation is that the repository performs no quality control beyond linking. There is no indication that each app is tested, builds successfully, or adheres to any licensing standard. The README includes star counts for most entries, but those are not a measure of code quality or security. The repository is not archived, and its last push was on 2026-11-02, so the list itself is being updated; that still says nothing about whether each linked app is maintained. Also, because it is a collaborative list, there is a risk of duplicate entries, outdated links, or apps that have been removed from the App Store. For an engineer, using this list to find a reference implementation for a specific framework is fine, but you must verify each linked repository independently.

Alternatives: GitHub Search and Awesome Lists

A direct alternative is GitHub's own search, which allows you to filter repositories by language, topic, and last update. For example, searching for `language:Swift topic:ios` gives you a live, always-updated list, but without the curated categorization. Another alternative is the "awesome-ios" list, a popular curated collection of iOS libraries and resources, but that focuses on libraries, not full apps. The key difference is that open-source-ios-apps is specifically about complete applications, not components. If you want to see how an entire app is structured, this list is more targeted. However, GitHub search gives you recency and activity data directly, which this list does not. The trade-off is curation versus freshness: this list offers human organization, but it can become stale, while GitHub search is always current but requires you to do the filtering yourself. For a one-off search, GitHub search might be faster; for a broad survey of app categories, this list is more convenient.

Maintenance and License Implications

The repository is licensed under CC0-1.0, which means the list itself is dedicated to the public domain. You can copy, modify, and redistribute the list without restriction, though the linked apps have their own licenses, which you must respect separately. The maintenance model is collaborative: anyone can contribute by editing contents.json and submitting a pull request. The README includes a Thanks section and a Contact section, and the repository is owned by dkhamsing. The last push was on 2026-11-02, and recent releases include 3.3.2 (2026-10-03). Even so, repository activity says nothing about whether each linked app is maintained. If you plan to use this list as a reference, you should check the commit history and the last push date on GitHub before assuming it is actively maintained.

Editorial conclusion

Adopt this repository if you are an iOS developer or technical evaluator looking for a single, browsable index of open-source apps across Apple platforms, especially if you want to find reference implementations for specific frameworks like SwiftUI, Core Data, or React Native. Do not use it if you need a maintained codebase or a package manager; it is a list of links, not a collection of code. Before relying on any entry, verify the linked repository's license, last commit date, and whether it still builds with current Xcode versions, because the directory does not perform any of those checks. The repository's own README warns that it is generated from contents.json, so treat the metadata as a starting point, not a guarantee of quality or maintenance.

Frequently asked questions

What is the best open-source app on open-source-ios-apps?

The list does not pick winners or rank anything. It groups apps into categories and gives each one a link, a year, lowercase framework tags, and a star count, so the choice stays with the reader.

How do I add an app to open-source-ios-apps?

Edit contents.json, not README.md. The generated header states that the README is produced output, so edits to the Markdown are lost on the next build, and the contribution steps live in .github/CONTRIBUTING.md.

Does open-source-ios-apps show whether an app is still maintained?

No. An entry carries a year, lowercase tags, and a star count, with no last commit date, release tag, or build status, so maintenance has to be judged from the linked repository itself.

Which platforms does open-source-ios-apps cover?

iOS, iPadOS, watchOS, tvOS, and visionOS. watchOS, tvOS, and visionOS each have a top-level heading, while iPad support appears only as an ipad tag on individual entries.

Official sources

  1. Official README
  2. Project repository
  3. Release notes
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/dkhamsing-open-source-ios-apps.svg)](https://hysenlabs.com/projects/dkhamsing-open-source-ios-apps)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/dkhamsing-open-source-ios-apps.svg)](https://hysenlabs.com/projects/dkhamsing-open-source-ios-apps)

Was this useful?