Our support site has moved to https://support.intuiface.com

Before you start, select the best Experience structure


    Because of its structure and content, an experience may perform poorly even on high-end devices. Choosing a good architectural structure will boost your productivity, but also the rendering/interaction smoothness of your IntuiFace Experience.
    This article will try to address most common conception mistakes of IntuiFace Experience creators.

    Think about Structure before Design

    A common mistake is to add content and multiply the same action to achieve only one show/hide mechanism. We have noticed many situations in which projects became very hard to edit because of duplicated Actions.

    • Try to keep repetitive actions at a minimum.

    The following image illustrates a bad approach, where the actions are unnecessarily duplicated:

    Wrong_Aproach.jpg

    The following image shows a better approach by using only One action.
    Notice all the elements are nested in a Group Collection which is the target of the action :

    Good_Aproach.jpg

    Another useful approach is to Bind one asses's "Visible" property to another's, then use Triggers and Actions to Show/Hide only the main asset.

    visibility-binding.jpg

    All scenarios will provide the same end-user experience, but the second and third ones are better in terms of Experience management and performances.

    For more details about Performances General Tips you can read the following Article

    Use Excel to filter the content

    INFO : For more details about using an Excel Based approach read this Article

    Excel can be used as a data source for your content. You can simplify your project's structure by building a template in Composer and link it to Excel with the help of Bindings.

    Your experience's content will be filtered and it will display only relevant information. This approach will help not only to achieve an easy data management, but it will also speed up your project’s response times making it more fluid.

    You can have only one scene that will change data dynamically based on the Excel entries. Data management will become more easy with this approach as you will only have to edit the Excel file not the experience.

    Spread your content across multiple Scenes

    If you have overwhelming amount of content, avoid using it on the same Scene. Spreading your content on multiple Scenes will help you organize your Experience and will give you a better control over it's content.

    To easily manage the menu buttons of your project,or specific content that needs to be placed and look the same on multiple scenes, we recommend you to use a Property to Property Binding.

    By using Bindings, you can create a Content Management system directly in your Experience. Whatever you will modify on the Master scene will also be reflected on other Scenes.

    Other performance enhancement tips


    • Performances of 3D models can be highly impacted by the GPU card.

    • Carousel, among other assets, depends upon the 3D capabilities of your computer. 3D capabilities are handled by the GPU (graphics card) of your computer.

    • "Show item shadows" property of Carousel has a performance impact on low-end Graphic Cards. Disabling this option might smooth-en things up, however if you encounter latency using Carousel, you should consider upgrading the Graphics card of your computer.

    CarouselItemShadowsproperty.jpg

    • IntuiFace Player needs less resources than Composer, for a detailed list of software and hardware requirements click here