InVision Studio Changelog

What's new in InVision Studio 1.12.0

Apr 9, 2019
  • Starting today, you can browse the Studio App Store Beta to find 50+ apps and assets that help you do what you do best: create exceptional customer experiences.
  • Now you can configure export settings for layers within a component, including nested components.
  • When editing a component, Studio now displays more relevant information—like the component name and the library name—rather than showing the navigation for pages and libraries, like it did previously.

New in InVision Studio 1.11.0 (Apr 8, 2019)

  • What's improved?
  • Center yourself: To center the canvas view on a specific layer, now you can double click the layer's icon in the layer panel.
  • SVG exports: When exporting a layer that contains a shadow within a group, you'll probably notice Studio now produces a more accurate SVG.
  • The fancy type: Next time you're touching up a text layer, click the new More button (three dots, stacked vertically) in the inspector panel to access the Advanced Options for typography settings.
  • Pssst! Don't forget After you've finished viewing a Studio library, you'll notice a subtle reminder about the last page you were working on.
  • What's fixed?
  • Precisely!: When working with shadows or inner shadows, now you can use decimal values in the X Y, and Blur fields. Previously. Studio would errantly round decimal values in these fields.
  • Lessen the load: You should no longer run into the memory management issues related to modals and the color picker. Those issues were sometimes causing Studio to use more system memory than necessary over time.
  • One of a kind: When multiple component layers with export options were selected, Studio could end up adding some layers more than once to the selection, which led to the Inspector panel crashing. Studio will now add each layer to the selection once, and only once.
  • The whole story: The tooltips for the layout and grid menu will be much more useful now that you can actually see the text.
  • Number inputs You might notice that number-based input fields now behave