Recommend


1:CBS Connecticut
2:Zombie Soundz
3:Japanese ladio.net Appli
4:Silent Mode Switch
5:Fuck You
6:국립목포병원 김대연
7:破損的電話惡作劇
8:IPhone4S-SMC開賣偵測
9:掌上三國
10:Amino
11:HuaSengHeng
12:Sudoku 100
13:Routinely
14:★연인 필수★ 애정도 테스트
15:イケメン★ホスト学園lite 海人編
16:J研 着メロ
17:SketchBook Pro
18:Image To Text - OCR
19:FluffyGuy
20:TypingCONy for German (Beta)
21:KKBOX Player Widget(for HTC)
22:Young Salem #1
23:的QR條碼掃描器
24:鲜果联播
25:3D Flip Clock Theme Pack 02
26:GoldMill Slot Machine
27:코오롱 한국오픈(KOLON KOREA OPEN)
28:_朱子治家》 -- 点读儿童启蒙书系列 - 加强版
29:細木数子六星占術「2012年の運命」 for Mobage
30:Diablo Defense ®

1:Govberg Buys Watches
2:Govex
3:Gov Pro
4:Gourmet Biz
5:Goulston & Storrs News Application
6:GourmateMobile
7:Glossary of Freight & Shipping
8:Gottesman Residential Real Estate
9:Goto Guide
10:GottaDeal.com
11:GoTech
12:Flash Morse
13:Flash Message
14:Gloryacht
15:GOST.
16:GorjetaS
17:Flash Gordon Movies Unlimited App
18:GorillaTrades
19:GorillaMgc
20:Flash Gordon Conquers the Universe - The Complete Movie Serial
21:Glomaris Distance Table Free Edition
22:Gorilla Production Reel
23:Gore Brothers Mobile
24:Gorilla Expense 1.0
25:Get Tied Up Pro
26:Get-A-Business-Plan
27:Get Tied Up
28:Get Rid of Your Fear of Success with Prof McMurphy_s Subliminal Techniques
29:Glockner.com Honda Toyota GM
30:Get the Skinny from McKinney
maper

Android Team “Laser Focused” On The User Experience For Next Release

http://techcrunch.com/2010/06/16/android-team-laser-focused-on-the-user-experience-for-next-release/

by Michael Arrington

Google’s Android team has been pushing new versions of the operating system at a furious pace since the first Android device hit the market in 2008. Lots of features have been added over the last couple of years. But the user experience hasn’t evolved much.

That’s all going to change in the next version, we’ve heard from multiple sources close to Google.

The team more or less has the core features they want at this point, say our sources, although more tweaks are certainly coming. But Google wants to put an end to the desire of handset manufacturers and carriers to add their own UI layer on top of Google – things like Sense, Motoblur, Ninjablur, etc.

Most of the time their shells aren’t all that great anyway (see HTC EVO), and they tend to slow down the device.

Google is focusing the bulk of its efforts on the user experience for the upcoming Gingerbread release to counter this. And they want to get the Android experience closer to the iPhone.

It’s unlikely that third parties will ever completely resist the temptation to meddle to differentiate their products and to get more control over the user. But Google’s goal is to make those “skins” as pointless as possible.

That’s a big goal, particularly since Android is a flexible operating system that is designed to handle a variety of hardware options. When you don’t lock down the hardware it’s very hard to make the UI perfect. Which is why Apple’s Macs, with locked down hardware, have always been a better experience than the hugely hardware-flexible Windows operating system.

Android Chief Andy Rubin: Updates Will Eventually Come Once A Year

http://techcrunch.com/2010/06/01/android-chief-andy-rubin-updates-will-eventually-come-once-a-year/

by Jason Kincaid

In an interview with the Silicon Valley Mercury News, Google VP Andy Rubin — who founded and leads the Android platform — shared some information about the future of the mobile OS. One of the more interesting answers he had concerned Android’s rapid pace of innovation, and how things may slow down a bit in the future.

Since launching in fall 2008, Android has come an incredibly long way. In fact, in the interview Rubin acknowledges that the inital release felt more like a ‘.8′, rather than a full 1.0 release, but the platform has matured considerably with at least four major updates since then. However, many phones are still running versions of the OS that are months out of date, and developers have to worry about ensuring compatibility with each new upgrade. That’s going to change in the future: Rubin says that updates to Android are now coming around twice a year, and that once things settle down it will probably be more like once a year.

So we launched it, and from our internal 0.8, we got to 1.0 pretty quickly, and we went through this iteration cycle. You’ve noticed, probably, that that’s slowed down a little bit. Our product cycle is now, basically twice a year, and it will probably end up being once a year when things start settling down, because a platform that’s moving — it’s hard for developers to keep up. I want developers to basically leverage the innovation. I don’t want developers to have to predict the innovation.

In other words, Android will likely be adopting a more iPhone-like release schedule. While this isn’t fun to hear (I like getting my new features as soon as possible), it’s probably better for the health of the platform in the long run. Carriers/OEMs will be better able to keep up with rolling out upgrades, hopefully leading to less fragmentation, and developers won’t have to worry about optimizing for as many new releases.

In another question, Rubin also identified which products we’re most likely see to see Android on beyond phones, namely PCs, cars, and TVs. This isn’t really a surprise — we’ve already seen a few cars running Android, and  Google TV debuted last month —  but it sounds like these aren’t just going to be viewed as Android side projects: Rubin says that Google will be doing “everything [it] can to get the big ones”.

We’re at about 4 billion cell phones. About 1.4 billion Internet connected PCs — that includes desktop and laptops and everything else. Like 1.2 billion automobiles. Some 800 million TVs.
And it’s like, “OK, let’s target the top four.” Let’s do everything we can to get the big ones. Remember, our business is volume, because it’s an advertising business and we want to delight a lot of people. And how do you delight a lot of people? You get in the products that they use every day.


Leave a Reply

 

 

 

You can use these HTML tags

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>