Why a web studio ships apps
Because the interesting problems do not respect the boundary. Par-5 started as a directory of every golf course in America — 12,464 of them, mapped by state and town from open data, on static pages with nothing computed while a visitor waits. Once that corpus existed, the phone was the obvious place for it, so the same product got wrapped natively.
Why Not Run came the other way. The app existed first: adaptive training plans that rewrite themselves against what you actually ran, rather than a fixed template off a chart. The job was a product site that could explain that engine to a runner in under a minute without turning into documentation.
Both are the same lane as the client work, which is the point. Something that fits no category, built from a blank file, and still custom the whole way down.
How an app gets built here
Neither of these started as an app project, and that shapes how they are built.
Par-5 is a static site first. The directory is flat files generated ahead of time, with nothing computed while somebody waits, and the native app wraps that same product rather than reimplementing it. One corpus, one set of rules about what a page is allowed to claim, two places to read it. When the data improves, both improve, because there is only one of them.
Why Not Run runs the other way around. The training engine is the product and the plans are computed on the device, so the app carries real logic rather than being a shell around a website. The marketing site is a separate static build whose only job is to explain that engine well enough that a runner starts a trial.
Both ship to iPhone first. That is a resourcing decision rather than a philosophical one: one person shipping to one platform properly beats two platforms shipped badly, and Apple's review process is the harder of the two to satisfy. Android is a roadmap item for Why Not Run rather than a promise with a date on it.
Status, stated plainly
Neither app is downloadable yet. Par-5 is in review and could be approved any day; Why Not Run is heading the same way. When either is live, the card at the top of this page changes from a status line to a real App Store link, and that is a one-line change to a data file rather than a rebuild of the page.
Until then there is deliberately no download badge here. Apple's badge artwork may only be used unaltered and pointed at a live listing, so a greyed-out or decorative version of it would be a guidelines violation. A line of type is the honest version.
