Skip to main content

Every time I look for a component using the `option + 2` shortcut and start typing I expect the search input to be focused but it takes a second. By the time I’ve searched for a “Note” component I’ve been moved across my page to a seemingly random frame and selected the text tool but haven’t searched for any components. Wouldn’t it make sense to render the search input immediately rather than waiting for some kind of API response?

It’s massively frustrating, I hate the N for next frame shortcut anyway, but when I accidentally hit it when a text input should have been focused it’s a nightmare.

The component search issue is by far the worst, but I run into issues where I think I have a text frame selected or a property input focused and end up hitting random shortcuts instead of typing multiple times per day. Please take a look at this, the ergonomics are pretty rough in this regard, especially when you’re trying to work quickly and the app doesn’t respond to shortcuts as expected.

Be the first to reply!