Command line vs Mac app · Different jobs
A fastlane deliver alternative
for the editing you still do by hand.
fastlane deliver is free, open source, and the standard way to push App Store metadata, screenshots and builds from CI. It's very good at that. What it doesn't give you is a place to read and edit 50 locales at once, or any handling of In-App Purchases, Game Center or customer reviews. AppMeta is a native Mac app for that interactive side, and plenty of developers end up using both.
How does AppMeta compare to fastlane deliver?
deliver automates a release. AppMeta is for a person editing a listing. They overlap on metadata and screenshots and split everywhere else.
fastlane deliver: A command-line action configured by a Deliverfile. Metadata lives in plain .txt files under fastlane/metadata/<locale>/.
fastlane deliver: Unattended uploads and submission from GitHub Actions, GitLab CI, Jenkins, Bitrise, Codemagic and other CI services.
fastlane deliver: Renders your local files into an HTML preview and asks you to confirm, without comparing them to what's live.
--force skips the preview in CI. Before submitting, it can run precheck, which scans for placeholder text, unreachable URLs and other common rejection reasons.fastlane deliver: Metadata, screenshots, App Previews, binaries, review information, submission and phased release. TestFlight is fastlane's separate pilot action. There's no fastlane action for IAPs, Game Center or reviews.
fastlane deliver: Free under the MIT license. Needs Ruby 3.2 or later and a fastlane setup in your project.
fastlane deliver: Text files you can commit to git and review in pull requests, which is one of deliver's biggest strengths.
AppMeta vs fastlane deliver, feature by feature
A GUI for interactive editing next to the CLI most iOS teams already run.
| Feature | AppMeta | fastlane deliver |
|---|---|---|
| Interface | Mac app | Command line + Deliverfile |
| Price | $17.99/year or $29.99 lifetime | Free, open source (MIT) |
| Runs in CI | No | Yes |
| Metadata storage | Local working copy fetched from App Store Connect | .txt files per locale, easy to keep in git |
| Pull existing metadata | Fetch in the app | deliver download_metadata / deliver init |
| Review before upload | Live value vs your edit, per field | HTML preview of local files; no comparison with live |
| Push granularity | One field, one locale or all locales | Whole run (skip flags for metadata, screenshots, binary) |
| Binary upload | No (use Xcode or Transporter) | Yes |
| Screenshots | Upload for iPhone, iPad, Mac, Apple Watch, Apple TV | Yes, plus App Preview videos |
| Submit for review / phased release | Yes | Yes |
| In-App Purchases and subscriptions | Yes | No fastlane action |
| Game Center | Yes | No fastlane action |
| Customer reviews | Read and reply | No fastlane action |
| TestFlight | Built in | Separate action (pilot) |
| Keyword analysis | On-device checks + optional AI | None (precheck covers rejection risks) |
| Authentication | App Store Connect API key, stored in the Keychain | API key file, or Apple ID + 2FA session that expires |
| Requirements | macOS 14 or later | Ruby 3.2+; macOS (other OSes partly) |
fastlane details were checked on 25 October 2026 against docs.fastlane.tools and the fastlane GitHub repository (release 2.241.1). Behaviour can change between releases, so check the deliver docs for your version.
Who should keep fastlane deliver, and who should add AppMeta?
- You edit listings by hand across many locales
- You want to see the live value next to your change before anything is pushed
- You manage In-App Purchases, subscriptions or Game Center
- You reply to customer reviews
- You'd rather not keep a Ruby toolchain around for metadata edits
- Your release is scripted and runs in CI
- You want metadata in git, reviewed in pull requests
- You upload binaries from the same pipeline
- You want free and open-source tooling
- You never touch metadata by hand between releases
If you use both, pick one source of truth. When deliver's text files live in git and you edit in AppMeta, run fastlane deliver download_metadata afterwards so the next CI upload doesn't put the old text back.
About AppMeta
Questions
FAQ
What is the best GUI alternative to fastlane deliver?
Is fastlane deliver free?
Does fastlane deliver show a diff before uploading?
Can fastlane manage In-App Purchases, Game Center or reviews?
Does AppMeta upload builds or run in CI?
Can I use fastlane deliver and AppMeta together?
Try it
Open AppMeta.
Keep fastlane for the pipeline. Use AppMeta when a person needs to read, compare and edit the listing.
Last updated