I am building a set of Android and iOS apps — you can check them out at apps.dyor.com ↗. Keeping everything organized as I am building the mobile codebases, the marketing websites, the Firebase backend, the Google Play and App Store listings, the GitHub repos… wait, what was I talking about? Oy yes: keeping all these plates spinning is essential if I want to grow the revenue for these apps 100× (they are all at $0 — so perhaps even more!).
The four small apps that keep my work moving are Operator, Runner, Publisher, and Tiny Projects. Operator gets me to the right codebase, Runner builds and runs mobile apps, Publisher handles releases, and Tiny Projects keeps project follow-ups visible.
Start with Operator
Operator is the front door to my projects. It scans a directory (e.g., DyorProjects) where I keep all of my projects, groups folders by category (e.g., KMP projects, web projects, local projects, native projects), and gives me all of the typical ways I want to interact with a particular type of project (e.g., go to the project in Finder or Terminal, jump into an agent session for that project, push a project to GitHub). For Kotlin Multiplatform projects built on Koko ↗, there are shortcuts to launch Android Studio from the embedded MobileApp directory.
The important part is that the project list also shows what I can do next. After I finish a coding loop with an agent, I can jump over to Runner and run the server or push the mobile app to my phone - I do not need to flip between the syntax of starting up a local web server or opening up Xcode or Studio or writing some syntax to test out the new feature. If it is a mobile app, it has a link to Publisher so I can move releases to Google Play and App Store (more details below). Operator also shows Git status at a glance: whether the working tree has changes and whether the local branch is ahead of or behind its upstream. When I need current remote information, Fetch & Refresh fetches before updating the overview.
When code is ready to move, Operator provides a review step before pushing. On the main branch, that is a push. On a feature branch, it can merge the work into main. The review shows changed files and asks for a commit message, so I can see what is about to move before I start the operation.
Try it with Runner
For mobile projects, the next step is Runner. I choose the app and a target: an Android phone or emulator, an iOS simulator, or a paired iPhone. Runner builds, installs, and launches the app, with the build output visible in its window. If I only want a quick Kotlin/Native check, Compile iOS builds the framework without opening Xcode.
That gives me a short loop: make a change, run it on a real device or simulator, read the build output, and go back to the code. Runner remembers the last app and device, and closing its window does not stop a build already in progress.
Once I’m happy with the change, Runner’s ship action opens Operator’s Git review. After the change is on main, Publisher can see the new commits.
Ship it with Publisher
Publisher is where I handle the release and store side. It shows each app’s release status, checks what is configured and ready, and gives me separate views for the release overview, store listing, and activity history.
For Google Play, Publisher can build and upload an Android release, manage listing updates, and promote an existing artifact between testing tracks. For the App Store, it can upload to TestFlight and work with the listing and review submission flow. Before a build, it checks for release blockers. It also compares local listing files with the store so I can review what would change before uploading.
Keep the small tasks visible with Tiny Projects
Tiny Projects gives each project a small, focused task list. I use it to keep the next follow-up in view without turning every idea into a heavyweight project plan.
The tools fit together: Tiny Projects keeps the next tasks visible, Operator opens the right codebase, Runner helps me verify changes, and Publisher handles the release.
Make the workflow reusable
I’m also turning the ideas behind these tools into three reusable Codex skills: one for building a project launcher like Operator, one for a device-focused build and run tool like Runner, and one for a release workbench like Publisher. The goal is to help someone create a version that fits their own projects, devices, and release process instead of copying my folder paths or credentials.
The whole loop
The work starts in Claude Code on a side branch. From there I want a repeatable path through GitHub checks, Google Play testing, TestFlight, tester feedback, and production. When the testers find something to improve, I go around the loop again. When a release is ready, the marketing site and store listings need to catch up too — including the screenshots.
Open the full-size release workflow diagram ↗
Tiny Projects, Operator, Runner, and Publisher help keep planning, code, testing, and release connected. The screenshots, announcements, and store pages are part of shipping too: they help people understand what changed and decide whether to try the app.
Video
I’m preparing a walkthrough of this workflow, from a Tiny Projects task through the project list, a device run, and the release overview. The video link will go here when it’s ready.





