​
About product types

Many stores want to provide different asset types in their marketplace. Instead of showing all assets in the same way, we support offering multiple product types, where each type can have different properties, different card appearances, different layouts and different call to action.

​
Example use cases

  • Apps
  • Integrations
  • Games
  • Game characters
  • Plugins
  • Components
  • Widgets
  • Assets
  • Templates
  • Workflows
  • Sound files
This feature although powerful, isn’t necessary, so you could create one product type for all asset types. This is how most stores online work, one template for all products. It’s just a little limiting, and will require a more generic language.

​
Dynamic properties

You decide what properties to collect on products of that type. You can also set what properties are required, what are editabl by merchants, and what are searchable. Properties can be
  • Text
  • HTML
  • Image
  • Video
  • Media (image or video)
  • Link
  • An option from a list
A property can also be an array of values of the same type. For instance, a gallery of images is an array of type image.

​
Card appearance

Every product type has its own card appearance. This is using the same layout building blocks that you can read about in the Layout section. You can also have multiple card appearances for advanced use cases.

​
Cards actions

Cards are buttons. We support a variety of actions:
  • Product page
  • External link
  • Callback
  • Purchase
  • Link to a Store page
Setting any action that isn’t a Product page or Purchase means your users won’t be able to complete a managed purchase on SideDish. This is still a desired behavior for ads, or for redirects to parts of your own app.

​
Page layout

Every product type can set its page layout. This is using the same layout building blocks that you can read about in the Layout section. Products don’t necessarily have a page (You can have a product that is an external link). You can also have multiple page layouts for advanced use cases.