When Apple announced the Full Screen feature in Lion I was quite skeptical of it. I really didn’t see the value of it from what I read. Of course, once Lion shipped and I gave Full Screen a try, I love it. It’s not just that it provides a distraction-free workspace, but when I use gestures to swipe between apps, I just feel more productive; much more so than using the application switcher, Mission Control or switching apps with the Dock icons.
Unfortunately the one feature that would make Full Screen much more valuable to me, and one that should be painfully obvious to Apple, is missing. The ability to set Full Screen as the preferred viewing method in the preferences would be a killer option.
Apple being Apple, if they were to implement this feature, they would probably put it in the System Settings and it would be an “all-or-nothing” option. But to me, that option would be a different devil in the same hell.
Putting the option in an individual application’s preferences won’t work, because we would be reliant upon the individual app developer to actually code this feature into their apps; and we simply can’t expect every developer to support this feature, at least not yet. But here’s an idea…
Apple is missing one killer option with OS X’s Full Screen feature
When Apple announced the Full Screen feature in Lion I was quite skeptical of it. I really didn’t see the value of it from what I read. Of course, once Lion shipped and I gave Full Screen a try, I love it. It’s not just that it provides a distraction-free workspace, but when I use gestures to swipe between apps, I just feel more productive; much more so than using the application switcher, Mission Control or switching apps with the Dock icons.
Unfortunately the one feature that would make Full Screen much more valuable to me, and one that should be painfully obvious to Apple, is missing. The ability to set Full Screen as the preferred viewing method in the preferences would be a killer option.
Putting the option in an individual application’s preferences won’t work, because we would be reliant upon the individual app developer to actually code this feature into their apps; and we simply can’t expect every developer to support this feature, at least not yet. But here’s an idea…