App Builder Kit for Developers

Adobe believes that strong partnerships result in powerful results. Whether you are a Solution Implementer (SI), or an Independent Software Vendor (ISV) who wants to build App Builder apps, Adobe is committed to supporting you at every step—from onboarding and sandbox access to app development and distribution.

Through the Technology Partner Program (TPP), you receive access to the tools and resources you need for application development. Adobe is committed to helping you navigate challenges and complete your apps successfully.

Together with Adobe, you can create solutions that deliver real value to you, your customers, and the broader Adobe ecosystem.

In this page, you will find:

A starter kit to help you set up your account and sandboxes.
Guidance to building your app.
Instructions for submission and distribution.

Requirements to access App Builder

Access to App Builder requires meeting two conditions: having the required membership level and account type. These will provide access to our sandboxes, allowing you to build and publish an application.

Membership requirements - To build and publish an application, you must have a Silver tier membership or higher, which gives you sandbox access and the possibility to publish on the Adobe Exchange Marketplace.
Account requirements - A TPP account is required to access all sandboxes (App Builder, the Adobe Commerce as a Cloud Service SaaS sandbox, and the PaaS sandbox), whether you are an SI or ISV.

If you are a Solution Partner Program (SPP) partner, you will need to create a TPP account to access these environments.

How to set up your account

Follow these steps to set up your TPP account.

Step 1: Request a TPP account

Go to the Register to the Adobe Technology Partner Program page and create a Silver-level (or higher) TPP account. You will be asked to provide a corporate email address and company website as part of the registration process. How to register in the Adobe Technology Partner Program provides additional information about this process.

Adobe Support will create an IMS org for you, either proactively or after you request sandbox access in Step 3. Each registrant must use an Adobe ID.

After you join, Adobe will assign an ISV, a TPP organization, and an App Builder sandbox associated to that organization.

A Silver membership (or higher) within a TPP account is needed to access App Builder, or public app listing.

Step 2: Adobe reviews your request

Adobe will review your application and process your membership order. Within a few days, you'll receive an email notification confirming whether your membership has been approved or rejected because additional information is required. If further details are needed, Adobe will provide guidance on next steps.

Step 3: Request sandbox access

After your Silver membership is processed, you can request sandbox access, which will be provisioned within five days of your request.

App Builder Sandbox - Newly provisioned TPP organizations are automatically associated with a TPP organization. Older organizations without the necessary permissions should request access to all three sandboxes—App Builder, PaaS, and ACCS/SaaS—through TPP Support using a single ticket.
Commerce PaaS Sandbox – Account Managers should request both Composer entitlements for Adobe Commerce EE/B2B Access and PaaS sandbox through TPP Support.
Commerce SaaS Sandbox - File a ticket to TPP Support. Once received, you can add additional users that will need sandbox access in your Admin Console. See Step 6 to manually assign users as Admins or Developers.

You can create a ticket to check the status of your organization, or sandbox enablement, specifying the name of your assigned TPP organization.

Step 4: Log into your Adobe IMS organization

Verify that you are logged into your IMS organization by checking the top-right corner of the Adobe Experience Cloud or Developer Console. If it displays your organization name, you are ready to use App Builder. If it shows an email address, you are signed into a personal account instead of your IMS organization.

Step 5: Create a project from template

Navigate to the Developer Console to access App Builder.
Select Create Project from template.
Follow the steps described in the Create your First App Builder Application topic.

Step 6: Manage your team

The Admin Console is your central hub for managing access to Adobe Experience Cloud products. It enables administrators to control services, user access, product entitlements, and roles across the organization.

As an IMS organization admin, you have full control to add users, assign roles, and manage access through the Admin Console.

To manage team members who need to submit or manage App Builder listings, ensure their Adobe ID email is added to your IMS organization.

Use the following workflow to manage your teams:

Access the Admin Console by signing in with your Admin credentials.
Add users to your IMS Organization.
Assign product entitlements and roles
Ensure each user has the correct permissions for Adobe Experience Cloud products and App Builder tasks.

For detailed instructions, see Adobe Admin Console Users.

Only accounts with Developer or Admin access can manage App Builder listings.

Integrations

After partners get sandbox access, the Adobe Commerce engineering team will ask developers to extend the integration starter kit when getting started with App Builder development.

How to build an app

Get started by learning more about building an app.
Install the Adobe Commerce integration starter kit.
Read the App Submission guidelines.
Review the developer guides for out-of-process apps and app distribution.

Support resources:

Common issues.
Experience League forum.
Slack support channel in the Magento Open Source Workspace: #app-builder-community

How to package your app

Package and configure the app overview.
Internal publishing: Publish within the partner's organization.
External publishing: Publish on the Adobe Exchange Marketplace. Read the following distribution section.

Distribution

Here are the distribution steps with use case for Commerce SIs and ISVs.

Step 1: Create an App Builder listing

Sign into Developer Distribution (DD) and confirm that your approved IMS organization appears in the upper-right organization switcher. If the organization name looks like your email address, you are not in the TPP organization and will encounter an error when attempting to create a listing.
Create a public profile before submitting your first App Builder listing.
Create an App Builder listing using the zip file you created when building your App Builder app. After you create a listing, you can see it on the Listing Overview page.

Step 2: Submit a listing for review

Review the Adobe Exchange Marketplace publishing requirements to ensure your submission meets the requirements and to prevent delays in the approval of your listing.
Adobe brand and code reviewers will review the App Builder listing and send an email confirmation once it is approved. If your submission is incomplete, Adobe will provide feedback to help you address the issues. You can also check the status on your page, which will display an Approved or Published status.

Variations

ISVs can publish the listing under their name, if they have an Adobe ID associated with a TPP organization.

SIs can:

Publish the listing under their name if they have joined the Technology Partner Program using their Adobe ID associated with a TPP organization.
Publish on behalf of an ISV if they have been added to the TPP organization of the ISV. To confirm approval, submit a TPP Support ticket providing evidence that the ISV authorizes the SI to publish on their behalf. and Adobe will then share the organization name with the SI user to ensure that they sign in to the Developer Distribution (DD) under the correct organization.

Any user with an Adobe ID associated with the TPP publishing organization can submit, manage, and retract an App Builder Listing in Developer Distribution.

Users updating or revising the App Builder App itself require Commerce and App Builder sandboxes in their organization.