Lines Matching refs:applications

27 other applications or dialogs, inadvertent loss of data, unintended blocking,
29 your applications run and the system interactions that can affect your
31 interacts seamlessly with the system and with other applications. </p>
55 used by other applications, you should expose it via a ContentProvider, rather
59 with the system and other applications. The Android system is designed to treat
60 applications as a sort of federation of loosely-coupled components, rather than
63 by allowing you to integrate cleanly and seamlessly with other applications, and
79 Way" is to do just that: Android applications that accept or edit input should
93 applications to understand your data format; if you change that format, you'll
94 break any other applications that aren't similarly updated.</p>
97 applications via a clean, well-thought-out, and maintainable API. Using a
101 by the ContentProvider, and this without affecting other applications.</p>
170 blend in nicely. Users are jarred by applications which contrast with the user
174 you're starting from the same UI base as all the other applications. For all
200 <p>That's why you should always code your applications to minimize network
204 inverse case though: applications that are usable some of the time, but
225 When building your applications, keep that in mind.  Don't make assumptions
236 radio;  that's why it's important to write your applications to do as little