Hello, App Bird

https://github.com/TweetingBirds/appbird

I started a new project called App Bird. It’s a small command line tool that keeps your App Store listing in your app’s repo, as plain text files, and syncs it with App Store Connect only when you say so.

Why I built it

There are plenty of other tools that do similar things. But with the help of Claude I can build customized tools like this quickly. I built this after having issues with my initial submission of Quips. I messed up the submission of the Mac and iOS apps with the subscriptions. There was also a missing field that to be honest Apple should have flagged before even letting me click the Submit button (rejected 7 days later). But now with App Bird I can run appbird check and know if my submission is ready to go.

The App Store listing is some of the most important text an app has. It’s the first thing most people read. But for most of us it lives in a web form: no history, no review, no way to see what changed or who changed it. App Bird allows you to add the app listing data to your code so it is version controlled alongside your app code.

What it does

You run appbird pull once, and your description, keywords, subtitle, promotional text, release notes, URLs and the rest land in a metadata/ folder, one file per field per language. Commit it. From then on, the workflow is the one you already use for code:

  1. Edit the files.
  2. Open a pull request, so someone (or future you) can review the change.
  3. Run appbird diff to see exactly what’s different from App Store Connect.
  4. Run appbird push once it’s merged.
$ appbird diff
Version 1.1 (PREPARE_FOR_SUBMISSION, editable)

update 1.1 en-US
  ~ en-US/promotional_text: 'Rate it in one tap.' → 'Rate it in one tap, now in German.'
  ~ en-US/description
      [@@](https://micro.blog/@) -3,1 +3,1 [@@](https://micro.blog/@)
      -Every visit, kept whole
      +Every journal entry, kept whole

$ appbird push
Write 2 change(s) to App Store Connect? [y/N] y
→ update 1.1 en-US
Done: 2 change(s) written. Nothing was submitted for review.

It covers more than the text you’d expect:

  • Screenshots, app previews and creative assets, with appbird media diff, push and pull. Files are matched by checksum, so an unchanged screenshot is never uploaded twice.
  • TestFlight “What to Test” notes and test information.
  • Subscriptions and in-app purchases: their names, descriptions and review notes.
  • App Info settings: categories, the age rating questionnaire and content rights, in one app_info.json.
  • appbird check, which goes through what App Review needs and tells you what’s missing before you submit.
  • appbird validate, an offline check of character limits, URLs and locale codes. It needs no API key, so it runs on every pull request in CI.

What it will never do

This was a design rule from day one. App Bird never submits anything for review and never touches prices or availability. It doesn’t release versions, add or remove testers, or delete localizations. diff only reads, and push shows you the diff and asks first.

Submitting an app and setting its price are decisions, and I want a person to make them in App Store Connect. App Bird’s job is to get the words and pictures right and out of the way.

Small, on purpose

  • One binary, no dependencies. A single static executable for macOS, Linux and Windows. No Ruby, no gems, no Python.
  • fastlane-compatible. The text files use fastlane deliver’s names, so if you already have a fastlane/metadata folder, you can point App Bird at it.
  • Easy to hand to an AI agent. The README has copy-paste prompts that set it up, add the CI workflow, or edit the listing, and each one tells the agent to stop before anything writes to App Store Connect.

And yes, there’s an owl. Run appbird version for fun. We all need more joy.

Where it stands

App Bird is at 0.8.0. The core is done: text, media, TestFlight, in-app purchases, App Info, readiness checks, and JSON output for scripts. It can also self-update (appbird update).

It isn’t 1.0 yet, and that’s deliberate. My plan is to use it on real apps for a while before I promise a stable file layout. The road to 1.0 is freezing that layout, writing proper 1.0 docs, and making install easier (Homebrew, a notarized binary, and a reusable GitHub Action). I’ve completed 4 app releases with App Bird and I love that it is easy and gets out of the way. Claude also loves using it and thinks the logo is cute.

Try it

curl -fsSL https://raw.githubusercontent.com/TweetingBirds/appbird/main/install.sh | sh
cd my-app
appbird init com.example.myapp
appbird pull

You’ll need an App Store Connect API key; the README walks through making one. App Bird is MIT licensed and lives at github.com/TweetingBirds/appbird.