Repository navigation
General
Table of Contents
A Domo Apps Design includes all the code, assets, manifest, and HTML needed to display the app. It may contain a default mapping indicating a specific data source that can be used to power the design. Every design has a UUID that is, by definition, unique to itself.
A Domo App is an instance of a Design. An App may specify its own custom data source mapping to override that specified by the design. This could be used to have multiple instances of a Design, with each displaying data from a different data source. Each app also has its own UUID.
In order to keep Domo secure, protect data, and protect customer experience, all Domo Apps are rendered in their own iframe residing on their own subdomain. For example.
<iframe src="//85992d26-6d77-4c99-95e2-7284ecbbdcb0.domoapps.prod2.domo.com">
<!-- Design's index.html inserted here -->
</iframe>This is an example of an iframe that contains the Domo App with id 85992d26-6d77-4c99-95e2-7284ecbbdcb0.
When developing a Design, it can be helpful to load the URL from the iframe on its own. This way you can quickly refresh and see your changes without having to refresh all of Domo.
Since the design is running in its own subdomain, its assets are accessible from that same location. For example, if one design includes a lolcat.jpg in the base directory, it can be requested as would be done normally:
<img src="lolcat.jpg">This request would resolve out to the full path of:
https://85992d26-6d77-4c99-95e2-7284ecbbdcb0.domoapps.prod2.domo.com/lolcat.jpg
Some asset paths are reserved for special use.
-
/data- For [requesting mapped data](Requesting Data) -
/domo- (future) For requesting Domo data