Questions

The home of three tools for indie iOS developers: Pitlane, Docket and Metrics. They are made by one developer who ships apps alone.

Each works on its own. Together they cover the loop: Pitlane builds and runs your projects, Docket tracks what ships next, and Metrics shows how it is doing.

Pitlane serves a local HTTP API and Docket has an MCP server and a CLI, so an agent such as Claude Code can build your app and update your backlog.

Pitlane runs on macOS. Docket runs on macOS, iOS and iPadOS. Metrics runs on iPhone and iPad.

Pitlane replaces the Xcode window for the loop you repeat all day: pick a project, build, run it on a simulator or a cabled iPhone, archive when it's ready. Xcode itself stays installed, because Pitlane calls its xcodebuild and simctl, but it stays closed while you work. Edit in Cursor, Claude Code or Xcode; Pitlane handles the building and running.

Yes. Pitlane drives the Xcode you already have, a full install selected with xcode-select on macOS 14 or later, so the compiler, the simulators and the signing are Apple's own. It shares Xcode's DerivedData, so a build here and a Run in Xcode reuse the same cache.

Add them to Pitlane's sidebar. Each project remembers its own scheme, configuration and destination, builds can run side by side, and Pitlane idles at a few tens of megabytes, so the only thing costing RAM is the build itself.

Yes. While Pitlane runs it serves a small HTTP API on 127.0.0.1, loopback only. An agent can list your projects and simulators with their memory, start a build, read the parsed errors and warnings, launch the app and stop it: the same actions as the buttons, license gate included. curl 127.0.0.1:4747/ prints the usage text, and one switch in Settings turns the API off.

Reduce Simulator Memory in Pitlane switches off the roughly 170 background services a simulator boots that your app never calls: Siri, Spotlight, News, photo analysis, iCloud sync. Each simulator ends up two to four times smaller in memory, the change sticks across reboots, and anything your apps declare in their entitlements or Info.plist, from push to widgets to HealthKit, stays on. It needs an iOS 18 or newer runtime, and Restore Background Services puts a simulator back to stock.

That is what the memory reduction is for. Stock simulators together mean swapping on a modest Mac; reduced ones fit several at once, and Pitlane can switch the services off before every Build & Run so new simulators start light. The sidebar shows every booted simulator's process count and real footprint, plus the total against your RAM.

Pitlane parses the output as it streams into a list of errors and warnings. Click one and Xcode opens at that line; an agent reads the same list over the API. The full log is still there too.

Pitlane's reset ladder goes Clean, then DerivedData, then the package caches, then the global SPM cache, then the stuck processes, ordered by how much each rung throws away so you start with the cheapest fix. It tells you what it cleared.

It launches xcodebuild and simctl on your behalf, which the App Sandbox forbids. It's signed with a Developer ID certificate and notarized by Apple instead, so it opens without a warning.

Yes. Pitlane checks in about once a day and gets back a signed pass that lasts three days, so a flight or a weekend without a connection changes nothing.

No analytics, and nothing about your projects or your code leaves the Mac. There are two outbound requests: an update check you can turn off, and one check-in a day that sends a one-way hash of your Mac's hardware ID, plus your license key and the Mac's name once you have one.

Metadata, in-app events, nominations and build status, for all your apps at once.

Anything the app does through its UI. An agent can read tasks, update status and check build state through MCP.

Scripted access to your backlog from the terminal. Useful in git hooks, CI scripts, or when you want to add a task without opening an app.

Jira, Trello and Linear are built for teams of engineers. Docket is built for a solo developer working with AI agents, which can read and update tasks directly through MCP.

'Show me my Metrics', 'How is my app doing in Metrics', or 'What did I earn today in Metrics'. Per-app and portfolio queries both work.

App Store Connect API credentials are stored in the iOS Keychain. Reports cache on-device. Nothing is sent off-device, and the daily AI insight is generated locally by Apple's Foundation Models.

The free tier tracks a single app fully. Pro unlocks unlimited apps.

Yes. Choose the demo data option on first launch to see the full app with a sample portfolio.