Lines Matching full:apis
13 <li><a href="#Using">Using the v4 Library APIs</a></li>
31 application in order to use APIs that are either not available for older platform versions or that
32 offer "utility" APIs that aren't a part of the framework APIs. The goal is to simplify your
33 development by offering more APIs that you can bundle with your application so you can
39 support classes to work with v13 APIs). The minimum version is indicated
62 <li>Support for Accessiblity APIs:
100 <li>Changes to Fragment APIs:
102 <li>Added new APIs to control the visibility of new menus.</li>
103 <li>Added custom animation APIs.</li>
104 <li>Added APIs in <code>FragmentActivity</code> to retain custom,
152 android.view.MotionEvent} APIs</li>
154 android.view.VelocityTracker} APIs</li>
156 android.view.ViewConfiguration} APIs</li>
157 <li>All new APIs (available only in the support library) that allow you to create UIs
179 <p>These are exactly the same as the APIs added to the v4 support library, but rely on
181 Android 3.2 and higher (all other APIs in the v4 library are already available with API level
269 <p>Your application is now ready to use the library APIs. All the
270 provided APIs are available in the {@code android.support} package (for
273 <p class="note"><strong>Tip:</strong> To see the library APIs in action, take a look at the sample
286 <h2 id="Using">Using the v4 Library APIs</h2>
289 beyond, plus some updated version of existing classes, and even some APIs that currently don't
305 <p>For each of the classes above (and others not listed), the APIs work almost exactly the same
307 the online documentation for information about the supported APIs. There are some
352 <p>The libraries currently do not provide reference documentation for the included APIs. To generate
