How the original iPhone forced Google to completely rebuild Android


Recommended Posts

The day Steve Jobs unveiled the original iPhone model (January 9th, 2007,) Google?s Android team, which had been secretly working on a smartphone for two years, took a ?kick in the stomach,? The Atlantic revealed. While Google knew, as everyone else also knew at the time, that Apple was working on a smartphone, the company ?just didn?t think it would be that good,? Ethan Beard, an early Android business development executive said. Watching the iPhone keynote on his way to a CES 2007 Android-related meeting in Las Vegas, Rubin reportedly stopped his car to see the entire performance Steve Jobs was putting on stage at the time. ?Holy crap,? he told a colleague, ?I guess we?re not going to ship that phone,? referring to the BlackBerry-like Android device his team was working on at the time.

 

?Sooner? was the codename of the first Android handset that never shipped because of the iPhone. The device was arguably ?more revolutionary than what had just been revealed in the iPhone,? the publication writes, but it was ?ugly,? featuring a traditional keyboard and a touch-less small display.

?As a consumer I was blown away. I wanted [an iPhone] immediately. But as a Google engineer I thought ?We?re going to have to start over?? Chris DeSalvo said. ?What we had suddenly looked so? nineties. It?s just one of those things that are obvious when you see it.?

 

After working for two years on Sooner, which was supposed to ship in late 2007, the Android team had to refocus on a different device, a phone with a touchscreen that could compete with the iPhone, codenamed Dream at the time, and whose launch was pushed back to fall 2008.

 

?I never got the feeling that we should scrap what we were doing ? that the iPhone meant game over,? then Android?s project manager Erick Tseng said. ?But a bar had been set, and whatever we decided to launch, we wanted to make sure that it cleared the bar.?

 

Interestingly, Google managed to reach its goal with Android, which at the time the iPhone launched was making sure Microsoft would not do to the smartphone business what it did to the PC business before, and keep its search-based services relevant in the growing mobile ecosystem. ?It?s hard to relate to that [fear of Microsoft] now, but at the time we were very concerned that Microsoft?s mobile strategy would be successful,? Google?s Eric Schmidt said during his testimony in the Oracle vs Google copyright trial last year. Since then,Android became the most successful smartphone platform, by market share, with Apple still making most of the profits from the mobile business.

http://news.yahoo.com/original-iphone-forced-google-completely-rebuild-android-152547037.html

Actual title: "How the original iPhone forced Google to completely rebuild Android"

 

Title for Neowin: "How the original iPhone forced Google to copy it"

 

Can we get this man a job as a writer here?!

No, this is the original title....

Right. That's the title of the article. "copied it" is the title of this post.  :shifty:

 

EDIT to your EDIT: Fine. I'll take that into consideration next time.

Right. That's the title of the article. "copied it" is the title of this post.  :shifty:

 

I edited my post.  When you change the title of the article you are quoting, it is frowned upon.  The change you made makes a big difference.

Copy and Rebuild are different though. 

very true

 

however they did rebuild to make the feature set in-line with what the iPhone was offering....

 

they weren't even thinking Touch-interface back in 2007. 

  • Like 2

Android_before_after_iphone.jpg

That is Eclair, Android 2.0 on that Nexus One.  The first handset is a prototype.  Think maybe you missed a phone or two in between?

 

Talk about cherry-picking.

 

Try this on for size as the first available android phone (well before the HTC Nexus One, heh):

 

imgHtc%2520Dream4.jpeg

That is Eclair, Android 2.0 on that Nexus One.  The first handset is a prototype.  Think maybe you missed a phone or two in between?

 

Talk about cherry-picking.

 

Try this on for size as the first available android phone (well before the HTC Nexus One, heh):

 

imgHtc%2520Dream4.jpeg

What are you trying to imply here? That Android wasn't designed to copy the look and feel of the iPhone? Obviously the first one was a prototype. It is how they envisioned Android at the beginning: as a Blackberry clone. All of a sudden, the new Android features a dock at the bottom, similar to iOS and Mac OSX.

What are you trying to imply here? That Android wasn't designed to copy the look and feel of the iPhone? Obviously the first one was a prototype. It is how they envisioned Android at the beginning: as a Blackberry clone. All of a sudden, the new Android features a dock at the bottom, similar to iOS and Mac OSX.

 

Who cares if they copied them? Almost every company copies their competitor's ideas or features and attempts to improve upon them. In return the consumer generally gets a more refined and polished product. 

Who cares if they copied them? Almost every company copies their competitor's ideas or features and attempts to improve upon them. In return the consumer generally gets a more refined and polished product. 

We would be no where as a civilization if we didn't. Unfortunately people don't understand that. Prior to the iPhone's launch and wide acceptance, the most popular smart phone was a Blackberry, so would it not make sense that that's what they'd model it after? That was the popular form factor at the time. The iPhone is far from the first to use a full touch screen, Windows Mobile had been doing it for quite a while. What Apple did was make the form factor popular by polishing it up a little. The capacitive touch screen with a finger friendly UI was a major part of making the modern style smart phone popular. Was it new from Apple? Still no, but again they helped polish it up for the general public. Even dumb it down in a sense to gain acceptance from the less tech savvy.

 

So which form factor did Google settle on focusing on for Android, the dying Blackberry style smart phone with integrated keyboard, or the new and improved touch based smartphone like the iPhone. Thankfully Google isn't stupid and chose not to go with the form factor that was going out of style. Even then, they still had a slider keyboard on a lot of early Androids, which again was more like copying WinMo than iPhone.

 

This article pops up every few months whenever iPhone users aren't feeling quite smug enough with themselves. Nothing really of substance though, just perhaps an interesting read into the history and early product development of Android as compared to it's surrounding ecosystem.

What are you trying to imply here? That Android wasn't designed to copy the look and feel of the iPhone? Obviously the first one was a prototype. It is how they envisioned Android at the beginning: as a Blackberry clone. All of a sudden, the new Android features a dock at the bottom, similar to iOS and Mac OSX.

I too suggest not to change titles. But, one things for sure here one must learn here is that the people here WORSHIP Android hardcore, saying ANYTHING that is not praise for it will get you immediately trampled upon. 

I too suggest not to change titles. But, one things for sure here one must learn here is that the people here WORSHIP Android hardcore, saying ANYTHING that is not praise for it will get you immediately trampled upon. 

You get the same treatment from the Apple camp and Microsoft camp.

 

There is a term for these guys...fanboys?

 

All I said was that he cherry-picked before and after devices, when one was never released, and the second one, there were several android releases in between.

 

If you want to make a point, at least be honest about it.

But Google didn't copy them.  Google isn't a hardware company.  Now if HTC decided to change the look and design of their first G1 Android phone that was entirely up to them.  Trying to compare a hardware company (Apple) to a software company (Google) is poor at best.  Not that these facts ever stop Apple fanboys from distorting them horribly like the linked article.

What are you trying to imply here? That Android wasn't designed to copy the look and feel of the iPhone? Obviously the first one was a prototype. It is how they envisioned Android at the beginning: as a Blackberry clone. All of a sudden, the new Android features a dock at the bottom, similar to iOS and Mac OSX.

Who he hell cares. Think Microsoft or Apple would be where they are at if they didnt copy things either? Seriously, that is how things progress and how innovation progresses. Samsung is the one that took it way to far and where the copying comes in to play with Android really. Which Google doesnt have any say in Samsungs designs.

But anyway, people need to stop complaining about who copied who. It is really getting old.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • No, size is not the only selling point. I did not even remotely say that. Your claim was that "building your own will be faster and cheaper". This is false. You cannot build something close to that form factor with off-the-shelf parts. You can build a Mini-ITX PC and pay more, or something larger and pay less. But these are different market segments. It's apples and oranges.
    • There is a default resolution setting in Settings > Display that can be changed with a click. You can also change the settings on a per-game basis. No CLI needed. Also, Steam has countless games that are not "[perpetual] alpha/beta games", so no need for the straw man. Plus you can use other stores as well. And console games (e.g. PS5) cost a fortune, which itself more than negates the price subsidy on the system, unless you plan on exclusively playing 1 or 2 games. It's true that you shouldn't buy a system that doesn't support the game(s) you want to play, but I think that's kinda obvious, and applies to every console as well as PC. I don't game in the living room and have no need of a Steam Machine, but there is a clear market segment that would find it useful.
    • RSS Guard 5.2.0 by Razvan Serea RSS Guard is a simple (yet powerful) feed reader. It is able to fetch the most known feed formats, including RSS/RDF and ATOM. It's free, it's open-source. RSS Guard currently supports Czech, Dutch, English, French, German, Italian. RSS Guard will never depend on other services - this includes online news aggregators like Feedly, The Old Reader and others. RSS Guard is developed on top of the Qt library and it supports these operating systems: Windows GNU/Linux OS/2 (eComStation) Mac OS X xBSD (possibly) Android (possibly) other platforms supported by Qt The core features of RSS Guard are: support for online feed synchronization via plugins, Tiny Tiny RSS (from RSS Guard 3.0.0). multiplatform, support for all feed formats, simplicity, import/export of feeds to/from OPML 2.0, downloader with own tab and support for up to 6 parallel downloads, message filter with regular expressions, feed metadata fetching including icons, simple Adblock functionality, customized popup notifications, Google-based auto-completion for internal web browser location bar, ability to cleanup internal message database with various options, enhanced feed auto-updating with separate time intervals, multiple data backend support, SQLite (in-memory DBs too), MySQL. is able to specify target database by its name (MySQL backend), “portable” mode support with clever auto-detection, feed categorization, drap-n-drop for feed list, automatic checking for updates, ability to discover existing feeds on websites, full support of podcasts (both RSS & ATOM), ability to backup/restore database or settings, fully-featured recycle bin, printing of messages and any web pages, can be fully controlled via keyboard, feed authentication (Digest-MD5, BASIC, NTLM-2), handles tons of messages & feeds, sweet look & feel, fully adjustable toolbars (changeable buttons and style), ability to check for updates on all platforms + self-updating on Windows, hideable main menu, toolbars and list headers, KFeanza-based default icon theme + ability to create your own icon themes, fully skinnable user interface + ability to create your own skins, “newspaper” view, plenty of skins, support for "feed://" URI scheme, ability to hide list of feeds/categories, open-source development model based on GNU GPL license, version 3, tabbed interface, integrated web browser with adjustable behavior + external browser support, internal web browser mouse gestures support, desktop integration via tray icon, localizations to some languages, Qt library is the only dependency, open-source development model and friendly author waiting for your feedback, no ads, no hidden costs. RSS Guard 5.2.0 changelog: Added: Feed auto-fetch can now also be delayed while Feral GameMode is active on Linux and startup auto-fetch is skipped when GameMode is already active. (#2265) WebEngine builds can now use RSS Guard generated proxy auto-config (PAC) rules so article/web browsing follows per-account and per-feed proxy settings more closely. (#2273) Generated PAC rules now also cover related subdomains and use Public Suffix List data, so feeds such as feeds.bbc.co.uk can also proxy resources from images.bbc.co.uk. (#2273) Standard feeds can now define extra proxy domains, useful when article images, stylesheets or other page resources are loaded from a CDN or another domain that should use the same feed proxy. (#2273) RSS Guard now asks for proxy credentials when a WebEngine page needs proxy authentication and can fill credentials from the current feed proxy when available. (#2273) Network settings again include an option to ignore all cookies, which clears stored cookies and prevents new cookies from being accepted. Standard RSS/ATOM feeds can now individually ignore cookies while downloading feed data. Stored cookies can now be deleted from the Tools menu. Custom skin colors can now override the feed list article count color separately from feed titles, including a separate highlighted color. (#2275) Settings dialog can now search across available settings and highlight matching controls. (#1754) Standard RSS/ATOM feeds can now optionally be reported as broken when they are valid but contain no articles. (#2039) Standard RSS/ATOM feeds can now override the application-wide feed connection timeout per feed. (#1023) Tray icon can now use a custom background color and unread-count text color, with an option to reuse the generated icon as the application icon. (#1973) Support for more benevolent parsing of Gemlog entries (#2295). Article list can now show when an article was received by RSS Guard. (#947) Feed deep discovery now actually scrapes all links found in the website and checks if they are feeds or not. This greatly enhances usability of the deep discovery mode and discovers many more feeds than before. (#2306) Search boxes now show a small dot when the feed or article list is hiding some items because of active filtering. (#873) Articles now have a shortcut-assignable action to open the homepage of the feed they belong to. (#2060) Fixed: Parallel feed updates no longer crash when multiple update results are processed at the same time. (64cf521) Links in WebEngine articles opened from feeds such as Kill the Newsletter now open correctly instead of being swallowed by the embedded page. (#2272) Relative article URLs resolution was kinda broken. (#2282) Clicking article URL did not work when the URL had "fragment" set. (#2293) The default proxy setting now uses Qt/system default proxy behavior instead of forcing no proxy. (e0263ad) WebEngine article loading now keeps the current feed context, so feed-specific proxy credentials remain available while the article page loads. (fdd0f00) Download: RSS Guard 5.2.0 (64-bit) | Portable | ~ 130.0 MB (Open Source) Link: RSS Guard Home Page | Other Operating Systems | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • This is gonna separate the creeps from the rest of the crowd.
  • Recent Achievements

    • Rookie
      DaviKar went up a rank
      Rookie
    • Dedicated
      HidekoYamamoto94 earned a badge
      Dedicated
    • One Month Later
      timbobit earned a badge
      One Month Later
    • One Month Later
      nates earned a badge
      One Month Later
    • Week One Done
      Almohandis earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      461
    2. 2
      +Edouard
      161
    3. 3
      PsYcHoKiLLa
      110
    4. 4
      Michael Scrip
      83
    5. 5
      Steven P.
      69
  • Tell a friend

    Love Neowin? Tell a friend!