Lines Matching full:application
25 <p>Even if your application is fast and responsive, certain design decisions can
30 application. In short, you should strive to develop an application that
33 <p>A common seamlessness problem is when an application's background process
36 you are building and testing your application in isolation, on the emulator.
37 However, when your application is run on an actual device, your application may
39 it could end up that your application would display it's dialog behind the
40 active application, or it could take focus from the current application and
42 phone call, for example). That behavior would not work for your application or
45 <p>To avoid these problems, your application should use the proper system
48 notifications, your application can signal the user that an event has
54 and other lifecycle methods. Or, if your application exposes data intended to be
74 your application being killed.</p>
76 <p>If the user was editing data in your application when the other Activity
77 appeared, your application will likely lose that data when your application is
81 fashion. When the user revisits the application, she should be able to
84 <p>A classic example of a good use of this behavior is a mail application. If the
85 user was composing an email when another Activity started up, the application
91 data. While it's possible to expose certain kinds of application to the world
105 <p>If the user is running an application (such as the Phone application during a
111 the background. Doing so will interrupt whatever application is currently
115 application does, this could be bad news.</p>
120 what your application has to show him.</p>
128 <p>If your application needs to perform some expensive or long-running
130 dreaded "Application Not Responding" dialog from being displayed to the user,
131 with the ultimate result being the fiery demise of your application.</p>
138 the application is hung and offers to kill it for the user.</p>
149 <p>Any application worth using will probably have several different screens.
155 your application. However, that's not quite accurate: where an Applet subclass
157 as one of potentially several entry points to your application. The only
162 <p>So, when designing your application, think of your application as a federation
164 run, and as a nice side effect also plays nicely with Android's application
189 application looks great on any device.</p>
227 in restricting your application so that it can only be used on those devices.
239 Minimizing the amount of processor time your application uses really comes
