> 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/porting_applications/metadata.md). # Metadata F-Droid and the Play Store need metadata in order for your application to be accepted. This includes descriptions, translations, screenshot, contact and licensing information, icons and others. Where it makes sense, the metadata is translated into different languages. The metadata is important, since it's used to display the app to the user. It's comparable to how appstream files are used by different software centers on the desktop. As part of the packaging step, craft will automatically generate [fastlane](https://f-droid.org/en/docs/All_About_Descriptions_Graphics_and_Screenshots/) metadata for the app based on the existing appstream metadata. Fastlane metadata is required to be accepted into the F-Droid store. When uploading apps to the Play Store, then KDE's Google Play Publishing Service will create the required metadata from the fastlane metadata. This means that normally, you won't need to manually create or edit most of the metadata. If there are problems with the descriptions in F-Droid or the Play Store, make sure the appstream file is correct. Some metadata, for example a banner image for F-Droid, can be added manually. To do that, the files need to be put in a specific folder in the app's repository. For the banner image, this is at `fastlane/metadata/org.kde./en-US/images/featureGraphic.svg`. For other metadata, have a look at the [fastlane documentation](https://f-droid.org/en/docs/All_About_Descriptions_Graphics_and_Screenshots/). --- # 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/porting_applications/metadata.md?ask=&goal= ``` `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.