Group items tagged

We compared these findings with that of our tests of Apple's mobile Safari browser on the iPhone 4. The results show that the Android device delivers significantly faster JavaScript execution than the iPhone, scoring over three times better on V8 and almost twice as fast on SunSpider

你可以在 EyE-Sight 站点了解到更多关于这一功能的消息，也可以通过下面的视频来了解更多细节。 继续观看视频：

手势相对于无趣的触摸和点击来说，给用户带来了的动态感。但是，缺乏一致性，操作的不易发觉，加上极易触发的不可恢复的操作，使得整个系统的可用性遭到损害。  我们迫切的需要回到基本原则，为这些系统开发可用性指南，这份指南应该基于交互设计的坚实原则，而不是某个公司在人机交互指导中的奇思，或者一些开发者的妙想

简单的宣称你的用户界面“有趣”和“自然”并不能证明你的界面可用，当你的用户使用软件时，对于如何操作茫然无措，并不是什么好玩的事情

1.Android 许多重要的功能是不可见的，除非你长按界面上的某东西，我经常对此感到懊恼

Information about the current build, extracted from system properties.

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

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

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

最近，专门调查分析智能手机程序使用情况的Flurry.com公布了一幅有意思程序保留时间对比图。Android程序安装3个月后的保留比例和iPhone在30天后的比例相当

可能的原因？Flurry的看法是： iPhone的软件选择更多 Android用户平均年龄更大，玩机热情不如以往 Android用户更宽容，更善于利用现有程序

面向杂志、报纸数字化发布的德国软件公司 Neofonie GmbH 近日发布了自己的平板电脑——WePad 以配合自家的内容发布平台 WeMagazine。

Neofonie 表示产品预期在今年 4 月发售，有可能早于 iPad 在欧洲的发售日期。WePad 的规格表看起来确实很美，增加了很多 iPad 缺失的重要功能，但至关重要的软件系统最终表现如何还无从得知。对于一家基本没有操作系统开发经验的小公司而言，这是一个相当有挑战性的任务。

It allows third-party application servers to send lightweight messages to their Android applications. The messaging service is not designed for sending a lot of user content via the messages. Rather, it should be used to tell the application that there is new data on the server, so that the application can fetch it. C2DM makes no guarantees about delivery or the order of messages. So, for example, while you might use this feature to tell an instant messaging application that the user has new messages, you probably would not use it to pass the actual messages. An application on an Android device doesn’t need to be running to receive messages. The system will wake up the application via Intent broadcast when the the message arrives, as long as the application is set up with the proper broadcast receiver and permissions.

It uses an existing connection for Google services. This requires users to set up their Google account on their mobile devices.

C2DM imposes the following limitations: The message size limit is 1024 bytes. Google limits the number of messages a sender sends in aggregate, and the number of messages a sender sends to a specific device

Apple tends to do that a lot. It’s deeply ingrained in their culture, priorities, and product development practices. In brief, their philosophy seems to be to ship only what’s great and leave out the rest. That’s why, instead of having a bad copy-and-paste implementation for the iPhone’s first two years, we just didn’t have one at all

Android as a platform, both in hardware and software, doesn’t reflect this. Nearly every hardware and software release has major shortcomings or rough edges. Many details and design decisions are lacking, wrong, or inexplicable. Neither Google nor the current Android device manufacturers embody the part of Apple’s culture that allows them to release a great product on day one. They have a different pattern: It’s always getting better. We’re always supposedly one or two releases from it being really great.

I never make technology-buying decisions based on future promises, rumors, or potential. I let other people be the bleeding-edge extremely early adopters, and I stick with what I know will work and stay out of my way. I don’t buy things that are “getting better”, because they usually don’t. Whatever caused them to be lacking in their current release will usually prevent them from being great in future releases. I buy things that are great today. They’re usually things that have been great since day one. And, more often than not, they’re Apple products.

Intent picMessageIntent = new Intent(android.content.Intent.ACTION_SEND);  picMessageIntent.setType("image/jpeg");    File downloadedPic =  new File(      Environment.getExternalStoragePublicDirectory(      Environment.DIRECTORY_DOWNLOADS),      "q.jpeg");    picMessageIntent.putExtra(Intent.EXTRA_STREAM, Uri.fromFile(downloadedPic));  

For completeness we really should handle the possibility of the task getting cancelled. This can happen when the user navigates away from the app and the task is killed before its completed. This will cause the onPostExecute() method to not be called and so the onRefreshComplete() method won’t be called. Depending on how the user navigates through the app, they could return to this activity without going through the complete onCreate() lifecycle, and you’ll end up with the screen still showing the “loading” progress message in the header. This is common when using tabs between multiple ListViews. Also, the documented best practices for implementing an AsyncTask says that in long running background work you should periodically check if the task has been cancelled and try to gracefully quit your work and exit. So let’s get all of that in there.