Skip to content

Commit 6ef33cb

Browse files
committed
docs: fix error in merge caused by Ibd81091fc6002a77ce43f553b63facec53f16a38
Change-Id: Ic46ba89cfd0566fea792f65dfa130bef7010b164
1 parent ec80d7f commit 6ef33cb

File tree

1 file changed

+0
-13
lines changed

1 file changed

+0
-13
lines changed

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

Lines changed: 0 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -19,19 +19,6 @@ page.title=Designing for Responsiveness
1919
<p><strong>Figure 1.</strong> An ANR dialog displayed to the user.</p>
2020
</div>
2121

22-
<p>It's possible to write code that wins every performance test in the world, but still sends users
23-
in a fiery rage when they try to use the application. These are the applications that aren't
24-
<em>responsive</em> enough &mdash; the ones that feel
25-
sluggish, hang or freeze for significant periods, or take too long to process
26-
input. </p>
27-
28-
<p>In Android, the system guards against applications that are insufficiently responsive for a
29-
period of time by displaying a dialog to the user, called the Application Not Responding (ANR)
30-
dialog. The user can choose to let the application continue, but the user won't appreciate having to
31-
act on this dialog every time he or she uses your application. So it's important to design
32-
responsiveness into your application, so that the system never has cause to display an ANR to the
33-
user. </p>
34-
3522
<p>It's possible to write code that wins every performance test in the world,
3623
but still sends users in a fiery rage when they try to use the application.
3724
These are the applications that aren't <em>responsive</em> enough &mdash; the

0 commit comments

Comments
 (0)