The OldOS Project recreates iOS 4 and retools it for iOS 26
Recreating a fully functional version of iOS 4 in SwiftUI.
At a glance
- What is it?
- The OldOS Project is a SwiftUI recreation of an old iOS, built by one person over roughly six months of high school. Its apps talk to the real data on your phone, its file layout is built to be copied and extended, and the README has no build instructions at all.
- Who is it for?
- The OldOS Project is worth reading as a demonstration of how much of an operating system's surface can be rebuilt in a declarative UI framework, and as a code layout exercise, since the shared-components-then-copy pattern is the most transferable idea in it. Three things to know before you try to build it.
- Can I use it commercially?
- Not without permission. GitHub finds no licence file in the repository, and without a licence all rights are reserved by default: you may read the code but not reuse it. Check the README, or ask the authors, before using it.
- Is it still maintained?
- Yes. The repository last received commits 14 days ago.
- What is it written in?
- Mainly Swift, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- zzanehip/The-OldOS-Project3,559 ★ · +24
| Repository | 2026-09-24 | 2026-11-15 |
|---|---|---|
| zzanehip/The-OldOS-Project | 3.5k | 3.6k |
24 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
It recreates an old iOS and targets a current one
The repository's own description is one sentence: a recreation of a fully functional version of iOS 4 in SwiftUI. The aim is stated in the next section as a merge, pairing today's technologies with a recreation of the user experience from about ten years ago, designed to be as close to pixel perfect as the author could get. The current release note makes the second half of that explicit. Version 2.0 is described as bringing the project back and retooling it for modern devices, naming iOS 26 among them, and for developers it adds compilation fixes and support for the latest Xcode versions. So the host system is several generations newer than the system being imitated, which is the whole point of the exercise and also the reason it needed a second pass.
The apps are wired to the data on your phone
What separates this from a set of static mock screens is a claim about integration. The README says the vast majority of apps are fully functional, meaning they integrate with the data on your phone to deliver what it calls a live, emulator-like experience, and it names four examples: play your music in the iPod app, get directions in Maps, surf the web in Safari, view the current weather in Weather. It also says no shortcuts were taken in fleshing out the system, listing background changes, settings adjustment and app search, while conceding that a few apps are not ready yet. The stated benefit is that you no longer need a secured legacy phone to try it, since it runs on your daily device. That framing also explains the project's other stated purpose: letting anyone see how the old system worked, and showing what a declarative UI framework can do.
The layout is a set of bases you copy
The Where to Begin section is the most useful thing in the README, and it explains the file layout rather than the features. The project is organised as one file per app, with code and commentary behind each. Beside the app files there is a Common file, and the author's stated intent is to structure the app the way Apple built interface builder: a collection of base UI elements that are available to copy into any other file when you need custom behaviour, and usable as-is when the generic version is enough. Then come HomeScreen and LockScreen, which together stand in for the Springboard, and the asset catalogue, where images are organised by app. The practical consequence for a reader is that there is no shared framework to learn: the pattern is copy this file, which is also why the file count is as high as it is.
There is no build instruction anywhere in the README
The README covers what the project is, what is special about it, how the code is arranged, a screenshot section that renders as an empty image block, a thanks section and a licence line. It does not contain a single command. There is no clone step, no project open step, no dependency note, and no mention of the deployment target or the signing configuration. That is unusual for a project inviting people to learn from it and modify it, and it is not helped by the repository listing, which has six entries and no project file at the top level. Two of those six are worth noting anyway: a submodules file, so part of the tree comes from elsewhere, and a small JSON file at the root whose purpose the README never states.
Images arrive twice, by two different routes
The README says image assets are structured by app inside the asset catalogue, which is the normal place for them. The repository listing also has an Images directory at the top level, next to the source directory and the submodules file, which is not where an asset catalogue lives. With a submodules file also present, the most likely reading is that the top-level image directory is pulled in from somewhere else and that the catalogue inside the project is generated or maintained alongside it. That is an inference from the listing rather than something the README states, and the reason it matters is practical: if you clone without initialising submodules, some imagery will be missing and nothing in the README will tell you why. Reading the submodules file is the first thing to do here.
The licence is stated once and recorded nowhere else
The last section of the README names an attribution licence, Creative Commons Attribution 4.0, with a link. The repository header records no recognised licence value at all, and there is no licence file among the six top level entries. So the two do not conflict, exactly, but only one of them says anything. For a project whose stated purpose includes being modified and built on by others, that asymmetry is worth resolving before you fork it: a Creative Commons licence is a content licence rather than a software licence, and whether that was the intent or simply the closest button is not something the repository answers. Everything else in the header is conventional, with a single primary language recorded and no homepage.
Releases are IPA builds numbered by a build counter
The three recent releases are named in two layers. The tags are a version and a build number joined by a low line character, and the release titles describe them as IPA builds of version 2.0: build 8 dated 2026-08-22, build 7 dated 2025-12-07, and build 1 dated 2025-06-29. So the newest tag shares its timestamp with the last push to the default branch, and the build counter is the versioning scheme, not a semantic version. The gap in the visible list between build 1 and build 7 is eight months, which is a slower cadence than the tag numbers suggest. There is no changelog in the repository and no documentation site linked, so the update notes live in the README banner rather than in release descriptions.
Editorial conclusion
The OldOS Project is worth reading as a demonstration of how much of an operating system's surface can be rebuilt in a declarative UI framework, and as a code layout exercise, since the shared-components-then-copy pattern is the most transferable idea in it. Three things to know before you try to build it. The README documents no build steps, no project file and no dependency setup, so you are working from the source alone. The release artefacts are IPA builds rather than a test flight listing. And the licensing is stated once in the readme as an attribution licence while the repository header records nothing, so check which terms you are actually relying on.
Frequently asked questions
Where can I find the OldOS TestFlight code?
The README does not mention TestFlight. What the release list shows is IPA builds: tags that pair a version with a build number and are titled as IPA builds of version 2.0, the newest being build 8 dated 2026-08-22.
What are OldOS made of?
Mostly SwiftUI, according to the README, which says the project is built almost entirely with it. The structure is one file per app, a shared Common file of base UI elements that you copy when you need custom behaviour, HomeScreen and LockScreen standing in for the Springboard, and images organised by app in an asset catalogue.
What is The-OldOS-Project?
A recreation of a fully functional version of iOS 4 in SwiftUI, aiming at a pixel-perfect recreation of the old user experience while running on modern devices. The author says it was built over roughly six months while in high school, and the whole app is open sourced.
Which apps in OldOS actually work?
The README says the vast majority are fully functional and integrate with the data on your phone, naming iPod for music, Maps for directions, Safari for the web and Weather for current conditions. It also concedes that a few apps are not ready yet.
What changed in OldOS version 2.0?
The update note in the README says version 2.0 brings the project back and retools it for modern devices, including iOS 26. For developers it adds compilation fixes and support for the latest versions of Xcode.
Official sources
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.
[](https://hysenlabs.com/projects/zzanehip-the-oldos-project)Star history chart for your README
[](https://hysenlabs.com/projects/zzanehip-the-oldos-project)Was this useful?