Skip to main content

Idea pipeline

1676 Ideas

Don't Clobber macOS default keybindingsIdea

Context: I come from a long background of using and developing for both Windows and macOS systems. I primarily use macOS for all tasks nowadays.Idea: Allow use of macOS’s native text editing keybindings rather than those defined by the Lucid web app. Restated: allow users to use text editing shortcuts that are indigenous to their system’s native keybindings.Detail:One of macOS’s strengths are enabling common methods of interactions even across different applications, whether they be Apple or otherwise. It’s a design paradigm that's baked pretty deeply into the OS and in frameworks used when creating applications. This design is surfaced in all modes of interaction: keyboard, trackpad, mouse, UI, and others.The focus of this request are text elements and keyboard shortcuts.For any text element web (input, textarea), provided a web application has not overridden them, I can expect to use emacs-style keybindings to navigate the text within that field. Examples:ctrl-a : place cursor at beginning of the line ctrl-e : place cursor at end of line ctrl-f : move cursor forward ctrl-b : move cursor backward ctrl-d : delete character in front of cursor ctrl-n : next line ctrl-p : previous lineThese basic ones are very helpful navigating / editing text, no matter what the app. An application need do nothing at all and it would benefit from having these keybindings work by default. That all changes when an application creates new keybindings.It’s clear that the UI designers at Lucid come or came from a Windows background as they have specifically enabled Windows-style keyboard while editing text:ctrl-a : select all ctrl-p : print dialog ctrl-b : bold ctrl-i : italic ctrl-u : underlineIt seems the Lucid app programmers specifically disabled ones all the ones I typically use, the ones I listed above. I imagine this was to create a common experience across all systems.Many programs nowadays allow users to select what set of keybindings they prefer using. It could be a user-selectable option.  

jimmy
jimmyLucid product team

How are you using Assisted Layout?Seeking Feedback

Hello Lucid community members! I am the product manager for the teams who developed our recent assisted layout feature.  Assisted layout makes it quick and easy to keep your canvas content organized. We do this by aligning shapes and automatically routing lines in a simplified grid-based layout: This feature is available through the ‘Assisted Layout’ button shown in the bottom right corner of all Lucid container.  You can also activate assisted layout by:The contextual menu in Lucidspark The properties panel in LucidchartThis feature also powers the ‘Tidy Up’ button you may have seen when making bulk selections on the canvas: We would love to hear how you are using assisted layout as part of your workflow, and the ways it can improve. GoalsUnderstand what tasks and jobs assisted layout has the greatest impact Learn when people choose to use assisted layout in their workflows Collect feedback on where assisted layout can improve to better meet your needs Some discussion starters Where assisted layout shines 🌎 I find assisted layout most helpful for [specific task] because..." [fill in the specific diagramming or brainstorming task you do most, and how this feature simplifies it] 🌎  "I usually switch to assisted layout at [this stage] of my workflow to…." [describe when in your process you move from messy ideas to organized structure, and why] 🌎 “I prefer using assisted layout over manual alignment specifically when I am working on..." [mention a specific activity where auto-alignment provides more value than manual tweaking] 🌎 Assisted layout has saved me the most time doing [tasks] because… [fill in which tasks this feature streamlines and why it’s valuable for you] 🌎  "The moment I realized assisted layout was a game-changer was when I had to [action] and..." [share a specific 'aha' moment where the tool changed how you approach working] 🌎  "Assisted layout makes [task] so much easier by..." [explain the specific feature capability that improves your work.  Example: line routing, spacing, dropzones] 🌎 “As a [job title] I use assisted layout all the time to…” [describe how the tool supports your specific professional role and responsibilities] Where assisted layout can improve 🌎 "I find myself turning assisted layout off when I need to [action] because..." [identify the specific action or situation that the assisted layout struggles to handle] 🌎 "I struggle to use this feature with [types of content or tasks] because….” [mention specific shapes or jobs types that don't seem to fit well within the current grid logic] 🌎 "It is difficult to find the assisted layout tool because [reasons]."[provide feedback on the UI placement or the onboarding experience] 🌎 "I was confused when I tried to [task] and realized assisted layout didn't support..." [outline any missing capabilities, like cell spanning or nesting, that you expected to see] 🌎 "I tried using the tool for [use case], but the organization didn't look right because..." [explain how assisted layout failed to meet your aesthetic needs] 🌎 "I would use assisted layout more often if...." [suggest any high-priority changes or requests that would make the tool more essential for you] 🌎 "I wish the layout engine was smarter about [feature] so I wouldn't have to manually..." [describe a specific adjustment you still have to make by hand after the tool runs]