> For the complete documentation index, see [llms.txt](https://docs.appstoremanager.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appstoremanager.net/documents/phrase-and-lokalise/typical-use-cases.md). # Typical use cases [Phrase](http://phrase.com/) and [Lokalise](https://lokalise.com/) are tools to make and manage translations of any kind.\ App Store Manager works excellently with both of them (and similar tools). In an increasingly globalized world, localization has become vital to software and content development. Adapting products, websites, and applications to different languages, cultures, and markets is crucial for reaching a diverse audience. Developers and content creators often use potent tools like Phrase and Lokalise to streamline the localization process. The App Store Manager links App Store Connect/ Google Play Console and translating tools.\ \ Typical use cases are: * Creation and maintenance of App Store and Google Play Store translations in Phrase and Lokalise. * Transfer of metadata translations via App Store Manager into the respective store * Initial loading of app metadata into Phrase and Lokalise --- # 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.appstoremanager.net/documents/phrase-and-lokalise/typical-use-cases.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.