Jobs likes to claim that the iPhone can deliver "the real web," and it certainly sounds like the browser itself is quite powerful, but there are several problems here:
1) The iPhone has a maximum screen width (when held in landscape mode) of 480 pixels. The majority of web sites are optimized for an 800-pixel-wide screen. The iPhone doesn't seem to reformat pages to fit the screen (i.e., rescale graphics and wrap text). So that means that with the iPhone, you're either going to be looking at a "10 mile view" of a web page where you can see the entire width of the page but can't read the text, or you'll zoom in to read text and need to scroll horizontally. Jobs touts this as some sort of innovation. Correct me if I'm wrong, but didn't many early (and even later) web browsers for the Palm OS and PPC work this way? Most people (and the companies behind them) decided it sucked and changed course to instead reformat web pages to fit onto the smaller screen.
2) Even if the iPhone had an 800-pixel-wide screen, the only time it could deliver on its promise to provide a "desktop-quality" web browsing experience would be when you were connected via WiFi. Well, this is a phone primarily, not an internet tablet, and much of the time you're going to need to connect to the web via the cell carrier's data network. In this case, we're talking EDGE, which will be exceptionally painful. This pain is only increased because of point #1.
Sorry, but you can't change physics. The phone lacks the minimum desktop resolution width to deliver a readable no-horizontal-scrolling-required web page, and the data network it's tied to lacks the speed required to deliver these web pages in an acceptable timeframe. IMO, the current Treo, WM, and Symbian S60 browsers have the better approach. If a phone comes out with an 800-pixel-wide screen, I would agree that offering a full-size-view would make sense, but even then it should offer some sort of "fast" view which attempts to reduce page retrieval times when accessing the web when using a slower cell data connection.
Thoughts?
1) The iPhone has a maximum screen width (when held in landscape mode) of 480 pixels. The majority of web sites are optimized for an 800-pixel-wide screen. The iPhone doesn't seem to reformat pages to fit the screen (i.e., rescale graphics and wrap text). So that means that with the iPhone, you're either going to be looking at a "10 mile view" of a web page where you can see the entire width of the page but can't read the text, or you'll zoom in to read text and need to scroll horizontally. Jobs touts this as some sort of innovation. Correct me if I'm wrong, but didn't many early (and even later) web browsers for the Palm OS and PPC work this way? Most people (and the companies behind them) decided it sucked and changed course to instead reformat web pages to fit onto the smaller screen.
2) Even if the iPhone had an 800-pixel-wide screen, the only time it could deliver on its promise to provide a "desktop-quality" web browsing experience would be when you were connected via WiFi. Well, this is a phone primarily, not an internet tablet, and much of the time you're going to need to connect to the web via the cell carrier's data network. In this case, we're talking EDGE, which will be exceptionally painful. This pain is only increased because of point #1.
Sorry, but you can't change physics. The phone lacks the minimum desktop resolution width to deliver a readable no-horizontal-scrolling-required web page, and the data network it's tied to lacks the speed required to deliver these web pages in an acceptable timeframe. IMO, the current Treo, WM, and Symbian S60 browsers have the better approach. If a phone comes out with an 800-pixel-wide screen, I would agree that offering a full-size-view would make sense, but even then it should offer some sort of "fast" view which attempts to reduce page retrieval times when accessing the web when using a slower cell data connection.
Thoughts?