A regular criticism of Apple is that the company tends to push aesthetics over functionality. I’ve never entirely agreed with this thinking, believing that—for the most part—Apple advocates usability over everything else, and aesthetics form a major part of how usable something is.

However, two recent reports of upcoming Apple products concern me, since it seems Apple is in some cases sacrificing usability for platform consistency.

The first case is in the iPad, where Steve Jobs has reportedly confirmed via email (9To5Mac) that the iPad screen-rotation lock will become a mute button as of iOS 4.2. This matches the functionality on the iPhone and iPod touch, which is presumably why Apple has made the change. However, it doesn’t seem to take into account how people use the various devices; a rotation lock is far more important on the iPad, since the accelerometer is so sensitive. The iPad is also less likely to be used in scenarios where a mute button will be required, unlike the iPhone and iPod touch.

What grates for me in this scenario is that when asked “Are you planning to make that a changeable option?”, Jobs responded “Nope”. In other words, Apple is changing the functionality of a major hardware component of its device, without providing users with a means to revert, despite the button’s functionality being controlled by software. That there won’t be an option buried in the Settings app suggests Apple cares more for platform consistency than anything else. (Note: I’m aware iOS 4.1+ provides a software-based orientation lock by swiping the apps tray, but this is sub-optimal. Not only is this control awkward to access—and will be more so on the larger iPad—but many users won’t even know it exists.)

MacRumors today reports on some equally concerning aspects of Lion (the next version of Mac OS X). According to a reader, the scrollbars are as per iOS (appearing only when needed and fading when they aren’t). This is idiotic from a user-experience standpoint. One of the biggest issues with iOS is that while it’s mostly intuitive, there’s a lot of ‘mystery meat’ navigation. Users have to ‘discover’ things far too often, since navigation and UI components are regularly hidden. Visible scrollbars provide an indication of a document’s size and your location within it; only showing scrollbars temporarily does not enhance usability—it degrades it; it’s also alien to a desktop operating system.

Both these things point to Apple wanting to merge concepts in iOS and Mac OS X at all costs. Some cross-pollination is undoubtedly a good idea—Mac OS X having system-wise auto-save/app-resumption will be a major productivity boost if implemented properly; but Apple must also remember that what works on one system won’t necessarily work on the other—and it should also realise that some things really don’t work from a usability standpoint on iOS as it is, and so welding such concepts to Mac OS X isn’t a great idea.