You can use Shopify App Bridge to embed apps and channels directly into the Shopify admin, Shopify Mobile, and Shopify POS. Shopify App Bridge helps to reduce your development time by accessing native Shopify features across different platforms, and makes sure that the user experience is consistent wherever merchants are using your app.
Shopify App Bridge is currently being released as an update to all current consumers of the Embedded App SDK. Since it’s backwards compatible, you don't need to update your existing apps for them to support Shopify App Bridge.
You can install Shopify App Bridge by using Yarn:
yarn add @shopify/app-bridge
Set up your app
In the following example, you need to store
shopOrigin during the authentication process and then retrieve it for the code to work properly. To learn more about this process, see Getting and storing the shop origin.
Import the library from the
@shopify/app-bridge package and provide a configuration:
Shopify App Bridge introduces the concept of actions. An action provides a way for applications and hosts to trigger events with a statically-typed payload.
To learn more about the supported actions, see the actions source folder.
Once the app is set up, you can access additional details and the state of the app at
any time by making async call
You can also use a shorthand to retrieve nested properties by passing in a
query when calling
getState(query), for example:
Shopify App Bridge can be extended with hooks, which run when actions are dispatched and updated. Hooks are middleware that can modify or cancel actions.
To learn more about hooks, see the hooks source code.
Development & Debugging
Shopify App Bridge is shipped with a development build which includes the validation middleware in order to provide helpful information during development.
If you're consuming App Bridge from a CDN or using the UMD build, simply include the development version:
umd/index.development.js instead of
When consumed as JS Modules, development/production build is dynamically selected based on the
NODE_ENV variable. Development build is used when
Please note that the development build is not intended for production use, as the resulting file size is significantly larger due to the validator being present.
yarn start- Start a development server.
yarn clean- Remove any artifacts produced by the
yarn lint- Run the source linter.
yarn check- Run the TypeScript type checker.
Running the tests
yarn test- Run the tests.
yarn test:watch- Run the tests in watch mode and auto-rerun on changes.
yarn test:coverage- Run the tests and generate a coverage report.
To enable automatic prettier formatting, copy or link the pre-commit script to
.git/hooks/pre-commit and make sure that it's executable.
Please follow a standardized commit message format when contributing to this repo: https://www.conventionalcommits.org/en/v1.0.0-beta.2/