Technology partners

Get your product into Appbrew apps.

Build one npm package. Appbrew enables it for merchant apps and lists you in the Integration directory.

A pure-JS package ships with the next scheduled app release.

Build apps for brands? Agency partner program 

Shopify brands running their app on Appbrew

  • SwimOutlet
  • Kut from the Kloth
  • SUGAR
  • Mixology
  • Anatomie
  • Pixi
  • Sukoshi
  • perfectwhitetee
  • littlebox
  • Beastlife
  • Minimalist
  • Judge.me
  • Klaviyo
  • GoKwik
  • Yotpo
  • Recharge
  • Okendo
  • Smile.io
  • Gorgias
  • Rebuy
  • LoyaltyLion
  • Attentive
  • CleverTap
  • MoEngage
  • WebEngage
  • AppsFlyer
  • Branch
  • Shiprocket
  • Stamped
  • Loox
  • Appstle Subscriptions
  • Boost AI Search & Filter
  • Firework
  • Afterpay
  • Apple Pay
  • BiteSpeed
  • BON Loyalty
  • Contlo
  • Google Ads
  • Joy
  • Junip
  • Nector
  • Netcore
  • Privy
  • REVIEWS.io
  • Rivo
  • Tidio
  • Shopflo
  • Return Prime
  • ViSenze
  • Wizzy.AI

From repo to listed

One package, five steps, your own repo.

  1. Partner quickstart 
  2. Build an integration 
  3. Testing your work 
  4. Publishing your package 
  5. Appbrew enables it 
Your repo
# from your repo root$ pnpm create-integration my-integration$ pnpm install # packages/my-integration├── package.json   # the manifest└── src    └── index.ts
Kiyoko Beauty’s Appbrew app: product cards with star ratings
  • blockReviewsBadge
  • trackerAnalyticsEvent.VIEW_ITEM
  • manifest"key": "enableBadges"
Your repo
# iOS and Android, on a draft theme$ pnpm run-ios$ pnpm run-android # for a tracker, the events must# arrive on your platform
Release workflow on GitHub
# Run workflow · bump: patch, minor or major✓ Build my-integration✓ Publish to npm.appbrew.tech✓ Tag the release # versions are immutable
"appbrew": {
  "configKey": "my-integration",
  "requiresNativeBuild": false,
  "settings": [
    { "key": "apiKey",
      "title": "API key" },
    { "key": "merchantId",
      "title": "Merchant ID" },
    { "key": "enableBadges",
      "title": "Show review badges",
      "type": "boolean" }
  ]
}

My integrationEnabled by Appbrew

API key••••••••••••

Merchant IDmeadow-goods

Show review badges

Commands and manifest from the Appbrew developer docs. Step 5’s form is drawn from that manifest.

How Appbrew promotes partners

Brands find you where they already look.

Studio: a merchant asks Milo to connect Judge.me reviews; Milo asks which draft theme should carry them, sets Judge.me up on a new draft copied from the live app, and says the code goes in once the merchant says yes

Milo already sets up four from chat

Firebase, Meta, GoKwik with KwikPass and Judge.me, on a draft, then it waits for the brand’s yes.

How Milo sets up integrations

Your listing in the Integration directory

See the directory

Partner dinners and a first look, every quarter

A small table of partners and the Appbrew team, and what’s next on the platform. Touch Grass once a year.

Partners on Appbrew

Built from the docs.

Partner story · LinkRunner

“Very time-saving. Focus on your products, rather than focusing on the app.”

“I just gave him the docs and said, ‘This is the SDK, install it.’”

Founding engineer, LinkRunner

From the docs aloneOne technology partner sent an 80%-done package with their first email.

FAQ

Short answers for partners.

Become a partner 

Do I need a React Native team?

Blocks are React components, written like any custom block in the host app, and a tracker is a TypeScript class. If your product is hosted, a WebView block can render it in the app first.

How does my integration reach a brand’s app?

Appbrew enables your package for merchant apps. The settings you declared in the manifest then appear in Studio, where the brand fills them in.

Does my package need an App Store release?

Only if it adds native modules. A pure-JS package ships with the next scheduled release of each app; a native one ships with a store release on the brand’s own accounts.

Can I publish from my laptop?

No. Your repo’s Release workflow publishes to Appbrew’s registry with Appbrew-held credentials, tags the release and refuses a version that already exists.

What happens when Appbrew ships a platform release?

You declare the platform versions your package supports. When Appbrew asks you to validate against a newer one, you bump the whole @gauntlet set in the sample app and re-run your flows.

Is there a public REST API?

No. Your integration runs inside the app as an npm package. For a web page opened in the app, there is the Web SDK.

Who do I talk to?

Start with the form on this page. Repos are provisioned by Appbrew, so nothing here is self-serve. Once your repo is set up, registry access and support come from your Appbrew contact.

Become a partner

Tell us what you’d build.

  1. 1ApplyYour product and your team’s GitHub usernames.
  2. 2Repo accessA host app repo, ready to run.
  3. 3Build and publishThe Partner quickstart, clone to publish.

Your product, in Appbrew apps.

Build one package. Appbrew enables it and lists it.