Commentary

iPhone Dead After 40 Minutes?

That's what John C. Dvorak claims in his podcast, anyway. Citing an internal Cingular product tester, the iPhone only provides for 40 minutes of talk time and the interface crashes all the time. I taste some sour apples here.

That's what John C. Dvorak claims in his podcast, anyway. Citing an internal Cingular product tester, the iPhone only provides for 40 minutes of talk time and the interface crashes all the time. I taste some sour apples here.Just a week after Dvorak bashed Apple and said it should write the iPhone off as a proof-of-design project, he's at it again. This time he says an internal mole at Cingular provided him with secret information about the usability of Apple's forthcoming venture into new technology.

In Dvorak's podcast, he said "a guy at Cingular who's testing the product" gave him the skinny. According to the questionable source, the iPhone's battery is not removable, talk time lasts a mere 40 minutes and the user interface makes mistakes all the time. What those mistakes are remain a mystery.


More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

The validity of this information is flimsy at best. I, for one, can't believe that Apple wouldn't have its UI ducks mostly in a row a mere 2 months before launch. The battery issue is slightly more believable, though who knows if the production battery was actually supplied to the tester.

Either way, I fear rumors from fanboys and Apple haters alike will continue to mount and swirl around the closer we get to the launch date.


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