Like pros?
Well in many circles, it's Amateurs that lead the way since they have few resources and want "best" results. Examples: Early computing and Radio communication.
It's my view that NLE are stuffed with features that clutter the screen. If you use a Keyboard/Controller, you remember where the "Splice" key is, because there are two actions involved "visual" and "touch" - this is not the same when using the screen.
When the program fires up just how many options does the screen need to present? four, maybe five if you include "Shut this program down, I made a mistake"
So why are users presented with a whole screen and no obvious starting point?
By making the NLE easy to navigate at every stage, Users will sing LWKS praises and you sell more controllers.
However, I do think there is an issue over HD import, as it seems that only the Pro-version supports .m2ts - and as I've said before a few hundred piunds will buy a stills camera capable of doing video in HD - far better than those CHS camcordrs costing a fortune only (say) ten+ years ago, when NLE's startd, once computers got "useful".
I'm NOT suggestng LWKS should have any fewer facilities, just that the Workflow should determine what's presented on the screen. Pro's may have different objectives, but ease of use is probably up there too.
Most programs concentrate on the huge number of "themes", - "transitions" - ... I suspect this is to boost the "Features Rating" - yet being able to produce your first video at the speed of light (geddit?) would be something other programs couldn't achieve.
Here's a suggestion for your programmers . . . . USB-number-pads are cheap, how about a limited Editor's Keyboard option? You can sell sticky lables to convert one to have 17 funtions (more using CNTL), aimed at the beginner - so it will import clips, stills, music, each from a defined source (Drive/folder/etc/).
Post #28975 concerns frame-rates: unfortunately these are a mess World-wide due to Analogue days. When importing (right at the start of a new project) the user should be able to set all the Properties and maybe ask LWKS to alert them to any media that falls outside. This would stop the creation of a Pig's Ear when too late, the Properties are found wanting.
This should include all imports, including Text which is generated outside LWKS.
Good Hunting.