Group items tagged

If your data is stored in a SQLite database on the device, performing a full-text search (using FTS3, rather than a LIKE query) can provide a more robust search across text data and can produce results significantly faster.

If your data is stored online, then the perceived search performance might be inhibited by the user's data connection. You might want to display a spinning progress wheel until your search returns.

<?xml version="1.0" encoding="utf-8"?><searchable xmlns:android="http://schemas.android.com/apk/res/android"    android:label="@string/app_label"    android:hint="@string/search_hint" ></searchable>

如果你看过主站介绍 Kik 的文章，一定对 Kik 用户的快速增长感到惊讶，这个功能简单的消息软件在短时间野蛮生长,在发行的 15 天内，用户人数从 0 增长到 100 万人

Kik 这种 Push IM 将快速消灭传统的短信，尤其是它把触角伸进你的通讯录之后

Kik 最初的目的是一个革命性的（很酷的）音乐分享、远程操作服务，但是 Kik 团队很快发现他们利用这些技术创造了一个信息交流应用，于是他们暂时放弃了音乐服务的打算，将所有多余的东西抛弃，专心做了一个快速、可靠的短消息应用。 Kik 的 CEO Ted Livingston 告诉 BGR，由于人数增长过快，他们不得不雇佣一架飞机，给数据中心增加服务器以保证服务的正常运行

Intent videoClient = new Intent(Intent.ACTION_VIEW);    videoClient.setData(Uri.parse("http://m.youtube.com/watch?v="+videoId));    videoClient.setClassName("com.google.android.youtube", "com.google.android.youtube.PlayerActivity");    startActivityForResult(videoClient, VIDEO_APP);

Some of the highlights from the report include: Smartphones accounted for 48% of AdMob’s worldwide traffic, up from 35% in February 2009, fueled by heavy application usage on iPhone and Android devices. Although the share of feature phone traffic in AdMob’s network declined from 58% to 35%, the absolute traffic from feature phones still grew 31%.  This means that while the overall traffic from feature phones is growing, traffic from smartphones and mobile Internet devices is growing faster. The mobile Internet device category experienced the strongest growth of the three, increasing to account for 17% of traffic in AdMob’s network in February 2010.  Although the vast majority of traffic in this category comes from the iPod touch, the category also includes devices like the Sony PSP and Nintendo DSi.

wired.com转《纽约时报》消息，Google即将发售自己开发的平板电脑，这款产品是一种“有电脑功能的电子阅读器”。 匿名消息来源称，此产品运行Android系统。Google已与出版商洽谈，以便把书籍和杂志加入此设备。Google平板电脑运行Android而不是传说中的Chrome OS，可能是因为Chrome OS不大会成为一个完整操作系统，而只是提供足够的软体加载浏览器、拜访Google的在线服务。而前者已经足够完备

来自AndroidLib.com的最新统计数 据显示，2010年3月，Android应用市场里的应用增加了9331个。通过历史对比，这些数字更加惊人。比如，去年12月，新增 Android应用为3807个，到1月份为止，新增应用为4458个，2月新增5532个。3月新增9331个。如果Android保持这种增长趋势， 其应用数量很有可能在今天达到5位数，从而对苹果形成有力竞争

As part of my job, I ran into memory leaks issues in Android applications and they are most of the time due to the same mistake: keeping a long-lived reference to a Context.

There are two easy ways to avoid context-related memory leaks. The most obvious one is to avoid escaping the context outside of its own scope. The example above showed the case of a static reference but inner classes and their implicit reference to the outer class can be equally dangerous. The second solution is to use the Application context. This context will live as long as your application is alive and does not depend on the activities life cycle. If you plan on keeping long-lived objects that need a context, remember the application object. You can obtain it easily by calling Context.getApplicationContext() or Activity.getApplication().

In summary, to avoid context-related memory leaks, remember the following: Do not keep long-lived references to a context-activity (a reference to an activity should have the same life cycle as the activity itself) Try using the context-application instead of a context-activity Avoid non-static inner classes in an activity if you don't control their life cycle, use a static inner class and make a weak reference to the activity inside. The solution to this issue is to use a static inner class with a WeakReference to the outer class, as done in ViewRoot and its W inner class for instance A garbage collector is not an insurance against memory leaks

The action bar: is located at the top of the screen to support navigation and highlight important functionalities replaces the title bar (which is often included into it) is best used for actions across your app, like search, refresh and compose can provide a quick link to app homeby tapping the app logo is preferably not contextual, but actions can differ from page to page

Use when You want to bring key actions on screen, so they are in sight. You don't want to hide them under the menu-button. The action bar is best used for common actions like search, refresh and compose. When screen real estate is valuable, consider putting actions in the options menu.

Current Instapaper and former Tumblr developer Marco Arment wonders out loud if Google Android phones can ever achieve the levels of usability and polish Apple’s iPhone has arguably had since day one

Android will continue to exhibit what Google does best: great low-level engineering and tight integration with Google’s other services. But it’s never going to be Apple-like in user experience, polish, or design. Attention to detail, like most facets of truly good design, can’t be (and never is) added later. It’s an entire development philosophy, methodology, and culture

Renderscript is a key new Honeycomb feature which we haven’t yet discussed in much detail

Renderscript is a new API targeted at high-performance 3D rendering and compute operations. The goal of Renderscript is to bring a lower level, higher performance API to Android developers. The target audience is the set of developers looking to maximize the performance of their applications and are comfortable working closer to the metal to achieve this

Renderscript has been used in the creation of the new visually-rich YouTube and Books apps. It is the API used in the live wallpapers shipping with the first Honeycomb tablets.

Google 员工 Damon Horowitz 曾经是多家创业公司的联合创始人。他最近一次创业是 Aardvark 问答网站，然后就被 Google 收购。Damon Horowitz 的有趣之处在于，他拥有一个哲学博士学位，在公司内部大家称他为“哲学家”。

一旦话题涉及到了科技领域的伦理道德，Horowitz 就会问大家是喜欢 iPhone 还是 Android 。当大多数人回答说“喜欢 iPhone ”时，Horowitz 就开玩笑地说你们是“冤大头”，只是因为外表漂亮而选择设备

这个结果很可怕。我们更在乎手机功能的强大，而不在乎这些功能是否在道德框架之内。”

launches the pending intent

checkout flow finishes

Google 的开源政策使 Android 迅速成长，但是在这个过程中，Android 分裂和用户体验差的批评就一直没有停止过。对于各厂商的定制，Google 一直采取放任的态度，因为这对 Google 核心业务的影响不大

但是最近发生的一些事情已经让 Google 不安了，一是 Amazon 发布了自己的 Android Appstore。Amazon是一个很强大的内容提供商，而且可能会推出平板产品。如果 Amazon 和其它硬件厂商合作，或推出自己的 Android 产品，使 Amazon Appstore 与 Android 更好的整合，将会威胁到 Android Market。

这两股潮流结合起来，Android 生态圈面临着失控的危险。我想，这就是 Google 宁可挨着“不开源”的骂名，将 HoneyComb 的代码暂时封闭起来的原因