Android/frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: fix error in merge caused by Ibd81091fc6002a77ce43f553b63facec53f16a38

Browse Source 
Change-Id: Ic46ba89cfd0566fea792f65dfa130bef7010b164
This commit is contained in:
Scott Main
2010-10-04 14:13:54 -07:00
parent ec80d7f311
commit 6ef33cb3b8
1 changed files with 0 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
docs/html/guide/practices/design/responsiveness.jd
View File

@@ -19,19 +19,6 @@ page.title=Designing for Responsiveness
<p><strong>Figure 1.</strong> An ANR dialog displayed to the user.</p>
</div>
<p>It's possible to write code that wins every performance test in the world, but still sends users
in a fiery rage when they try to use the application. These are the applications that aren't
<em>responsive</em> enough &mdash; the ones that feel
sluggish, hang or freeze for significant periods, or take too long to process
input. </p>
<p>In Android, the system guards against applications that are insufficiently responsive for a
period of time by displaying a dialog to the user, called the Application Not Responding (ANR)
dialog. The user can choose to let the application continue, but the user won't appreciate having to
act on this dialog every time he or she uses your application. So it's important to design
responsiveness into your application, so that the system never has cause to display an ANR to the
user. </p>
<p>It's possible to write code that wins every performance test in the world,
but still sends users in a fiery rage when they try to use the application.
These are the applications that aren't <em>responsive</em> enough &mdash; the