Adobe Commerce App Builder Roadmap

Improve the experience of developing Adobe Commerce App Builder integrations in JetBrains IDEs.

Problems to address

Developer problem	Desired outcome
Understanding how events, action configuration, and handler code connect requires searching across files.	Navigate directly from an event or webhook to the action and code that handle it.
Broken references and missing configuration can take time to locate.	Identify the affected configuration and understand what needs fixing while editing.
It is difficult to determine why an event does not reach its handler.	Follow the integration flow and narrow down where the failure occurs.
Commerce environments and versions can support different capabilities.	Understand whether an integration is compatible with its target environment.
Reproducing payload and webhook failures involves several tools and manual steps.	Reproduce failures and verify integration behavior from the IDE.

First: Understand integration connections. Navigation between events, webhooks, actions, and handler code.
Next: Catch configuration mistakes earlier. Clear feedback for broken references and incompatible configuration.
Next: Make troubleshooting easier. Help developers trace event handling and understand environment differences.
Later: Simplify testing. Make integration failures easier to reproduce and verify.

Priorities are exploratory and will be refined through developer feedback.

Action input confusion: a historical report, now closed, illustrates the difficulty of understanding where action parameters originate.
Events not reaching a handler: a developer describes difficulty tracing delivery between Commerce and App Builder.
Commerce environment differences: a historical SaaS/PaaS incompatibility report illustrates the need for environment-aware guidance; it does not establish current endpoint availability.
Adobe's debugging workflow: documents the setup, payload invocation, and log inspection steps involved in troubleshooting.