-
Complexity vs Ease of Use
It’s interesting to speculate on how “professional” FCP-X will be, but here is the dilemma: at some point ease of use becomes inversely related to the complexity of the feature set.
It is 100% clear that Apple’s prime directive with FCP-X is to make it easy to use by people who only edit occasionally, and would be unlikely to ever master (i.e. feel comfortable with) a full-featured application.
One could envision Apple designing a contextual interface (similar to the Autodesk/discreet approach), where screen information changes depending on what task you happen to be performing. This does allow you to simplify the display at any point in time, but it is questionable whether this flattens the learning curve – if anything, it raises it.
But imagine that the contextual interface could be disabled for the occasional user, leaving a simple (if more limited) set of features. Did Apple take this approach?
My contention is that if this were the case, we would have seen more evidence at the NAB SuperMeet preview – unless Apple decided to leave this advanced functionality turned off for the preview. Highly unlikely for a show catering to professional editors, in my opinion, since this “switchable” advanced functionality would have to be considered a major new feature.
No, I’m afraid it is clear that Apple has simply cut out much of FCP’s advanced feature set. Obviously this is cheaper and easier than the “switched” contextual interface approach that might have allowed Apple to design something simple for the occasional user, while still offering advanced functionality for the professional.