Skip to content

Product Terminology

This page is the single source of truth for official Appcircle product and module names. All customer-facing surfaces (status page, API docs, UI, marketing, support) must use the customer-facing terminology listed here, not internal microservice names.

Info

This page is a follow-up to PL-201, which aligned the status.appcircle.io component names with the terminology used on docs.appcircle.io. When you add or rename a customer-visible component, check it against this page first.

Why it matters

Customers do not know our internal service names. Showing internal naming on customer-visible surfaces confuses readers, hurts trust, and makes our products harder to search for. Consistent terminology across every surface keeps the product coherent and reduces support load.

Internal → customer-facing name mapping

These are the renames agreed in PL-201. Use the customer-facing name on every customer-visible surface. Not all of these are modules: some are features or actions (for example, Webhooks, In-app Notifications, Re-sign Binary, Testing Portal, Appcircle MCP Server). The official module list is in the next section.

Internal Name Customer-Facing Name
Web Hooks Webhooks
Build Management Build
Signing Identity Management Signing Identities
Testing Distribution Management Testing Distribution
Publish Management Publish
Enterprise App Store Management Enterprise App Store
Resign Binary Re-sign Binary
Testing Distribution Portal Testing Portal
Web App Notifications In-app Notifications
MCP Gateway Appcircle MCP Server

Official module names

The official Appcircle modules, as documented on docs.appcircle.io:

Module Documentation
Build https://docs.appcircle.io/build
Signing Identities https://docs.appcircle.io/signing-identities
Testing Distribution https://docs.appcircle.io/testing-distribution
Publish https://docs.appcircle.io/publish-to-stores-module
Enterprise App Store https://docs.appcircle.io/enterprise-app-store
Appcircle CodePush https://docs.appcircle.io/code-push

Naming notes

These customer-facing names are the short, surface-level labels (for example, status page components). The official documentation sometimes uses a longer canonical form. Both refer to the same product; prefer the form that fits the surface, and never use the internal name.

  • Build is labelled "Build Module" in the docs heading ("Build Module Overview"). Use "Build" as the short component/module label.
  • Publish is titled "Publish to Stores" in the docs. Use "Publish" as the short label and "Publish to Stores" when the full module name is needed.
  • Signing Identities (plural) is the module name. Body text in the docs occasionally says "Signing Identity module" (singular); prefer the plural form.
  • Re-sign Binary is the canonical action label (hyphenated, capital B). The Testing Distribution variant appears as "Re-sign Binaries" (plural). Do not use "Resign" without the hyphen.
  • Webhooks is one word (capital W). Do not write "Web Hooks".
  • In-app Notifications uses a lowercase "a" in "app". Do not write "In-App Notifications".
  • Appcircle MCP Server keeps "MCP" in all caps and all three words capitalised.
  • Appcircle CodePush is written as two words, "Appcircle" plus "CodePush", where "CodePush" is a single word with a capital C and a capital P. Do not write "Code Push" or "Codepush".