mirror of
https://github.com/LCTT/TranslateProject.git
synced 2025-01-10 22:21:11 +08:00
01-The history of Android translate completed
This commit is contained in:
limox
parent
d4ceed4f9a
commit
c0393d58d1
@ -1,204 +0,0 @@
|
||||
alim0x translating
|
||||
|
||||
The history of Android
|
||||
================================================================================
|
||||
> Follow the endless iterations from Android 0.5 to Android 4.4.
|
||||
|
||||
|
||||
Android's home screen over the years.
|
||||
Photo by Ron Amadeo
|
||||
|
||||
Android has been with us in one form or another for more than six years. During that time, we've seen an absolutely breathtaking rate of change unlike any other development cycle that has ever existed. When it came time for Google to dive in to the smartphone wars, the company took its rapid-iteration, Web-style update cycle and applied it to an operating system, and the result has been an onslaught of continual improvement. Lately, Android has even been running on a previously unheard of six-month development cycle, and that's slower than it used to be. For the first year of Android’s commercial existence, Google was putting out a new version every two-and-a-half months.
|
||||
|
||||
注：youtube视频地址开始
|
||||
<iframe width="640" height="480" frameborder="0" src="http://www.youtube-nocookie.com/embed/1FJHYqE0RDg?start=0&wmode=transparent" type="text/html" style="display:block"></iframe>
|
||||
|
||||
Google's original introduction of Android, from way back in November 2007.
|
||||
注：youtube视频地址结束
|
||||
|
||||
The rest of the industry, by comparison, moves at a snail's pace. Microsoft updates its desktop OS every three to five years, and Apple is on a yearly update cycle for OS X and iOS. Not every update is created equal, either. iOS has one major design revision in seven years, and the newest version of Windows Phone 8 looks very similar to Windows Phone 7. On Android, however, users are lucky if anything looks the same this year as it did last year. The Play Store, for instance, has had five major redesigns in five years. For Android, that's normal.
|
||||
|
||||
Looking back, Android's existence has been a blur. It's now a historically big operating system. Almost a billion total devices have been sold, and 1.5 million devices are activated per day—but how did Google get here? With this level of scale and success, you would think there would be tons of coverage of Android’s rise from zero to hero. However, there just isn’t. Android wasn’t very popular in the early days, and until Android 4.0, screenshots could only be taken with the developer kit. These two factors mean you aren’t going to find a lot of images or information out there about the early versions of Android.
|
||||
|
||||
The problem now with the lack of early coverage is that *early versions of Android are dying*. While something like Windows 1.0 will be around forever—just grab an old computer and install it—Android could be considered the first cloud-based operating system. Many features are heavily reliant on Google’s servers to function. With fewer and fewer people using old versions of Android, those servers are being shut down. And when a cloud-reliant app has its server support shut off, it will never work again—the app crashes and displays a blank screen, or it just refuses to start.
|
||||
|
||||
Thanks to this “[cloud rot][1]," an Android retrospective won’t be possible in a few years. Early versions of Android will be empty, broken husks that won't function without cloud support. While it’s easy to think of this as a ways off, it's happening right now. While writing this piece, we ran into tons of apps that no longer function because the server support has been turned off. Early clients for Google Maps and the Android Market, for instance, are no longer able to communicate with Google. They either throw an error message and crash or display blank screens. Some apps even worked one week and died the next, because Google was actively shutting down servers during our writing!
|
||||
|
||||
To prevent any more of Android's past from being lost to the annals of history, we did what needed to be done. This is 20+ versions of Android, seven devices, and lots and lots of screenshots cobbled together in one space. This is The History of Android, from the very first public builds to the newest version of KitKat.
|
||||
|
||||
注：下面一块为文章链接列表，发布后可以改为发布后的地址
|
||||
----------
|
||||
|
||||
### Table of Contents ###
|
||||
|
||||
- [Android 0.5 Milestone 3—the first public build][10]
|
||||
- [Android 0.5 Milestone 5—the land of scrapped interfaces][11]
|
||||
- [Android 0.9 Beta—hey, this looks familiar!][12]
|
||||
- [Android 1.0—introducing Google Apps and actual hardware][13]
|
||||
- [Android 1.1—the first truly incremental update][14]
|
||||
- [Android 1.5 Cupcake—a virtual keyboard opens up device design][15]
|
||||
- ----[Google Maps is the first built-in app to hit the Android Market][16]
|
||||
- [Android 1.6 Donut—CDMA support brings Android to any carrier][17]
|
||||
- [Android 2.0 Éclair—blowing up the GPS industry][18]
|
||||
- [The Nexus One—enter the Google Phone][19]
|
||||
- [Android 2.1—the discovery (and abuse) of animations][20]
|
||||
- ----[Android 2.1, update 1—the beginning of an endless war][21]
|
||||
- [Android 2.2 Froyo—faster and Flash-ier][22]
|
||||
- ----[Voice Actions—a supercomputer in your pocket][23]
|
||||
- [Android 2.3 Gingerbread—the first major UI overhaul][24]
|
||||
- [Android 3.0 Honeycomb—tablets and a design renaissance][25]
|
||||
- ----[Google Music Beta—cloud storage in lieu of a content store][26]
|
||||
- [Android 4.0 Ice Cream Sandwich—the modern era][27]
|
||||
- ----[Google Play and the return of direct-to-consumer device sales][28]
|
||||
- [Android 4.1 Jelly Bean—Google Now points toward the future][29]
|
||||
- ----[Google Play Services—fragmentation and making OS versions (nearly) obsolete][30]
|
||||
- [Android 4.2 Jelly Bean—new Nexus devices, new tablet interface][31]
|
||||
- ----[Out-of-cycle updates—who needs a new OS?][32]
|
||||
- [Android 4.3 Jelly Bean—getting wearable support out early][33]
|
||||
- [Android 4.4 KitKat—more polish; less memory usage][34]
|
||||
- [Today Android everywhere][35]
|
||||
|
||||
----------
|
||||
|
||||
### Android 0.5, Milestone 3—the first public build ###
|
||||
|
||||
Before we go diving into Android on real hardware, we're going to start with the early, early days of Android. While 1.0 was the first version to ship on hardware, there were several beta versions only released in emulator form with the SDK. The emulators were meant for development purposes only, so they don’t include any of the Google Apps, or even many core OS apps. Still, they’re our best look into the pre-release days of Android.
|
||||
|
||||
|
||||
The emulator’s default qwerty-bar layout running the Milestone 3 build.
|
||||
Photo by Ron Amadeo
|
||||
|
||||
Before whimsical candy code names and [cross-promotional deals with multinational food corporations][2], the first public release of Android was labeled "m3-rc20a"—"m3" standing for "Milestone 3." While Google may not have publicized the version number—and this build didn't even have a settings app to check—the browser user agent identifies this as "Android 0.5."
|
||||
|
||||
In November 2007, two years after Google acquired Android and five months after the launch of the iPhone, [Android was announced][3], and the first emulator was released. Back then, the OS was still getting its feet under it. It was easily dismissed as "just a BlackBerry clone." The emulator used a qwerty-bar skin with a 320x240 display, replicating an [actual prototype device][4]. The device was built by HTC, and it seems to be the device that was codenamed "Sooner" according to many early Android accounts. But the Sooner was never released to market.
|
||||
|
||||
[According to accounts][5] of the early development days of Android, when Apple finally showed off its revolutionary smartphone in January 2007, Google had to "start over" with Android—including scrapping the Sooner. Considering the Milestone 3 emulator came out almost a year after Apple's iPhone unveiling, it's surprising to see the device interface still closely mimicked the Blackberry model instead. While work had no doubt been done on the underlying system during that year of post-iPhone development, the emulator still launched with what was perceived as an "old school" interface. It didn't make a good first impression.
|
||||
|
||||
At this early stage, it seems like the Android button layout had not been finalized yet. While the first commercial Android devices would use “Home," “Back," “Menu," and “Search" as the standard set of buttons, the emulator had a blank space marked as an "X" where you would expect the search button to be. The “Sooner" hardware prototype was even stranger—it had a star symbol as the fourth button.
|
||||
|
||||
|
||||
From left to right: the home screen, an open notification, and the “apps" folder.
|
||||
Photo by Ron Amadeo
|
||||
|
||||
There was no configurable home screen or widgets, just a simple dock of icons at the bottom that could be cycled through or tapped on. While touch screen support worked for some features, Milestone 3 was primarily controlled with a five-way d-pad—an anachronism that Android still supports to this day. Even this early version of Android could do animations. Icons would grow and shrink as they entered and exited the dock’s center window.
|
||||
|
||||
There was no notification panel yet, either. Notification icons showed up in the status bar (shown above as a smiley face), and the only way to open them was to press "up" on the d-pad while on the home screen. You couldn't tap on the icon to open it, nor could you access notifications from any screen other than home. When a notification was opened, the status bar expanded slightly, and the text of the notification appeared in a speech bubble. Once you had a notification, there was no manual way to clear it—apps were responsible for clearing their own notifications.
|
||||
|
||||
App drawer duties were handled by a simple "Applications" folder on the left of the dock. Despite having a significant amount of functions, the Milestone 3 emulator was not very forthcoming with app icons. "Browser," "Contacts," and "Maps" were the only real apps here. Oddly, "recent calls" was elevated to a standalone icon. Because this was just an emulator, icons for core smartphone functionality were missing, like alarm, calendar, dialer, calculator, camera, gallery, and settings. Hardware prototypes demoed to the press had [many of these][6], and there was a suite of Google Apps up and running by this point. Sadly, there’s no way for us to look at them. They’re so old they can't connect to Google’s servers now anyway.
|
||||
|
||||
|
||||
Milestone 3's menu system in the browser, the wallpaper interface, and the volume control.
|
||||
Photo by Ron Amadeo
|
||||
|
||||
The now-deprecated menu system was up and running in Milestone 3. Hitting the hardware menu button brought up a gray list with a blue gradient highlight, complete with hardware keyboard shortcuts. In the screenshot above, you can see the menu open in the browser. Going to a second level, like the zoom menu, turned the first level of the menu oddly transparent.
|
||||
|
||||
Surprisingly, multitasking and background applications already worked in Milestone 3. Leaving an app didn't close it—apps would save state, even down to text left in a text box. This was a feature iOS wouldn’t get around to matching until the release of iOS 4 in 2010, and it really showed the difference between the two platforms. iOS was originally meant to be a closed platform with no third-party apps, so the platform robustness wasn’t a huge focus. Android was built from the ground up to be a powerful app platform, and ease of app development was one of the driving forces behind its creation.
|
||||
|
||||
Before Android, Google was already making moves into mobile with [WAP sites][7] and [J2ME flip phone apps][8], which made it acutely aware of how difficult mobile development was. According to [The Atlantic][9], Larry Page once said of the company’s mobile efforts “We had a closet full of over 100 phones, and we were building our software pretty much one device at a time.” Developers often complain about Android fragmentation now, but the problem was much, much worse before the OS came along.
|
||||
|
||||
Google’s platform strategy eventually won out, and iOS ended up slowly adding many of these app-centric features—multitasking, cross-app sharing, and an app switcher—later on.
|
||||
|
||||
|
||||
The dialer screen that pops up when you press numbers on the home screen, an incoming call, and the call conferencing interface.
|
||||
Photo by Ron Amadeo
|
||||
|
||||
Despite not having a dialer icon, Milestone 3 emulator was equipped with a way to make phone calls. Pressing anything on the keyboard would bring up the screen on the left, which was a hybrid dialer/contact search. Entering only numbers and hitting the green phone hardware button would start a phone call, and letters would search contacts. Contacts were not searchable by number, however. Even a direct hit on a phone number would not bring up a contact.
|
||||
|
||||
Incoming calls were displayed as an almost-full-screen popup with a sweet transparent background. Once inside a call, the background became dark gray, and Milestone 3 presented the user with a surprisingly advanced feature set: mute, speakerphone, hold, and call conferencing buttons. Multiple calls were presented as overlapping, semi-transparent cards, and users had options to swap or merge calls. Swapping calls triggered a nice little card shuffle animation.
|
||||
|
||||
|
||||
The contacts list, an individual contact, editing a contact, and the recent calls screen.
|
||||
Photo by Ron Amadeo
|
||||
|
||||
Contacts was a stark, black and blue list of names. Contact cards had a spot for a contact picture but couldn't assign one to the space (at least in the emulator). The only frill in this area was XMPP presence dots to the left of each name in Contacts. An always-on XMPP connection has traditionally been at the heart of Android, and that deep integration already started in Milestone 3. Android used XMPP to power a 24/7 connection to Google’s servers, powering Google Talk, cloud-to-device push messaging, and app install and uninstall messages.
|
||||
|
||||
|
||||
The browser’s fake Google homepage, the address bar, and the history interface.
|
||||
Photo by Ron Amadeo
|
||||
|
||||
The browser ran Webkit 419.3, which put it in the same era as Mac OS X 10.4's Safari 2. The homepage was not Google.com, but a hard-coded home.html file included with Android. It looked like Google.com from a thousand years ago. The browser's OS X heritage was still visible, rendering browser buttons with a glossy, Aqua-style search button.
|
||||
|
||||
The tiny BlackBerry-style screen necessitated a separate address bar, which was brought up by a "go to" option in the browser's menu. While autocomplete didn't work, the address bar live searched your history as you typed. The picture on the right was the History display, which used thumbnails to display each site. The current thumbnail was in front of the other two, and scrolling through them triggered a swooping animation. But at this early stage, the browser didn’t support multiple tabs or windows—you had the current website, and that was it.
|
||||
|
||||
|
||||
A video-screengrab-derived Google Maps Photoshop, the directions interface, and the gallery test view.
|
||||
Photo by Ron Amadeo
|
||||
|
||||
From the beginning, Google knew maps would be important on mobile, even shipping a Maps client on the Milestone 5 emulator. That version of Google Maps was the first thing we came across that died from cloud rot. The client can't load information from Google’s servers, so the map displayed as a blank, gray grid. Nothing works.
|
||||
|
||||
Luckily, for the first screenshot above, we were able to piece together an accurate representation from the Android launch video. Old Google Maps seemed fully prepared for a non-touch device, listing hardware key shortcuts along the bottom of the screen. It’s unclear if places worked, or if Maps only ran on addresses at this point.
|
||||
|
||||
Hidden behind the menu were options for search, directions, and satellite and traffic layers. The middle screenshot is of the directions UI, where you could even pick a contact address as a start or end address. Maps lacked any kind of GPS integration, however; you can't find a "my location" button anywhere.
|
||||
|
||||
While there was no proper gallery, on the right is a test view for a gallery, which was hidden in the "API Demos" app. The pictures scrolled left and right, but there was no way to open photos to a full screen view. There were no photo management options either. It was essentially a test of a scrolling picture view.
|
||||
|
||||
|
||||
The time picker and calendar, with ridiculous kerning issues, and the vertical list test, featuring Ars.
|
||||
Photo by Ron Amadeo
|
||||
|
||||
There was also no settings app, but we can look at the original time and date pickers, thanks to the API Demos. This demonstrates how raw a lot of Android was: kerning issues all over the place, a huge gap in between the minute digits, and unevenly spaced days of the week on the calendar. While the time picker let you change each digit independently, there was no way to change months or years other than moving the day block out of the current month and on to the next or previous month.
|
||||
|
||||
Keep in mind that while this may seem like dinosaur remnants from some forgotten era, this was only released six years ago. We tend to get used to the pace of technology. It's easy to look back on stuff like this and think that it was from 20 years ago. Compare this late-2007 timeframe to desktop OSes, and Microsoft was trying to sell Windows Vista to the world for almost a year, and Apple just released OS X 10.5 Leopard.
|
||||
|
||||
One last Milestone 3 detail: Google gave Ars Technica a shoutout in the Milestone 3 emulator. Opening the “API Demos" app and going to "Views," "Focus," then "Vertical" revealed a test list headlined by *this very Website*.
|
||||
|
||||
|
||||
The new emulator skin that comes with Milestone 3, RC37a, which uses a more modern, all-touchscreen style.
|
||||
|
||||
Photo by Ron Amadeo
|
||||
|
||||
Two months later, in December 2007, Google released an update for the Milestone 3 emulator that came with a much roomier 480×320 device configuration. This was tagged "m3-rc37a." The software was still identical to the BlackBerry build, just with much more screen real estate available.
|
||||
|
||||
----------
|
||||
|
||||
|
||||
|
||||
[Ron Amadeo][a] / Ron is the Reviews Editor at Ars Technica, where he specializes in Android OS and Google products. He is always on the hunt for a new gadget and loves to rip things apart to see how they work.
|
||||
|
||||
[@RonAmadeo][t]
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/
|
||||
|
||||
译者：[译者ID](https://github.com/译者ID) 校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[1]:http://arstechnica.com/gadgets/2014/06/how-we-found-and-installed-every-version-of-android/
|
||||
[2]:http://arstechnica.com/gadgets/2013/09/official-the-next-edition-of-android-is-kitkat-version-4-4/
|
||||
[3]:http://arstechnica.com/gadgets/2007/11/its-official-google-announces-open-source-mobile-phone-os-android/
|
||||
[4]:http://www.zdnet.com/blog/mobile-gadgeteer/mwc08-hands-on-with-a-working-google-android-device/860
|
||||
[5]:http://www.theatlantic.com/technology/archive/2013/12/the-day-google-had-to-start-over-on-android/282479/
|
||||
[6]:http://www.letsgomobile.org/en/2974/google-android/
|
||||
[7]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/%E2%80%9D
|
||||
[8]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/%E2%80%9D
|
||||
[9]:http://www.theatlantic.com/technology/archive/2013/12/the-day-google-had-to-start-over-on-android/282479/
|
||||
[10]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/1/#milestone3
|
||||
[11]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/2/#milestone5
|
||||
[12]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/3/#0.9
|
||||
[13]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/6/#1.0
|
||||
[14]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/7/#1.1
|
||||
[15]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/8/#cupcake
|
||||
[16]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/9/#Mapsmarket
|
||||
[17]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/9/#donut
|
||||
[18]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/10/#2.0eclair
|
||||
[19]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/11/#nexusone
|
||||
[20]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/12/#2.1eclair
|
||||
[21]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/13/#alloutwar
|
||||
[22]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/13/#froyo
|
||||
[23]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/14/#voiceactions
|
||||
[24]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/14/#gingerbread
|
||||
[25]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/16/#honeycomb
|
||||
[26]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/19/#music
|
||||
[27]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/19/#ics
|
||||
[28]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/21/#googleplay
|
||||
[29]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/21/#4.1jellybean
|
||||
[30]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/21/#playservices
|
||||
[31]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/22/#4.2jellybean
|
||||
[32]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/23/#outofcycle
|
||||
[33]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/24/#4.3jellybean
|
||||
[34]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/25/#kitkat
|
||||
[35]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/26/#conclusion
|
||||
[a]:http://arstechnica.com/author/ronamadeo
|
||||
[t]:https://twitter.com/RonAmadeo
|
||||
201
translated/talk/01 - The history of Android.md
Normal file
201
translated/talk/01 - The history of Android.md
Normal file
@ -0,0 +1,201 @@
|
||||
安卓编年史
|
||||
================================================================================
|
||||
> 让我们跟着安卓从0.5版本到4.4的无尽迭代来看看它的发展历史。
|
||||
|
||||
|
||||
这些年来历代安卓的主屏幕。
|
||||
图片提供：Ron Amadeo
|
||||
|
||||
安卓已经以不止一种形式陪伴了我们六年以上。在这段时间内，我们已经看到了不同于任何已有开发周期的，绝对惊人变化速度。当Google卷入智能手机的战场中时，它拿出了它的快速迭代，Web风格的更新周期，把它们应用到了开发的这个操作系统之中，而结果就是突击式的持续改进。近来，安卓项目甚至以前所未闻的六个月开发周期在运行，这可比它之前的开发周期慢。在安卓的第一年商业运作时，Google每两个半月就会发布一个新版本。
|
||||
|
||||
注：youtube视频地址开始
|
||||
<iframe width="640" height="480" frameborder="0" src="http://www.youtube-nocookie.com/embed/1FJHYqE0RDg?start=0&wmode=transparent" type="text/html" style="display:block"></iframe>
|
||||
|
||||
Google在2007年11月时对安卓最初的介绍。
|
||||
注：youtube视频地址结束
|
||||
|
||||
同行业的其它公司和其相比，只能是以蜗牛的步伐在缓慢前进。微软每三到五年升级它的桌面操作系统，苹果对OS X和iOS以一年为一个更新周期。另外不是每个更新都是同等地位的。iOS在七年内有一个主要的设计上的大变动，而最新的Windows Phone 8看起来和Windows Phone 7十分相似。但在安卓上，如果用户能看到今年的任何东西看起来和去年一样，那简直是中彩票了一样。比如Play商店，五年内有五次的重新设计。对安卓来说那更是家常便饭。
|
||||
|
||||
回头看看，安卓的存在是很模糊的。从其历史来看，现在它是个使用量巨大的操作系统。近十亿的设备销量，以及每天一百五十万左右的激活量——但Google是如何达到这种地步的？安卓现在如此水平的规模和成功，可能会让你觉得安卓从零开始到万众瞩目的英雄中覆盖到了方方面面。但事实上不是这样的。安卓在早期并不流行，以及直到安卓4.0屏幕截图还只能通过开发者工具实现。这两个因素意味着你无法轻易找到许多安卓早期版本的图片或信息。
|
||||
|
||||
对于早期版本的缺乏覆盖问题现在称作*安卓早期版本正在消亡*。尽管像Windows 1.0这样的系统可以永远在你身边——只要找台旧电脑把它装上去就好了——安卓可以被认为是第一个基于云的操作系统。许多功能严重依赖Google的服务来实现。随着越来越少的人使用老版本的安卓，那些服务被逐渐关闭。当一个依赖云的应用其服务支持停止之后，它再也不能正常运作——应用崩溃并显示空白的屏幕，或直接无法启动。
|
||||
|
||||
正是由于这种“[云腐烂][1]”现象，安卓回顾展在几年内不可能出现。早期版本的安卓没有了云的支持会是一个不能正常工作的破碎的空壳。尽管可以简单地认为这是早期版本安卓渐渐消失的一种方法，但这正是正在发生的。就在写到这里的时候，正有无数的应用因为服务器支持被关闭而失去作用。例如早期的谷歌地图和安卓市场客户端，已经不能和Google服务器交互。它们会弹出错误消息并崩溃或者是显示一个空白的界面。有些应用甚至在一个星期正常运行然后下个星期就宣告死亡，因为就在我们写下这篇文章的时候谷歌正在积极地关闭服务器！
|
||||
|
||||
为了防止在滚滚历史里丢失掉更多关于安卓的过去，我们做了需要完成的工作。这里有20+个版本的安卓，七台设备，以及无数的屏幕截图被集合到一起。这就是安卓编年史，从最早的公开版本到罪行的KitKat。
|
||||
|
||||
注：下面一块为文章链接列表，发布后可以改为发布后的地址
|
||||
----------
|
||||
|
||||
### 目录 ###
|
||||
|
||||
- [Android 0.5 Milestone 3——第一个公开版本][10]
|
||||
- [Android 0.5 Milestone 5——报废接口的领地][11]
|
||||
- [Android 0.9 Beta——嘿，这看起来很眼熟！][12]
|
||||
- [Android 1.0——谷歌应用的引入和实体硬件][13]
|
||||
- [Android 1.1——第一个真正的增量更新][14]
|
||||
- [Android 1.5 Cupcake——虚拟键盘打开设备设计的大门][15]
|
||||
- ----[谷歌地图———登陆安卓市场的第一个内置应用][16]
|
||||
- [Android 1.6 Donut——CDMA支持将安卓带给了各个运营商][17]
|
||||
- [Android 2.0 Éclair——带动GPS产业][18]
|
||||
- [The Nexus One——迎来Google Phone][19]
|
||||
- [Android 2.1——动画的大发现（以及滥用）时代][20]
|
||||
- ----[Android 2.1, update 1——无尽战争的开端][21]
|
||||
- [Android 2.2 Froyo——更快更华丽][22]
|
||||
- ----[语音操作——口袋里的超级电脑][23]
|
||||
- [Android 2.3 Gingerbread——第一个UI大变][24]
|
||||
- [Android 3.0 Honeycomb——平板和设计的新生][25]
|
||||
- ----[Google Music Beta——云存储的内容库][26]
|
||||
- [Android 4.0 Ice Cream Sandwich——摩登时代][27]
|
||||
- ----[Google Play以及直接面向消费者销售设备的回归][28]
|
||||
- [Android 4.1 Jelly Bean——Google Now指明未来][29]
|
||||
- ----[Google Play服务——碎片化以及让系统版本（几乎）过时][30]
|
||||
- [Android 4.2 Jelly Bean——新Nexus设备，新平板界面][31]
|
||||
- ----[周期外更新——谁需要一个新系统？][32]
|
||||
- [Android 4.3 Jelly Bean——为可穿戴设备做好准备][33]
|
||||
- [Android 4.4 KitKat——更完美；更少的内存占用][34]
|
||||
- [今日安卓无处不在][35]
|
||||
|
||||
----------
|
||||
|
||||
### Android 0.5, Milestone 3——第一个公开版本 ###
|
||||
|
||||
在我们开始在实体硬件上研究安卓之前，我们要从很早，很早以前的安卓时光开始说起。尽管1.0是第一个运行在实体硬件上的版本，但在那之前其实还有若干个只随SDK发布的模拟器beta版本。这些模拟器只用于开发的目的，所以它们不含任何谷歌应用，甚至是一些核心系统应用。但它们仍然是回顾安卓的发布前时光的最好渠道。
|
||||
|
||||
|
||||
模拟器默认的qwerty布局并运行Milestone 3。
|
||||
Ron Amadeo供图
|
||||
|
||||
在异想天开的糖果版本代号和[与跨国食品公司跨界合作][2]之前，第一个安卓的公开发布版本的标签是“m3-rc20a”——“m3”代表“Milestone 3（里程碑3）”。尽管谷歌可能不会公布版本号——这个版本甚至没有一个设置应用来查看——浏览器用户标识识别为“Android 0.5”。
|
||||
|
||||
在2007年11月，谷歌获得安卓两年，iPhone发布五个月之后，[安卓正式发布][3]，第一个模拟器正式释出。回到那时候看，这个系统才刚处于起步阶段。它很容易就被认为“只是个黑莓的山寨而已”。模拟器使用了一个qwerty布局的皮肤以及320×240的显示屏，是一台[原型设备][4]的复制品。这台设备由HTC制造，通过一些早期的安卓账户可以得知这台设备的代号似乎是“Sooner”。但是Sooner从未正式上市。
|
||||
|
||||
通过安卓早期[开发账号][5]得知，当苹果在2007年1月最终发布它革命性的智能手机后，谷歌不得不对安卓“从头来过”——包括放弃Sooner。考虑到Milestone 3模拟器在苹果的iPhone后近一年才推出，设备界面看起来还是那么像黑莓的模型是在是令人惊奇的事情。尽管在iPhone发布后的开发里任务毫无疑问地在优先保障下完成了，但模拟器仍然以被认为是“旧学院风”的界面发布。这使得它没能给人留下一个好的第一印象。
|
||||
|
||||
在早期阶段，安卓按键布局看起来并没有最终确定下来。尽管第一台商业安卓设备使用了“主屏幕”，“后退”，“菜单”以及“搜索”作为标准的按键套件，模拟器上有一个空白的标记为“X”的键，你可能会认为是那是搜索键应该在的地方。“Sooner”原型机看起来更奇怪——它在第四个键上有个星形标记。
|
||||
|
||||
|
||||
从左到右：主屏幕，一个打开的通知，以及“应用”文件夹。
|
||||
Ron Amadeo供图
|
||||
|
||||
在这里没有可以配置的主屏幕或小插件，仅仅只是简单的在底部有聚合图标的dock，可以循环或是点击。尽管已经有一些特性支持触摸屏，Milestone 3主要还是使用五向十字键——一个时至今日安卓仍然支持的不合时宜的设计。甚至早期的安卓都能够实现动画效果。图标在进入dock的中心窗口时会变大或缩小。
|
||||
|
||||
在这时候一样也还没有通知栏。通知图标显示在顶部状态栏（上面图片中的微笑标志），打开它的唯一方法是在主屏幕按下十字键的上键。你无法通过点击微笑的图标来打开它，也无法从除主屏幕以外的地方打开通知。当通知被打开的时候，状态栏些许地扩展开，通知文本会显示在一个聊天气泡中。一旦你阅读完通知，你无法手动清除它——应用本身负责清除它的通知消息。
|
||||
|
||||
应用抽屉的职责由一个dock左侧简单的“应用程序”文件夹负责。尽管有着不少标志性的功能，Milestone 3模拟器应用图标还不是十分完善。只有“浏览器”，“联系人” ，以及“地图”是这里面真正的应用。奇怪的是，“最近通话”被提升为一个独立的图标。因为这仅仅只是个模拟器，像闹钟，日历，拨号，计算器，照相机，相册，以及设置这样的智能手机核心功能的图标统统没有。硬件原型倒是有[其中的大部分][6]，它还有一套谷歌应用出现并运行着。不幸的是我们没办法看到它们了。它们已经老到无论如何都连不上谷歌的服务器了。
|
||||
|
||||
|
||||
Milestone 3的浏览器菜单系统，壁纸界面，以及音量控制。
|
||||
Ron Amadeo供图
|
||||
|
||||
这套现在已经过时的菜单系统出现并运行在Milestone 3上。点击实体菜单键会打开一个灰色带有蓝色梯度高亮的列表，通过实体键盘完成操作。在上面的截图中，你可以看到在浏览器中打开的菜单。进入二级菜单，像缩放菜单，一级菜单变成有些奇怪的透明状态。
|
||||
|
||||
令人惊喜的是，多任务及后台应用在Milestone 3上已经可以运作了。离开应用而不关闭它——应用会保存状态，甚至写入文本保存。这个特性iOS直到2010年推出iOS 4才能与其相比，这就真正显示出了这两个平台的不同。iOS最初是作为一个封闭的平台而没有第三方应用，所以平台的鲁棒性并没有得到很大的关注。安卓是从头开始被构建成一个强大的应用软件平台，轻松开发应用是它创造出来背后的推动力之一。
|
||||
|
||||
在安卓之前，谷歌已经通过[WAP网站][7]和[J2ME手机应用][8]向移动端开始迁移，这使得它们强烈地意识到移动开发的难度。据[The Atlantic][9]，拉里佩奇曾这么描述公司在移动端的努力“我们有一系列超过100台手机，我们在每一台设备上都要构建一次我们的应用”。开发者们现在经常抱怨安卓的碎片化，但在安卓出现之前，问题要比现在糟糕很多。
|
||||
|
||||
谷歌的平台战略实际上胜出了，iOS最终在不久后开始慢慢加入这些围绕应用的特性——多任务，跨应用分享，以及应用切换。
|
||||
|
||||
|
||||
当你在主屏幕按数字键弹出的拨号界面，来电，以及电话会议界面。
|
||||
Ron Amadeo供图
|
||||
|
||||
尽管没有拨号图标，Milestone 3模拟器还是有办法拨号。按键盘上的任意键会打开左侧界面，这是拨号/联系人搜索混合界面。仅输入数字并点击绿色的实体拨号键来开始通话，输入字母会搜索联系人。但是联系人无法通过数字搜索。甚至直接点击一个号码也不会打开联系人。
|
||||
|
||||
来电被显示成一个几乎全屏的令人愉快的透明背景弹窗。一旦进入通话，背景会变成深灰色，Milestone 3展现给用户一些令人惊奇的高级特性：静音，扬声器，保持，以及电话会议按钮。多方通话会显示成重叠，半透明的卡片状，用户有切换或者合并通话的选项可以选择。切换通话会触发一个漂亮的小卡片洗牌动画。
|
||||
|
||||
|
||||
联系人列表，打开一个联系人，编缉联系人，以及最近通话界面。
|
||||
Ron Amadeo供图
|
||||
|
||||
联系人是一个质朴的，黑色和蓝色的姓名列表。联系人卡片中有个联系人头像的位置但是没办法设置一张图像上去（至少在模拟器中不行）。这里唯一的装饰是每个联系人名字左侧的XMPP状态点。传统来说一个保持在线的XMPP连接是安卓的核心，它的深度集成从Milestone 3就已经开始了。安卓使用XMPP来驱动一个24/7在线的与谷歌服务器之间的连接，驱动Google Talk，云到端消息推送，以及应用的安装和卸载信息。
|
||||
|
||||
|
||||
浏览器的假Google首页，地址栏，浏览历史界面。
|
||||
Ron Amadeo供图
|
||||
|
||||
浏览器运行Webkit 419.3，它也被用在相同时代的像Mac OS X 10.4的Safari 2上。浏览器主页并不是Google.com，而是一个包含在安卓里的硬编码的home.html文件。它看起来就像是千年之前的Google.com。浏览器的OS X遗留还可以辨认出来，用了光滑的，Aqua风格的搜索按钮来渲染浏览器按钮。
|
||||
|
||||
这个小小的黑莓风格的屏幕需要一个分离的地址栏，可以通过浏览器菜单里的“前往”选项打开。尽管自动补全不起作用，地址栏会在你输入的时候实时搜索你的浏览历史。右侧图片显示的是历史界面，它使用了略缩图来显示各个站点。当前的略缩图在其它两个之前，滑动它们会触发一个猛扑的动画效果。但在早期阶段，浏览器不支持多标签或窗口——你可以看到当前站点，那就是全部了。
|
||||
|
||||
|
||||
一个视频屏幕抓取导出的谷歌地图界面，方向界面，相册测试界面。
|
||||
Ron Amadeo供图
|
||||
|
||||
在开始的时候，谷歌认识到在移动端地图将会非常重要，甚至在Milestone 5模拟器中内置了地图客户端。那个版本的谷歌地图是我们遇到的第一个死于云腐烂的。这个客户端无法从谷歌的服务器上载入信息，所以地图显示为一片空白，灰色的网格。没有什么能够运转。
|
||||
|
||||
幸运的是，因为上面的第一张截图，我们能够从安卓启动视频中拼凑出准确的界面。旧的谷歌地图看起来完全是为非触摸设备准备的，实体键快捷方式列表排列在屏幕底部。这样在看地图时，或是在如果仅仅显示该点的地址的时候就不大清楚。
|
||||
|
||||
隐藏在菜单之后的是搜索选项，方向，以及卫星和交通图层。中间的截图是方向的UI之一，你可以选择一个联系人的地址作为起点或者终点。但地图缺乏任何种类的集成GPS，你在哪都找不到“我的位置”这个按钮。
|
||||
|
||||
尽管没有合适的相册，在右边是相册的测试界面，隐藏在“API Demos”应用里。图片可以向左向右滚动，但无法以全屏的方式打开一张照片。同样它也没有照片管理选项。它本质上就是个图片滚动界面的测试视图。
|
||||
|
||||
|
||||
时间设置和日历，有点字间距问题，以及以Ars为特色的垂直列表测试。
|
||||
Ron Amadeo供图
|
||||
|
||||
同样模拟器中也没有设置应用，但是通过API Demos我们可以看到最初的日期时间设置界面。这个示例暴露出很多安卓没来得及处理的问题：到处都有的字间距问题，分钟数字间巨大的间隔，以及日历中星期日间不均等的间隔。尽管时间设置允许你单独更改每个数字，但除非你将当前日期移出本月到前一个或下一个月，否则你无法改变月份或年份。
|
||||
|
||||
别忘了尽管这看起来像是一些被遗忘时代的恐龙级别遗留物，但这仅仅是六年前发布的。我们总趋向与适应科技的脚步。我们很容易将这样的东西看作是20年前的东西。比较一下2007年晚些时候这个时间段的桌面操作系统，微软尝试将Windows Vista售往全世界快要一年了，而苹果刚刚发布OS X 10.5 Leopard。
|
||||
|
||||
最后一个关于Milestone 3的细节：谷歌在Milestone 3模拟器中给了Ars Technica一个快捷方式。打开“API Demos”应用并打开"Views," "Focus,"然后"Vertical"显示一个*this very Website*的头条测试列表。
|
||||
|
||||
|
||||
随Milestone 3，RC37a发布的更加现代，全触控风格的模拟器。
|
||||
Ron Amadeo供图
|
||||
|
||||
两个月后，2007年12月，谷歌放出了一个Milestone 3的更新，带来了更大的480×320设备设置。这个更新的标签是“m3-rc37a”。软件看起来还是像黑莓一样，仅仅是带来了更多的屏幕分辨率支持。
|
||||
|
||||
----------
|
||||
|
||||
|
||||
|
||||
[Ron Amadeo][a] / Ron是Ars Technica的评论编缉，专注于安卓系统和谷歌产品。他总是在追寻新鲜事物，还喜欢拆解事物看看它们到底是怎么运作的。
|
||||
|
||||
[@RonAmadeo][t]
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/
|
||||
|
||||
译者：[alim0x](https://github.com/alim0x) 校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[1]:http://arstechnica.com/gadgets/2014/06/how-we-found-and-installed-every-version-of-android/
|
||||
[2]:http://arstechnica.com/gadgets/2013/09/official-the-next-edition-of-android-is-kitkat-version-4-4/
|
||||
[3]:http://arstechnica.com/gadgets/2007/11/its-official-google-announces-open-source-mobile-phone-os-android/
|
||||
[4]:http://www.zdnet.com/blog/mobile-gadgeteer/mwc08-hands-on-with-a-working-google-android-device/860
|
||||
[5]:http://www.theatlantic.com/technology/archive/2013/12/the-day-google-had-to-start-over-on-android/282479/
|
||||
[6]:http://www.letsgomobile.org/en/2974/google-android/
|
||||
[7]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/%E2%80%9D
|
||||
[8]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/%E2%80%9D
|
||||
[9]:http://www.theatlantic.com/technology/archive/2013/12/the-day-google-had-to-start-over-on-android/282479/
|
||||
[10]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/1/#milestone3
|
||||
[11]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/2/#milestone5
|
||||
[12]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/3/#0.9
|
||||
[13]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/6/#1.0
|
||||
[14]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/7/#1.1
|
||||
[15]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/8/#cupcake
|
||||
[16]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/9/#Mapsmarket
|
||||
[17]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/9/#donut
|
||||
[18]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/10/#2.0eclair
|
||||
[19]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/11/#nexusone
|
||||
[20]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/12/#2.1eclair
|
||||
[21]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/13/#alloutwar
|
||||
[22]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/13/#froyo
|
||||
[23]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/14/#voiceactions
|
||||
[24]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/14/#gingerbread
|
||||
[25]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/16/#honeycomb
|
||||
[26]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/19/#music
|
||||
[27]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/19/#ics
|
||||
[28]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/21/#googleplay
|
||||
[29]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/21/#4.1jellybean
|
||||
[30]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/21/#playservices
|
||||
[31]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/22/#4.2jellybean
|
||||
[32]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/23/#outofcycle
|
||||
[33]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/24/#4.3jellybean
|
||||
[34]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/25/#kitkat
|
||||
[35]:http://arstechnica.com/gadgets/2014/06/building-android-a-40000-word-history-of-googles-mobile-os/26/#conclusion
|
||||
[a]:http://arstechnica.com/author/ronamadeo
|
||||
[t]:https://twitter.com/RonAmadeo
|
||||
Loading…
Reference in New Issue
Block a user