Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit fc7f3919 authored by Scott Main's avatar Scott Main Committed by Android Git Automerger
Browse files

am b3a5b85a: am 6ef33cb3: docs: fix error in merge caused by... 

am b3a5b85a: am 6ef33cb3: docs: fix error in merge caused by Ibd81091fc6002a77ce43f553b63facec53f16a38

Merge commit 'b3a5b85a' into gingerbread-plus-aosp

* commit 'b3a5b85a':
  docs: fix error in merge caused by Ibd81091fc6002a77ce43f553b63facec53f16a38
parents 6a02ba01 b3a5b85a

docs/html/guide/practices/design/responsiveness.jd

+0 −13
Original line number Diff line number Diff line
@@ -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