| /sdk/testapps/userLibTest/ |
| project.properties | 2 # Do not modify this file -- YOUR CHANGES WILL BE ERASED!
7 # "ant.properties", and override values to adapt the script to your
10 # To enable ProGuard to shrink and obfuscate your code, uncomment this (available properties: sdk.dir, user.home):
|
| /frameworks/base/docs/html/distribute/users/ |
| know-your-user.jd | 1 page.title=Know Your User
2 page.metaDescription=It\'s essential to understand your users and listen to their input. Here are some ideas.
3 page.image=/distribute/images/know-your-user.jpg
13 A key part of growing your apps' installed base is knowing more about your
14 users — how they discover your app, what devices they use, what they do
15 when they use your app, and how often they return to it.
23 The most obvious way to get to know your users is by reading review comments
24 for your apps on Google Play. While the details provided in reviews will vary
25 greatly, in addition to telling you about what users like and dislike in your
[all...] |
| /frameworks/base/docs/html/distribute/engage/ |
| deep-linking.jd | 2 page.metaDescription=Use search to bring your existing users back into your app.
8 Users who have your app installed might overlook it as a way to get the answers
9 they need. With App Indexing, deep links to your Android app appear in Google Search
10 results so users can get to your native mobile experience quickly, landing exactly
15 Google Search for developers can also help you re-engage your users in other ways
16 — by letting them interact with your app from a voice action, get deep into
17 your app from a search suggestion, or go back to your email reminders in Google Now. </p>
20 <p>Get started by <a href="https://developers.google.com/app-indexing/">indexing your
[all...] |
| /frameworks/base/docs/html/distribute/analyze/ |
| build-better-apps.jd | 2 page.metaDescription=Get actionable insights to optimize your app and learn what works best for your business.
8 While looking at your data in beautiful reports can be fun, the real power of
9 Google Analytics is uncovered when you derive insights from your data. Having
10 Analytics in your app can help you identify where in your app users spend
13 convert, so see if drawing more users to that action has an impact on your
20 Go beyond looking at the sheer number of actions people take in your app.
21 Combine your custom event data with conversion metrics and see what actions
48 <h2 id="flows">Know Your Flows</h2
[all...] |
| /frameworks/base/docs/html/distribute/tools/ |
| localization-checklist.jd | 2 page.metaDescription=Take advantage of the worldwide audience offered by Android and Google Play. Read this checklist to get an overview of how to deliver your product to markets around the world.
17 <li><a href="#test">5. Test your localized app</a></li>
29 Android and Google Play offer you a worldwide audience for your apps, with an
32 can maximize your apps? distribution potential resulting in ratings from
37 Localization involves a variety of tasks throughout your app development
39 key aspects of localization to get your app ready for a successful worldwide
53 countries where you?ll distribute your apps and the languages spoken there.
54 Localizing your apps is particularly important in countries where there is a
60 For international users, you can manage your apps in three main dimensions:
65 affect how your app is displayed
[all...] |
| /abi/cpp/ |
| use_rtti.mk | 1 # To use RTTI, "include abi/cpp/use_rtti.mk" in your target.
|
| /dalvik/dx/tests/116-leb128/ |
| info.txt | 3 The run script requires vogar, so you must have vogar on your $PATH to run this
|
| /developers/build/prebuilts/androidtv/leanback/ |
| CONTRIBUTING.md | 1 # How to become a contributor and submit your own code
5 We'd love to accept your sample apps and patches! Before we can take them, we
14 * If you work for a company that wants to allow you to contribute your work,
20 accept your pull requests.
26 1. Create your change to the repo in question.
27 * Fork the desired repo, develop and test your code changes.
28 * Ensure that your code is clear and comprehensible.
29 * Ensure that your code has an appropriate set of unit tests which all pass.
31 1. The repo owner will review your request. If it is approved, the change will
39 1. Create your own repo for your app following this naming convention
[all...] |
| /developers/build/prebuilts/androidtv/sample-inputs/ |
| CONTRIBUTING.md | 1 # How to become a contributor and submit your own code
5 We'd love to accept your sample apps and patches! Before we can take them, we
14 * If you work for a company that wants to allow you to contribute your work,
20 accept your pull requests.
26 1. Create your change to the repo in question.
27 * Fork the desired repo, develop and test your code changes.
28 * Ensure that your code is clear and comprehensible.
29 * Ensure that your code has an appropriate set of unit tests which all pass.
31 1. The repo owner will review your request. If it is approved, the change will
39 1. Create your own repo for your app following this naming convention
[all...] |
| /developers/build/prebuilts/androidtv/visual-game-controller/ |
| CONTRIBUTING.md | 1 # How to become a contributor and submit your own code
5 We'd love to accept your sample apps and patches! Before we can take them, we
14 * If you work for a company that wants to allow you to contribute your work,
20 accept your pull requests.
26 1. Create your change to the repo in question.
27 * Fork the desired repo, develop and test your code changes.
28 * Ensure that your code is clear and comprehensible.
29 * Ensure that your code has an appropriate set of unit tests which all pass.
31 1. The repo owner will review your request. If it is approved, the change will
39 1. Create your own repo for your app following this naming convention
[all...] |
| /development/libraries/stereocamera/ |
| README.txt | 4 To use the libraries, simply copy them as static libraries into your project.
|
| /development/samples/training/basic/ActivityLifecycle/ |
| ant.properties | 4 # integral to the build system of your project.
9 # 'source.dir' for the location of your java source folder and
10 # 'out.dir' for the location of your output folder.
14 # 'key.store' for the location of your keystore and
|
| build.properties | 4 # integral to the build system of your project.
9 # 'source.dir' for the location of your java source folder and
10 # 'out.dir' for the location of your output folder.
14 # 'key.store' for the location of your keystore and
|
| /external/chromium-trace/catapult/third_party/gsutil/third_party/protorpc/demos/quotas/backend/ |
| README | 4 It is possible to set up a quota service in your own application by following
11 a. Change the application to the name of your application.
12 b. Change the version to one that is appropriate for your application.
14 3) Edit quotas.js so that its settings are appropriate for your application.
|
| /external/curl/packages/Linux/RPM/ |
| README | 4 jobs. You need to fill in your own name and email at least.
|
| /external/eigen/blas/ |
| README.txt | 5 type 'make blas' from within your build dir.
|
| /external/skia/tools/ |
| OverwriteLine.h | 4 // Print this string to reset and clear your current terminal line.
|
| /external/tlsdate/m4/ |
| bottom.m4 | 8 #error "You should include config.h as your first include file"
|
| /external/webrtc/talk/app/webrtc/androidtests/ |
| ant.properties | 4 # integral to the build system of your project.
9 # 'source.dir' for the location of your java source folder and
10 # 'out.dir' for the location of your output folder.
14 # 'key.store' for the location of your keystore and
|
| /external/webrtc/webrtc/examples/androidapp/ |
| ant.properties | 4 # integral to the build system of your project.
9 # 'source.dir' for the location of your java source folder and
10 # 'out.dir' for the location of your output folder.
14 # 'key.store' for the location of your keystore and
|
| /external/webrtc/webrtc/examples/androidtests/ |
| ant.properties | 4 # integral to the build system of your project.
9 # 'source.dir' for the location of your java source folder and
10 # 'out.dir' for the location of your output folder.
14 # 'key.store' for the location of your keystore and
|
| /frameworks/av/media/utils/ |
| README | 3 Consider adding your utility class/function here if it will
|
| /frameworks/base/docs/html/guide/topics/security/ |
| index.jd | 3 page.landing.intro=Configure the security of your application.
|
| /frameworks/base/docs/html/training/ |
| best-permissions-ids.jd | 9 and identifiers properly in your apps.</p
|
| best-security.jd | 9 keep your app's data secure.</p
|
