Comparison
ascdir and asc: compact declaration or broad automation.
Both tools can keep metadata in version control and preview changes. ascdir uses one human-readable declaration across selected App Store state, while asc combines canonical JSON metadata and approval artifacts with a much wider operational surface.
| Area | ascdir | asc |
|---|---|---|
| Primary purpose | Declarative management of selected App Store state | Broad App Store Connect and Apple Ads automation |
| Local representation | One YAML manifest with referenced Markdown and asset directories | Canonical JSON metadata directories suitable for version control and automation |
| Review and approval | Field- and asset-level read-only plans before supported writes | Dry runs plus durable metadata plans, selective approval, and plan-hash verification |
| Clearing and deletion | Explicit empty values and destructive changes require operation-specific flags | Empty metadata values are rejected; locale deletion requires allow-deletes and confirmation |
| Scope | Metadata, product-page assets, TestFlight distribution, submission, and release | App Store Connect APIs, builds, signing, TestFlight, submissions, analytics, and more |
| Build responsibility | Uses builds uploaded by Xcode, Transporter, or another build pipeline | Build, signing, export, and upload workflows are available in the same CLI |
| Best fit | Teams wanting a compact, human-readable declaration for selected App Store state | Teams wanting canonical metadata review inside a broad App Store Connect CLI |
Primary purpose
- ascdir
- Declarative management of selected App Store state
- asc
- Broad App Store Connect and Apple Ads automation
Local representation
- ascdir
- One YAML manifest with referenced Markdown and asset directories
- asc
- Canonical JSON metadata directories suitable for version control and automation
Review and approval
- ascdir
- Field- and asset-level read-only plans before supported writes
- asc
- Dry runs plus durable metadata plans, selective approval, and plan-hash verification
Clearing and deletion
- ascdir
- Explicit empty values and destructive changes require operation-specific flags
- asc
- Empty metadata values are rejected; locale deletion requires allow-deletes and confirmation
Scope
- ascdir
- Metadata, product-page assets, TestFlight distribution, submission, and release
- asc
- App Store Connect APIs, builds, signing, TestFlight, submissions, analytics, and more
Build responsibility
- ascdir
- Uses builds uploaded by Xcode, Transporter, or another build pipeline
- asc
- Build, signing, export, and upload workflows are available in the same CLI
Best fit
- ascdir
- Teams wanting a compact, human-readable declaration for selected App Store state
- asc
- Teams wanting canonical metadata review inside a broad App Store Connect CLI
Reviewed August 23, 2026 against asc's official product overview, documentation, and metadata sync workflow. ascdir is not affiliated with or endorsed by the asc project or Rork.
Choose the operating model that fits.
Use ascdir when selected App Store state should live in one compact YAML, Markdown, and asset model. Use asc when you want canonical JSON metadata with durable approval artifacts inside a much broader App Store Connect CLI. They can also coexist when a team prefers ascdir's declaration model and asc for workflows outside ascdir's scope.
Get started with ascdir →