How can I publish an Experience Builder app to ArcGIS Online from the Developer Edition?

[SayantaGhosh]

I have successfully installed the ArcGIS Experience Builder Developer Edition on my computer and logged in using my ArcGIS Online (AGOL) account via the client ID and redirect URL. I can create and preview apps locally without any issue.

However, when I try to "publish" an Experience Builder app, it only gets saved and hosted on localhost and doesn't appear in my ArcGIS Online content. My goal is to host the app or make it accessible through AGOL.

Is there a way to deploy the Experience Builder app from the Developer Edition so it reflects on my AGOL account, or is there a specific process to publish or host it on ArcGIS Online?

Any help or clarification on the correct deployment workflow would be greatly appreciated!

[JeffreyThompson2 · Accepted solution]

When using Developer Edition, it is your responsibility to host your completed application to a web server. There is no way to host it in ArcGIS Online. 

A possible workaround would be to host your application on a web server, then create a new Experience Builder project in your Online Portal. This new project would only contain a full-page Embed Widget containing your deployed application. This way your application could still be found in your Online content.

[TimWestern]

To tack onto what @JeffreyThompson2  is saying.  There is a publish function in dev edition, you might see a web experience appear in portal, but any custom widgets, I don't think the portal will know what to do with them.  For Enterprise if you have widgets hosted somewhere, you can create a linkage to add them and use them in an experience, but I think you have to rebuild the look of the dashboard and placement of even the outof box widgets when you do that.

(There is a migration tool, and by changing some IDs you can get part way there I think, but I don't think it can publish the custom code the way you are suggesting, think about it, if it were possible, that potentially could be a security issue as code written by anyone with permissions to publish could be placed in AGOL (or your local AGE instance))