Shaun

My feedback

  1. 793 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    An error occurred while saving the comment
    Shaun commented  · 

    This is a huge problem. I regularly create components like mega menus, with open and closed states. Within those I have buttons which are also components (because I want hover states). Once those buttons are made components you lose the ability to make it's click event change the parent state.

    Component without this are pretty useless in a working prototype.

  2. 42 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    I’m keeping this one open, but a quick way for your client to share exactly what screen they want to talk about is to send you the URL they have in their browser when they’re looking at the prototype. Because we have deep linking, the URL will bring you right to that artboard.

    Shaun supported this idea  · 
    An error occurred while saving the comment
    Shaun commented  · 

    If we could have a grid view of pages like Invision, it's much easier for clients to nagivate. Currently they have to cycle through pages one by one, including ones only meant to be overlays etc. Also, we need to be able to omit certain art-boards from the prototype page view, but still keep them if they are being used as overlays etc.

  3. 375 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Shaun supported this idea  · 

Feedback and Knowledge Base