Lines Matching full:applications
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
246 <li>Applications may request the permission when the creator of the permission
279 encouraged for all applications that communicate over the network.</p>
281 <p>We have seen some applications use <a
284 accessible by other applications on the device. Instead, you should use an Android IPC
310 by other applications that have the {@link android.Manifest.permission#READ_SMS}
320 affecting applications, regardless of what platform they run on. Android does
321 have platform-level countermeasures that reduce the exposure of applications to
408 could inadvertently leak user data to other applications.</p>
434 normally reserved for Android applications. If you use it, expose
472 <p>Services that will be accessible to multiple applications should be accessed
482 <p>If credentials are to be used only by applications that you create, then you
537 If your IPC mechanism is not intended for use by other applications, set the
541 element. This is useful for applications that consist of multiple processes
546 <p>If your IPC is intended to be accessible to other applications, you can
566 may not be delivered to all applications. If you are sending an intent that must be delivered
571 specifying a non-Null permission with the method call. Only applications with that
574 malicious applications cannot register to receive those messages without
590 <p>A {@link android.app.Service} is often used to supply functionality for other applications to
602 attribute. By doing so, other applications will need to declare
660 is intended for use by other applications, you
664 prevent applications without appropriate permissions from sending an intent to
692 directly within your APK, then they cannot be modified by other applications.
694 {@link dalvik.system.DexClassLoader}. We have seen many instances of applications
736 to want to build modular applications and use dynamic class loading. When
749 <a href="{@docRoot}tools/sdk/ndk/index.html">Android NDK</a>. Applications built
762 Application Sandbox. On Android, all applications run in the Application
