Publishing Apps

Publishing an app in DynaMaker is straightforward. In this tutorial you learn the basics.

Use any app you have built that already has a working component (and ideally configurator), no matter how polished it is. This tutorial does not require coding, only a few clicks.

You complete two steps:

1. Publish online
2. Understand publishment

1. Publish Online

When you are done with your components and/or configurator, you can then Publish online.
Taking Tutorial 8 as example, click Publish Now:

tip

You can also publish via Publish > Publish to web:

A. Application Setup

In the first step of publishing your app you find:

• On the left:
  • Application Template > Automatic to generate the UI based on Visualization and Configurator.
  • Visualization > ASSEMBLY.Component to visualize the geometry of the assembly.
  • Configurator > ASSEMBLY.generateConfigurator to use this configurator for the UI.
• On the right:
  • the interactive preview of your app with the selected visualization and configurator.

• Click Next to go to Subscription.

B. Subscription

In order to publish an app you would need a subscription, which has to be done once for the first publishment. For this simply Assign the subscription to the app:

note

No subscription yet? Don't worry, you can keep reading this tutorial to see the workflow. Otherwise:

• if indecisive Request Free Trial.
• or purchase a new subscription via Go to Checkout.

tip

You can inspect your subscriptions any time at the top in Standard (ow whichever subscription you currently have) or via Publish to web > Manage Subscriptions.

C. Publish

For now click Publish to test:

tip

You can reopen your Test site anytime via Publish to web > Test site.

Publishing an app will generate a URL like: https://deployed.dynamaker.com/applications/test/qSZW2gJqeWB/, which can be used as it is or embedded in a website (iframe) nicely like the following:

Then once you have tested your app and fixed any possible bugs, it's time to publish to production which will be the environment used by the end-users.

tip

So what's the difference between Test and Production?

• Test is meant for testing new experimental features and changes.
• Production is meant for the end user, with all valid configurations.

Notice the difference in the URL too:

• Test: https://deployed.dynamaker.com/applications/test/qSZW2gJqeWB/
• Production: https://deployed.dynamaker.com/applications/qSZW2gJqeWB/

2. Understand Publishment

Your application can exist in three environments:

• Editors: what you as an engineer work with continuously, and what the user never sees.
• Test site: published app meant to show experimental changes, typically for user testing.
• Production site: published (error-free) app meant to be used by the user, it must be polished.

The typical workflow of publishing an app (see picture above) is:

1. Building App: Engineer builds the app based on requirements (editors v1).
2. Implementation: Engineer adds the feature (editors v1 → v2).
3. Internal Testing: publish to the Test site (test v1) and share the URL with e.g. Sales for feedback.
4. Bug Fixing & Improvements: if Sales reports issues, engineer fixes them, improves code (editors v2 → v3 → v4), and republishes to Test site (test v2) for re-review.
5. Approval & Release: once approved, publish to Production site (prod v1) and give Sales the customer-ready link.
6. Next Cycle: Sales gathers new feature requests while customers use the current version; engineer works on them in editors (v4 → v5), then repeats the cycle.

---

Do you want to create your own User Interface with buttons, extra configurators, tabs and more functionalities? Learn the basics in the next tutorial Custom UI.