Introduction

Want to list your Intuiface-based work on the Intuiface Marketplace? The Marketplace is a great platform for experience creators to get exposure.

This article reviews what you need to know.

NOTE: You must have an active Platform subscription (either Essential, Premier, or Enterprise) to list an experience in the Marketplace.

Submission and Review Process

1. Experience submission
   
   • Once you've built your experience in Intuiface, publish it and then open its information panel.
   • At the bottom of this information panel, click the Submit button in the "Submit Experience to Marketplace" section.
     
   • Complete and submit the "Experience Submission Form". Be sure to review the Experience Checklist before submitting your experience to avoid several rounds of reviews.
2. Experience review
   At this stage, we review the design, usability, content, and structure of the experience.
3. Experience approval/rejection
   Once we determined whether your experience is approved or rejected - after no more than two business days - you will receive a notification by email. If approved, your experience is automatically listed on the Intuiface Marketplace.

Experience Checklist

Your experience must meet all of these requirements to be approved for listing on the Intuiface Marketplace. Go through this list before submitting your experience for review.

Quality standards

We look for craftsmanship in Intuiface experiences that would otherwise require an investment of time or money to create. We look for working experiences with intuitive navigation, interaction, and overall good design. Do not submit a very simple experience with only one interaction element unless there is something extremely special about it. If you have a simple experience, consider making a multi-pack instead. Do not send us default experiences that require just a few clicks to create. Your submissions should be a reflection of your talent and skill.

Functionality

Things should work as much as possible out of the box. If there are unavoidable configuration steps to be performed by the user, such as defining a Twitter feed, these should be clearly documented in an Instructions scene to support user experience and ensure overall satisfaction. Instruction scenes should identify what needs to be preconfigured and, if relevant, link elements to supporting articles in the Intuiface Help Center. Make sure all triggers and actions in your experience are operational.

Usability

Interaction with your experience should be intuitive. Users must easily understand how to navigate from one scene to another and clearly identify which elements in your experience are interactive and which are not. For example, make sure you differentiate the pressed state for image buttons to provide visual feedback.
Make good use of the different asset states - free, static, pinnable - to ensure elements are only as interactive as you intended them to be.

Design

Even though "good" design is subjective, we expect quality design for submitted experiences. Experience layout should follow consistent spacing and should not appear cramped or cluttered. Text needs to be legible and should have proper spelling and grammar. (Paragraphs can use “lorem ipsum”). Images should not appear pixelated.

Organization in Composer

If you permit users to edit your experiences, ensure everything is well organized and appropriately named in Composer. Users must easily identify which elements are to be modified. If you are using hidden elements, lock them, making it easier for users to manipulate items on the scene in Edit Mode.

Performance

Be thoughtful about experience performance. Media content should be reasonably sized. Do not use a 4K background if your target screen's resolution is only Full HD.

If you are presenting multiple scenes or collections that reproduce a similar layout, use Headless CMS or Excel to store your content and feed that content into a template. Here is an example with Excel.

Content you do not hold the license to redistribute

You may not upload content that you did not create or are not legally licensed to redistribute. This includes images or videos ripped from other websites or content you purchased on stock photo and video websites. You also may not use paid fonts such as Helvetica or Proxima Nova as the font source is provided to the user in the project. Make sure the fonts you use in your experience are free (such as Google Fonts).

Never upload anything you did not create or are not legally allowed to redistribute. You are legally liable and can be sued by the owner of the content and by anyone who downloads and uses the experience.

Testing your experience

Before submitting an experience, ensure you test it thoroughly on all the platforms for which you claim to support. Do not submit an experience for a platform you have not tested. If, upon submission, we find broken triggers and actions or if the experience is performing poorly because of oversized media, we will reject it.

Submitting your experience

Use an explicit name for your experience so users can easily understand what it contains. Provide a clear summary and description of your experience. Also, choose full-screen screenshots of your experience that best represent your project.

We also encourage you to support your experiences with great supplementary material. You want to make a good impression, and you want your project to stand out from the crowd. You can also entice your users by linking to website material and/or YouTube/Vimeo videos to create interest among your audience. A short demonstration video usually makes a good first impression and clearly illustrates your experience.

Experience Support

You are not expected to provide support; experiences are posted to the Marketplace as-is. However, feel free to provide support information within your experience.