Commentary

Would More Megapixels Make The iPhone's Camera Worse?

There's an interesting article over at Ars Technica about how boosting the number of megapixels in the iPhone's camera would lead to worse picture quality. The author explores the things that really matter: autofocus and lens quality. For the most part, I agree with his analysis, but Apple still could have improved the camera.

There's an interesting article over at Ars Technica about how boosting the number of megapixels in the iPhone's camera would lead to worse picture quality. The author explores the things that really matter: autofocus and lens quality. For the most part, I agree with his analysis, but Apple still could have improved the camera.Last week I wrote a short piece titled "Five Reasons NOT To Buy The 3G iPhone." Thank you to the many, many people who agreed and/or disagreed with the article and, further, who took the time to e-mail me about the story. One of the reasons I listed was that Apple took no steps to improve the camera.

Many of you assumed I meant for Apple to boost the number of megapixels the iPhone's camera has. While that would have been a nice gesture, it is far from the only thing that would improve the quality of images taken with the iPhone.


More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

On megapixels, Ars says:

If Apple were to use a higher resolution image sensor with the same lens, the pictures wouldn't be any sharper -- and 2MP sharpness in a 5MP camera is just not acceptable. The other option would be to reduce the size of the lens opening, but that way, the amount of light that reaches the sensor is reduced and the iPhone would have an even harder time taking decent photos under dim lighting. The other problem is that the more megapixels that are crammed in the same size sensor, the smaller those pixels get. Since individual pixels are gathering less light, many will be "underexposed" and produce a lot more noise. That's the last thing that the iPhone's camera needs.

He's absolutely right. Simply boosting the number of megapixels would result in images of poorer quality. If Apple really wanted to improve the camera, it would have done a few things: add autofocus, improve the lens quality, add a flash, and add better camera software.

The first three would definitely result in a phone with a higher price tag, and possibly even an altered size/shape. Autofocus camera chips tend to be a bit thicker than fixed-focus lenses. Depending on how Apple engineered the guts of the device, this could have resulted in a bulge, or other change in the shape of the iPhone. My guess is Apple didn't want to take that route.

Better software, on the other hand, is something Apple could easily have done, and without impacting the price of the iPhone too much. As it is, the iPhone has zero ability to configure or change the settings for the camera. All you can do is point, and shoot. Sure, this ease-of-use factor is classic Apple thinking at work, but many (myself included) like to be able to make adjustments such as dial down the resolution, have some control over image size, crop the image, check for the right white balance setting, and so on. Apple must be assuming that iPhone users will use iPhoto (other other photo-editing software) to make those adjustments after the fact. The truth is, sometimes it would be nice to perform those actions on the phone, because you're going to send the photo to someone else directly from the phone.

As I mentioned in my article last week, I am hoping a third-party developer steps up to the plate and delivers software to do just this.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links