> For the complete documentation index, see [llms.txt](https://docs.novaflowos.com/start/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.novaflowos.com/start/kde-developer-platform/readme/packaging/android/googleplay/_index.md).

# Introduction

This tutorial will guide you in publishing a new application on [Google Play](https://play.google.com/store/apps).

We assume that the application you want to publish on Google Play is already packaged and published in one of KDE's F-Droid repositories. If not then read the tutorial on [packaging and publishing applications for Android](/start/kde-developer-platform/readme/packaging/android/index-1.md).

If, in the past, your application was published on Google Play by uploading APKs then read the tutorial on [publishing new releases of old applications on Google Play](/start/kde-developer-platform/readme/packaging/android/googleplay/releasing-old-apps.md).


---

# 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.novaflowos.com/start/kde-developer-platform/readme/packaging/android/googleplay/_index.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.