Keep the Swift. Explore new hardware.
We’re building bridges between Apple’s software world and the devices you choose.
Porting source and running a guest OS are different engineering problems. Daybreak explores both, with the boundaries visible.
Compile selected Swift and SwiftUI source against ShimKit’s compatibility surface. Your app keeps its language while Android supplies the host.
Selected UI and device features have been verified on hardware. API coverage is still incomplete.
Study Darwin and controlled iOS guest applications on Android: booting, drawing, input, and the machinery that connects them.
Controlled fixtures, not a general IPA launcher. Apple system images are not included.
Our primary testing spans Pixel 3a, 6, 7, 9, and 10a, alongside other targets including the obscure BlueBerry. Daylight DC-1 and Nothing Phone (3) are part of the wider workbench. Testing coverage varies by device and runtime path.
Read the current workflow guide ↗Selected SwiftUI views render through the Android host. Unsupported framework APIs remain.
Controlled UIKit fixtures exercise layers, text, and target-action input. General app compatibility remains open.
Reproducible setup, clearer device checks, and an easier edit–build–run loop.
Illustrated deep dives into compatibility, rendering, and input. Step through the diagrams or let them play.
Compare source compilation, Mach-O loading, and an operating-system guest.
Read the illustrated guide ↗FIELD GUIDE 02 / INTERACTIVEManipulate the layer geometry and replay a corrupted or replaced frame.
Read the illustrated guide ↗FIELD GUIDE 03 / INTERACTIVEChange fit, fill, and rotation; inspect contact coordinates and queue behavior.
Read the illustrated guide ↗Browse the field wiki ↗ How Backstep works ↗
A testing fleet, not a compatibility certification. Individual results depend on the OS image, device, and execution path.