> For the complete documentation index, see [llms.txt](https://docs.appmysite.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmysite.com/app/download/android/android-app-visibility.md).

# Android app visibility

### How long before your app is visible in the Play Store?

Google Play takes upto 1 week to start showing your app in search results. If a week has already passed, we recommend reaching out to their support team via email. 

When you search on Google, Google Play search takes multiple factors into account, such as app titles, developer names, and app descriptions. 

{% hint style="warning" %}
To help your app get discovered, make sure you’re following best practices for [creating a comprehensive store listing](https://support.google.com/googleplay/android-developer/answer/4448378).
{% endhint %}

#### Open your app directly using the bundle identifier

If your app is not yet appearing in search results, you can still access it directly using the bundle identifier.

**Steps to open the app using the bundle ID:**

* Open a browser on your mobile or desktop device
* Enter the following URL in the address bar:\
  `https://play.google.com/store/apps/details?id=your.bundle.identifier`
* Replace `your.bundle.identifier` with your actual app’s bundle ID (e.g., com.example.myapp)
* Hit Enter to open your app’s Play Store listing directly

{% hint style="success" %}
Even if your app doesn't show up in Play Store search right away, you can share and access it directly using its bundle identifier.
{% endhint %}

With new apps being published every day and ongoing changes to how search results are ranked, you can expect search results to change regularly. Also, people can get different search results depending on their device, location, mobile carrier, support for available features, and more.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.appmysite.com/app/download/android/android-app-visibility.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.