joshuaswarren/omarchy-apple-dev
- Source
- GitHub
- First trending
- Category
- Coding tools
- GitHub stars
- 325
- Main language
- Python
This page introduces an external open-source repository. It is not an HDATF product.

What it does
This project provides scripts and compatibility tools for developers who want to build iOS apps from Omarchy Linux instead of running Xcode on macOS. Its inputs include Swift or SwiftUI app sources, project resources and an Apple-distributed iOS SDK. Swift and xtool produce an app bundle, while separate scripts handle USB device installation and preparation of an IPA distribution package. The inspected shipping script sequences release building, resource preparation, signing, packaging and offline validation, with upload enabled only by an explicit option. Starting requires a supported Linux machine, a matching Swift and SDK combination and an Apple ID to obtain the Xcode archive containing the SDK. Physical-device work also needs an iPhone and USB connection, while TestFlight requires a paid Apple Developer account and App Store Connect credentials. The README reports successful builds and Apple processing for selected apps, but those results were not reproduced in this review. It also distinguishes older device-debugging evidence from the newer toolchain and describes Linux-only wireless deployment limits, so this should not be treated as universal Xcode compatibility.
How it helps ATF
If ATF Works considers a native iPhone client, this could be compared as a Linux-based build route for a small prototype rather than adopted as a replacement for the current product. Harness could examine the separation of build, validation and optional upload when defining an external build executor. Candidate integration data would include the source revision, Swift and SDK versions, app identifier, artifact path and validation report, with signing credentials kept outside ordinary task records. A trial should separately verify device launch, resource rendering, signing and Apple processing because a local build alone proves none of the later stages. No ATF Works client or Harness integration was implemented here, and universal project conversion, unattended credential handling and wireless deployment are outside this proposal.
License
MIT Permissive. Commercial use and changes are allowed if the copyright notice is kept.
More in this category
- nykooi1/vibe-wise
A Claude Code plugin for learning while building software. It asks users for their approach before implementation, discusses tradeoffs and explains code changes afterward. - tester-army/e2e
An end to end testing framework for web and mobile apps. A test describes a goal in natural language and an agent drives the app to reach it, while locators and assertions check the result inside the same test. An agent step that a later assertion verifies is recorded, and the next run replays it with no model calls until the app changes. - arismarioneves/hyphp
A Windows PHP development environment that runs multiple PHP versions simultaneously and declares the version per project. It supports Apache or nginx, MySQL, local domains and HTTPS without Docker. - Louis-CFM/coucou
A desktop companion for monitoring Claude Code sessions from a MacBook notch or the top of a Windows screen. It shows session activity and permission requests, and provides chat and file input. - edgcpp/compiler
A C/C++ compiler project centered on the EDG front end. It includes C and C++ code generation, template instantiation tools, and utilities for intermediate representations.
Only repositories in the ranked Trendshift lists are included, and the lists are used only to find candidates. We do not copy their ranks. Descriptions, licenses and star counts come from each GitHub repository. The notes are our own reading. We have not tested these projects, and a place on a trending list does not prove quality.