Nov 10, 2026

Appos: Operator, Runner, Publisher, and Tiny Projects in One Window

I took four standalone Mac apps for building and shipping mobile apps and put them in one window. Appos is a single project list with Run, Publish, and Tasks one click away, and each tool still works on its own.

Appos: Operator, Runner, Publisher, and Tiny Projects in One Window

Last time I wrote about four small Mac apps that keep my mobile projects moving: Operator, Runner, Publisher, and Tiny Projects. They worked well. They also had a flaw that I only noticed once I started using them every day: each one was its own app, so moving a single app through a single workflow meant a gaggle of windows.

So I put them in one window. It's called Appos (the Greek god of apps, and, if you squint, the App Operating System).

The problem with four windows

The tools did hand off to each other. Open Runner from Operator and it picked up the same project; the same went for Publisher. The handoffs were fine. The windows were the problem.

A typical pass on one app, say Golf Sparks, from "I changed the code" to "it's with testers" had me with Operator, Runner, Publisher, and Tiny Projects all open at once, plus Terminal and Android Studio. All of that for one app going through one workflow. Cmd-Tab became part of the process, and I kept losing track of which window held the thing I wanted.

None of the tools was bad. Having them as separate windows for a single job was.

One project list, everything hangs off it

Appos has one sidebar: every project, with its icon, and under the name the one thing I most want to know, which is how many tasks are left. Click a project and the right side shows its page: tasks, the agent sessions I can continue, Studio, Finder, Terminal, and Git status with the ship button.

Appos showing the project list on the left and GolfSparks's project page on the right, with its task list and Publish, Run, and New Claude buttons

That page is Operator. The other three tools are now things you do to a project, so they open from it.

Run opens Runner, in place

Press Run on a project and Runner opens on the right, already pointed at that project: my iPhone, the Android emulator, an iOS simulator, the Compile iOS check, and a gate that tells me when my Firebase functions are out of date before I put a build on a device. A breadcrumb across the top (‹ Operator › GolfSparks › Runner) tells me where I am, and Esc takes me back.

Runner open inside Appos for Golf Sparks, showing device choices and a warning that Firebase functions need a deploy

Publish opens Publisher, in place

Publish does the same with the release side: what's next on the road from internal testing to production, which build is live on each track, and the store listing and activity tabs. The status updates are in the same window as the code and the device, so "waiting for Google Play review" is visible without leaving the project.

Publisher open inside Appos for Golf Sparks, showing the release overview with internal testing live and production waiting on review

One rule I kept on purpose: you can't jump straight from Runner to Publisher. Both open from the project page and both close back to it. A release should start from a project, not from whatever happened to be on screen.

Tiny Projects lives at the top

Tiny Projects is pinned above the project list as a tool, and every project's task count in the sidebar comes from it. Click Open in Tiny Projects on a project's page and the list opens scrolled to that project. If a project has no list yet, there's a button to create one. A project and its task list are matched by name (habit-hero is "Habit Hero"), so there's no mapping file to maintain.

Tiny Projects open inside Appos, showing every project's pending tasks

Builds keep going when you leave

If a build or an upload is running and I close the pane, it keeps running. The project's row in the sidebar shows a spinner (Running… or Publishing…) until it finishes, or Last run failed if it didn't. I can go look at another project while the first one builds.

The tools are still separate

This is the part I care about most. Appos doesn't replace the other apps or copy their code. Each tool is now split into a library (OperatorKit, RunnerKit, PublisherKit, TinyProjectsKit) plus a thin app around it. The standalone Operator, Runner, and Publisher still build and run exactly as before. Appos is a second host for the same code: it links the libraries from the sibling checkouts, so a fix in Runner shows up in both after a rebuild.

If all you want is the project launcher, build Operator and stop there. If you only ship to the stores, build Publisher. Appos is for when you want it all in one place.

Build your own

All of these are skills that your coding agent can build from, so you get a version that fits your own folders, devices, and release process instead of copying mine:

  • build-operator: the project launcher
  • build-runner: build and run on a phone, emulator, or simulator
  • build-publisher: Google Play, TestFlight, and the release workbench
  • build-tiny-projects: the small task list (a single web page, with an optional MCP server so an agent can add tasks)
  • build-appos: the window that puts them together

They're in the skills repo ↗. Start with build-operator, add the others when you want them, and build-appos last.

What's next

My apps are all still at $0 in revenue, so the real test is whether a smoother loop gets more of them in front of more people. The loop is shorter now. We'll see whether that matters.

Matt Dyor
by Matt Dyor
More Posts
It Took Two Tries to Get Buen Día onto Google Play

It Took Two Tries to Get Buen Día onto Google Play ↗

Google rejected Buen Día for freezing on a low-memory review device. Here's what we changed, the timeline, and how long each build took.

Published Nov 21, 2026

Buen Día: From Native Swift to Kotlin Multiplatform, 82% Shared

Buen Día: From Native Swift to Kotlin Multiplatform, 82% Shared ↗

I took a native iPhone app written in Swift and rebuilt it in Kotlin Multiplatform and Compose Multiplatform. About 82% of the code is now shared, and the same app went to Google Play.

Published Nov 17, 2026

30,000 Lines in Two Weeks: Massive Changes in the Hunt for Product-Market Fit

30,000 Lines in Two Weeks: Massive Changes in the Hunt for Product-Market Fit ↗

Golf Sparks 1.1 added about 30,000 lines of app, web and backend code in two weeks, roughly a quarter of the whole codebase, and it reached both stores the same night. A new batch is already waiting. This is the new normal.

Published Nov 15, 2026

Simplified Startup Business Framework: CP Squared, Revisited for the AI Era

Simplified Startup Business Framework: CP Squared, Revisited for the AI Era ↗

In 2016 I wrote a one-page framework for early startups: Customer, Pain, Competition, Product. Now that AI lets anyone build anything, it matters more, because the scarcity is a problem worth solving.

Published Nov 13, 2026

Going to Production on Google Play and the App Store

Going to Production on Google Play and the App Store ↗

What it actually took to take Golf Sparks from testers to production review on both stores in one weekend: payments you can test before launch, the store-console forms that block you, and a short checklist.

Published Nov 2, 2026

How I Work with Operator, Runner, Publisher, and Tiny Projects

How I Work with Operator, Runner, Publisher, and Tiny Projects ↗

A walkthrough of Operator, Runner, Publisher, and Tiny Projects: the small Mac apps I use to organize projects, build and test mobile apps, handle releases, and keep follow-up work visible.

Published Oct 30, 2026

Page generated at: 2026-11-21T23:14:44.855Z