تطوير Adobe App Builder

Frequently asked

Questions we get from people about to book.

When should I use Adobe App Builder instead of a Magento module?

When the workflow is event-driven, scales independently of the storefront, or needs to integrate with multiple external systems through Adobe Event Mesh. Catalogue rendering, checkout flows and most customer-facing UI stay in the monolith.

Do we need an Adobe Commerce licence?

App Builder works against Adobe Commerce primarily. Some Magento Open Source workflows can be wired up through self-hosted event mesh equivalents, but you need to confirm licensing for the workspaces themselves.

How do you handle deployment to multiple environments?

Three workspaces by default: dev, stage and prod. CI pipeline pushes to dev on every PR merge, promotes to stage on tag, and prod on manual approval. We set up the pipeline as part of the engagement.

Can the app be published to the Adobe Marketplace?

Yes, with separate certification time. We can build to marketplace publication standards if you tell us at discovery; the QA pass is more thorough and adds about 2 weeks.

What about cold starts?

Adobe IO Runtime actions have cold-start latency in the 200-800ms range. Customer-facing synchronous flows that need sub-100ms response should stay in the monolith. Asynchronous and event-driven workflows are fine.