> For the complete documentation index, see [llms.txt](https://hardartcore.gitbook.io/in-app-updates/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hardartcore.gitbook.io/in-app-updates/getting-started.md). # Hierarchy The source of the asset is inside: **Assets/hardartcore/In-App Updates** folder. You can find everything you needed there. ### Demo folder Inside **Demo** folder you will find a simple demo scene with a basic implementation with subscribing for all the events from **UpdateManager** class and showing information about the download process when there is an update available ### Plugins folder Inside **Plugins** folder you will find the native **Android Java .aar** library with a txt file with **proguard** rules which you should include in your **proguard** file if that option is enabled for you. ### Prefabs folder Inside **Prefabs** folder you will find two prefab files: **UpdateManager** & **AutoUpdateManager**. The difference between both prefabs is that **AutoUpdateManager** will take care for everything, you just need to drag & drop it in your Scene and you are good to go. However if you need to customize the process of informing the user about the update, show progress of bytes downloaded vs total and etc. you should use **UpdateManager** which will let you customize the user experience. You can check the **DemoScene** inside **Demo** folder to see a sample implementation of that. ### Scripts folder Inside **Scripts** folder you will find both **AndroidUpdateManager.cs** & **AutoUpdater.cs**. That's where the magic happens! --- # 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://hardartcore.gitbook.io/in-app-updates/getting-started.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.