| /frameworks/base/docs/html/guide/practices/app-design/ |
| D | index.jd | 4 …applications on a new platform, you first learn what APIs are available and how to use them. Later…
6 … help you learn the nuances of Android and get started building great applications more quickly, T…
8 …applications offer an outstanding user experience, in addition to a compelling technical feature s…
15 applications that are fast, responsive, and seamless. </p>
20 <li><a href="seamlessness.html">Designing for Seamlessness</a> (coexisting with other applications)…
|
| D | seamlessness.jd | 26 other applications or dialogs, inadvertent loss of data, unintended blocking,
28 your applications run and the system interactions that can affect your
30 interacts seamlessly with the system and with other applications. </p>
54 used by other applications, you should expose it via a ContentProvider, rather
58 with the system and other applications. The Android system is designed to treat
59 applications as a sort of federation of loosely-coupled components, rather than
62 by allowing you to integrate cleanly and seamlessly with other applications, and
78 Way" is to do just that: Android applications that accept or edit input should
92 applications to understand your data format; if you change that format, you'll
93 break any other applications that aren't similarly updated.</p>
[all …]
|
| /frameworks/base/docs/html/guide/topics/ui/accessibility/ |
| D | index.jd | 52 make their applications more accessible.</p>
56 modes. Accessibility services can provide these enhancements for all applications, a set of
57 applications or just a single app.</p>
59 <p>The following topics show you how to use the Android framework to make applications more
72 <dd>A checklist to help developers ensure that their applications are accessible.</dd>
77 <dd>How to use API features to build services that make other applications more accessible for
|
| /frameworks/base/docs/html/guide/topics/media/ |
| D | index.jd | 13 href="http://android-developers.blogspot.com/2010/06/allowing-applications-to-play-nicer.html">
14 <h4>Allowing applications to play nice(r) with each other: Handling remote control
26 mistakes in the way they interact with the Android system and with other applications</p>
43 applications. In later lessons, you dive deeper and learn how to control the camera hardware
51 audio focus caused by the system or other applications.</p>
|
| /frameworks/multidex/instrumentation/ |
| D | README.android | 2 for multiple dex applications.
5 of applications with multiple dexes.
|
| D | README.txt | 2 for multiple dex applications.
5 of applications with multiple dexes.
|
| /frameworks/base/docs/html/about/versions/ |
| D | android-2.3.3.jd | 52 applications to interact with more types of tags in new ways.</p>
54 <p>A new, comprehensive set of APIs give applications read and write access
72 <p>Advanced tag dispatching now gives applications more control over how and
74 used a single-step intent dispatch to notify interested applications that a tag
77 other applications (<code>android.nfc.NfcAdapter.enableForegroundDispatch()</code>).
102 <li>{@link android.nfc.tech.TagTechnology}, an interface that gives applications
117 <p>To use the NFC API, applications must request permission from the user by
122 their applications are not discoverable to users whose devices do not support
133 connections. This lets applications communicate with simple devices that may not
142 <li>A new {@link android.graphics.BitmapRegionDecoder} class lets applications
[all …]
|
| D | android-2.3-highlights.jd | 129 <h3>Control over applications</h3>
134 tab displays a list of active applications and the storage and memory being used
141 <p>An updated set of standard applications lets the user take new approaches to
182 download manager facility in the system that any other applications can use, to
194 let developers bring new types of applications to the Android
208 common operations faster and more efficient for all applications. Of particular
215 applications. </li>
218 distribution. The changes improve responsiveness for all applications, but
234 <p>Native libraries exposed by the platform let applications handle the same
258 that gives applications access to powerful audio controls and effects from
[all …]
|
| D | android-3.0-highlights.jd | 66 …action, navigation, and customization and makes them available to all applications — even th…
70 <p>Across the system and in all applications, users have quick access to notifications, system stat…
74 …verflow dropdown menu, which users frequently access in a similar manner in most applications. </p>
85 …me screen also offers a familiar launcher for access to all installed applications, as well as a S…
97 …roid and it is central to the Android 3.0 experience. As users launch applications to handle vario…
130 <p>The Android 3.0 platform includes an updated set of standard applications that are designed for …
153 <p>The Android 3.0 platform is designed specially to meet the unique needs of applications on devic…
174 …applications into subcomponents called Fragments, then combine them in a variety of ways to create…
180 … that developers can use to quickly add new types of content to their applications. The new UI wid…
196 …nstance. The Action Bar lets developers expose more features of their applications to users in a f…
[all …]
|
| D | android-2.3.4.jd | 48 <p>Android 2.3.4 provides the same framework API to applications as Android 2.3.3
56 connected peripherals with applications running on the platform. The capability
58 API exposed to applications. Peripherals that attach to Android-powered devices
65 lets applications discover, communicate with, and manage a variety of device
67 parts of the Android platform that are not directly exposed to applications in
73 applications developed against Android 2.3.4 will run properly on devices
118 <p>For a full discussion of how to develop applications that interact with USB
123 their applications are not available to users whose devices do not provide the
|
| D | android-2.3.jd | 51 developers build internet telephony applications. Using the API, applications can offer
57 package. The key class is {@link android.net.sip.SipManager}, which applications
59 audio calls. Once an audio call is established, applications can mute calls,
65 applications should use the {@link android.net.sip.SipManager#isApiSupported
69 <p>To use the SIP API, applications must request permission from the user by
75 their applications are not discoverable to users whose devices do not include
92 platform notifies applications by broadcasting an Intent, appending the tag's
95 tag by Intent, applications extract the NDEF messages, store them, alert the
113 applications can call {@link android.nfc.NfcAdapter#isEnabled isEnabled()} to
117 <p>To use the NFC API, applications must request permission from the user by
[all …]
|
| D | android-3.1.jd | 52 integrating connected peripherals with applications running on the platform.
55 interactions. Using the APIs, developers can create applications that are able to
114 their applications are not availabe to users whose devices do not provide the
133 <p>For complete information about how to develop applications that interact with
137 <p class="note">To look at sample applications that use the USB host API, see <a
144 <p>Android 3.1 exposes a new MTP API that lets applications interact directly
185 specification. Methods in the class let applications get a device’s
189 5.3.1 of the MTP specification. Methods in the class let applications get an
200 these capabilities to let users interact with their applications using mice,
257 motion data to applications. For a full list of axes and their intended
[all …]
|
| D | android-3.1-highlights.jd | 159 <p>A new high-performance Wi-Fi lock lets applications maintain
176 <p>The Android 3.1 platform includes an updated set of standard applications
274 applications running on the platform. The API provides a way to interact across
281 applications that the hardware is available.</p>
296 <p>To learn more about how to develop applications that interact with
303 an API that lets applications manage connected peripherals. On devices that
304 support host mode, applications can use the API to identify and communicate with
308 <p>To learn more about how to develop applications that interact with
316 these capabilities to let users interact with their applications using mice,
326 axes that applications can use from a given input source, such as X, Y, Hat X,
[all …]
|
| D | android-2.2.jd | 80 <p>The Android platform now allows applications to request installation onto the
85 their applications by means of a new attribute of <code><manifest></code>
99 <p>By default, the system installs all applications onto the device's internal
101 means that the system will always install legacy applications onto internal
109 suitable for all applications, particularly because the external media may be
114 application, including a discussion of what types of applications should and
122 applications can use to backup and restore user data, to ensure that users can
153 <li>The platform provides new speech-recognition APIs that allow applications to have a richer inte…
174 administrator" applications that can control security features of the device,
184 <li>New UI modes "car mode" and "night mode" and {@link android.app.UiModeManager} let applications…
[all …]
|
| /frameworks/opt/telephony/src/java/com/android/internal/telephony/ |
| D | SmsApplication.java | 357 Collection<SmsApplicationData> applications, String packageName) { in getApplicationForPackage() argument
362 for (SmsApplicationData application : applications) { in getApplicationForPackage()
388 Collection<SmsApplicationData> applications = getApplicationCollectionInternal(context, in getApplication() local
402 applicationData = getApplicationForPackage(applications, defaultApplication); in getApplication()
414 applicationData = getApplicationForPackage(applications, defaultPackage); in getApplication()
418 if (applications.size() != 0) { in getApplication()
419 applicationData = (SmsApplicationData)applications.toArray()[0]; in getApplication()
524 Collection<SmsApplicationData> applications = getApplicationCollection(context); in setDefaultApplicationInternal() local
526 getApplicationForPackage(applications, oldPackageName) : null; in setDefaultApplicationInternal()
527 SmsApplicationData applicationData = getApplicationForPackage(applications, packageName); in setDefaultApplicationInternal()
[all …]
|
| /frameworks/base/docs/html/guide/practices/ |
| D | seamlessness.jd | 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>
[all …]
|
| /frameworks/base/docs/html/training/sharing/ |
| D | index.jd | 24 <p>One of the great things about Android applications is their ability to communicate and
29 applications using {@link android.content.Intent} APIs and the {@link
38 applications with intents.</dd>
|
| /frameworks/base/docs/html/training/camera/ |
| D | index.jd | 48 leveraging existing camera applications. In later lessons, you dive deeper
56 <dd>Leverage other applications and capture photos with just a few lines of code.</dd>
58 <dd>Leverage other applications and record videos with just a few lines of code.</dd>
|
| /frameworks/base/docs/html/training/articles/ |
| D | security-tips.jd | 71 applications.</p>
76 the ability to limit data access to particular applications, nor do they
114 to your own application or exported to allow access by other applications.
116 applications with access to your {@link android.content.ContentProvider}, mark them as <code><a
124 that will be exported for use by other applications, you can specify a single
177 <p>Because Android sandboxes applications from each other, applications must explicitly
202 applications, such as a {@link android.content.ContentProvider}.
207 protection level</a> on permissions for IPC communication between applications
224 uncommon for most applications, because the <a
233 to the user and only allow access by applications signed by the same developer
[all …]
|
| /frameworks/base/tests/AccessoryDisplay/ |
| D | README | 6 There are two applications with two distinct roles: a sink
42 These applications should be installed on two separate Android
47 When connected, the applications should automatically launch
|
| /frameworks/base/docs/html/guide/topics/manifest/ |
| D | supports-gl-texture-element.jd | 10 <p style="padding-top:1em;">Google Play filters applications according
58 (such as Google Play) or applications can check your application's
67 are strings, applications are free to declare other formats as needed.</p>
148 <p>Google Play filters the applications that are visible to users, so that
149 users can see and download only those applications that are compatible with
150 their devices. One of the ways it filters applications is by texture
172 <p>When a user searches or browses for applications on Google Play,
|
| D | permission-element.jd | 22 limit access to specific components or features of this or other applications.
96 applications access to isolated application-level features, with
97 minimal risk to other applications, the system, or the user.
122 <td>A permission that the system grants only to applications that are
126 for most needs and works regardless of exactly where applications are
129 vendors have applications built into a system image and need
|
| /frameworks/base/docs/html/training/design-navigation/ |
| D | index.jd | 13 … an Android device for a better understanding of the context in which Android applications run.</p>
15 …actionbar.html">pattern docs</a> at Android Design), used across most applications in devices runn…
24 …applications, in roughly chronological order. After going through the lessons in this class, you s…
|
| /frameworks/base/docs/html/google/play/licensing/ |
| D | index.jd | 9 applications that you publish on Google Play. With Google Play Licensing, your application can
20 <p>The licensing service is a secure means of controlling access to your applications. When an
32 for paid applications that wish to verify that the current user did in fact pay for the application
41 your applications, read the following documents:</p>
|
| /frameworks/base/docs/html/guide/practices/ui_guidelines/ |
| D | activity_task_design.jd | 50 <li>Activities are the main building blocks of Android applications. </li>
51 …our own activities, you are free to re-use activities from many other applications through intents…
52 <li>You can enable activities in your application to be started from intents in other applications.…
114 This document draws examples from several Android applications,
115 including default applications (such as Dialer) and Google
116 applications (such as Maps). You can try out the examples yourself in
119 applications used in this document.
145 <h3 id=applications>Applications</h3>
153 of applications that may include email, calendar, browser, maps, text
160 typically in a sliding drawer which displays applications as icons,
[all …]
|