iOS on the App Store · macOS as a direct download

Henge

A photoreal Stonehenge that keeps real time.

Druidic in spirit, ceremony and season — archaeological in fact, stone by cited stone.

HAND-ROLLED METAL 4 · NO ENGINE · NO NETWORK

ON THE APP STORE WATCH THE WALKTHROUGH MAC — EARLY BUILD

The instrument

The sky is computed, and every claim about the stones can be checked.

Henge is a real-time 3D simulation of Stonehenge for iPhone, iPad and Mac, built on a hand-rolled Metal 4 renderer (with a Metal 3 path for the simulator and older GPUs) — no game engine, no third-party code. Choose any date, from the monument's own era to tonight, and stand inside a sky that is computed rather than painted.

I

The sky is computed, never faked

Sun, moon, planets and 8,870 Hipparcos stars from the published ephemerides — Meeus, VSOP87, Laskar's obliquity — with ΔT and atmospheric refraction carried honestly back to 3000 BC. No hardcoded azimuths. The solstice bearing is derived, and the fact that it misses the built axis by a fraction of a degree is a finding, not a bug.

II

The shadows are the calendar

The renderer's shadows are measured against an analytic solution that lives outside the renderer, and the suite fails if they disagree by more than 0.28 m on the ground — a tolerance set by the shadow map's texel, not by taste. Visual plausibility is never accepted as agreement.

III

The stones stand where the survey puts them

Every surviving stone stands on the 1989–90 Rees plan of the monument (Historic England Archive, via Tim Daw's open digitisation), and every fallen block lies where it lies. Heights come from Cleal, Walker & Montague's Stonehenge in its Landscape where that appendix has been carried through; the rest, and every stone's cross-section, are labelled reconstructions until the per-stone data lands. Each stone says which it is, and every statement the app makes about the monument carries a tier and a citation, enforced by the type system.

IV

True scale, on real ground

One unit is one metre, everywhere — the stones, the grass, the sun's angular diameter, and Salisbury Plain itself from Environment Agency LiDAR. The sun rises over the actual skyline ridge, which delays it, which moves its bearing. That is the kind of detail the whole app is made of.

The numbers

Accuracy is measured by the test suite, not asserted by the marketing.

These tolerances are pinned by tests against published worked examples — loosening any of them requires the owner's sign-off, by charter.

0.001°
Solar apparent longitude
vs. Meeus's worked examples
0.002°
Right ascension & declination
vs. published ephemeris values
0.0001°
Obliquity of the ecliptic
Laskar — what keeps 2500 BC honest
0.28 m
Rendered shadow vs. analytic solution
measured on the ground, every run
What the engine establishes, computed rather than assumed — sunrise and sunset bearings against the monument's built axis of 49.9°.
Bearing2500 BC2026
Midsummer sunrise, flat horizon47.71°48.77°
Midsummer sunrise, 0.6° skyline49.08°50.11°
Midwinter sunset, 0.6° skyline230.10°231.12°

Against the built axis, midwinter sunset is the tighter fit — two tenths of a degree in the builders' own era. The monument may face the dying year, not the growing one. The app shows you both and lets the sky argue.

Four thousand years

Watch the monument rise — or fall — while the calendar walks between the eras.

Two labelled states, never blended: the monument at Stage 4, c. 2200 BC (Darvill et al. 2012), and the ruin as it stands. Switching between them plays the passage — the ditch silts, the bank settles, stones arrive one at a time in construction order and leave in gravity's own — while the sun arcs overhead in timelapse and the year counter spins through four millennia. Every frame of that sky is a real computation for a real date.

AS IT WASStage 4, c. 2200 BC · the whole monument · fresh chalk banks
AS IT STANDStoday · the ruin as surveyed · the silted ring