Commentary

Alexander Wolfe
 

Google's Android Frenzy Hides Mobile's Dirty Little Secret

There's one important point that's been lost amid all the chatter surrounding Google's non-announcement the other day of its vaporous GPhone, and its actual disclosure that it'll soon be releasing a phone-software development platform. It's this: mobile apps aren't the issue. It's the (slow) networks, stupid.

There's one important point that's been lost amid all the chatter surrounding Google's non-announcement the other day of its vaporous GPhone, and its actual disclosure that it'll soon be releasing a phone-software development platform. It's this: mobile apps aren't the issue. It's the (slow) networks, stupid.Despite the fact that Steve Jobs is tightly controlling all the apps which run on the iPhone, apps aren't hard to get. Not for the tightly wound iPhone, nor for open platforms like Nokia's Symbian-based phones. (Indeed, Nokia is openly touting its openness as an antidote to Apple's closed (figuratively and literally) approach.

Sure, in some cases there are apps which aren't as widely available, or for which options aren't as broad, as users would like (As a happy Blackberry user, I'm thinking here of instant messaging on these devices, which in some cases is available for the phone but not supported by the mobile service provider.)


More Global CIO Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Think about it: if you're a smartphone user, the biggest problem isn't you model's feature set, it's the fact that you probably avoid opening your browser unless it's absolutely necessary because mobile browsing is not a fun experience.

Moreover, the reason mobile browsing isn't because you can't search Google properly. (Indeed, Google is one of the few sites which works nicely when accessed from a smartphone.) It's that the browser is so crushingly slow to load. This lag stems from the puny data speeds supported by most service providers.

Consider the widely used EDGE network. It can support a theoretical maximum of 473.6 kbit/s, when it's running full-tilt on eight timeslots. More common is a max of 236.8 kbit/s (in four time-slot mode).

EDGE is considered "2.75 G"; that is, it's faster than a "2.5 G" data-rate technical such as GPRS, but not as fast as 3G. (Interestingly, EDGE's maximum is faster than the 3G's specification's data rate of 384 kbps, so I'm guessing that, in practice, 3G tends to run faster than EDGE. That is, most EDGE communications occur via four or fewer timeslots.)

Since all the domestic carriers are building out or have built 3G networks, the salient question seems to be: Will browsing on 3G be a better experience than today's experiences on EDGE. (I know there are other options, like EV-DO, but I've already gotten more technical than I intended to in this post.)

More likely, faster networks aren't the answer (since mobile service will never be fast enough to support deskbound-like browsing.

Instead, someone will have to come up with a lighter, smarter mobile browser, and every site of consequence will have to field mobile-optimized pages, which users will actually have to use. Then maybe surfing the Web from one's smartphone won't, er, suck.


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