REVIEW Unity SDK Architecture and suggests Performance Enhancement

I'm seeking expert assistance to review the architecture of our Unity SDK and optimize its performance. This includes: 1. Reviewing and Enhancing GUI Elements: - I'm aiming for both performance optimization and functionality enhancement of the GUI elements built into our Unity game engine. Expertise in Unity user interface design will be highly valued. 2. Optimizing SDK Integration: - There's also a need to review and optimize how our SDK integrates into another Unity game. Therefore, having a deep understanding of Unity SDK integration is crucial. 3. Backend Configuration Review: - The backend, which runs on Go, will also need to be reviewed. As such, significant experience with Go and backend configuration is required. 4. Performance Optimization: - The primary focus of the project includes improving the speed and responsiveness of our Unity SDK. A proven history of successful performance optimization in Unity is a must. By the end of this project, we aim to have an optimally performing, streamlined Unity SDK with a seamless integration into the Unity game. Please, only experienced Unity developers with a background in performance optimization should bid. Detailed Description: Our core product is an SDK built on the unity game engine. It is a product on its own with many GUI elements on the unity side as well as a backend running on Go. This unity SDK is then integrated into another Unity game. As a result this created a slightly complicated structure as both the unity game and unity sdk with GUI elements need to run without consuming too much of memory on download as well as memory on runtime. We would like a review to be done on our unity side architecture to evaluate the following: - General architecture keeping our above product in mind. - Resource utilization like all sprites, animation, sound etc. Evaluating how sprites and animations and being used from an architecture point of view - Texture architecture and utilization especially with a view towards technical decisions like png vs svg, rigging animation vs sprite animation, sprite design keeping scenes and prefabs in mind. Here again, we need to keep in mind that the unity game may have its own texture architecture and our unity SDK needs to have a structure which does not create conflict with the unity game. - Scalability of the architecture- we want to add more content which will be heavy on texture and animations. We would like to ensure that this does not become a bottleneck where run time memory becomes very high. - Analyze how memory is allocated and deallocated throughout the runtime of both the Unity game and the SDK. - Review the codebase of SDK for performance bottlenecks and areas of improvement. - Review how we load assets and data on-demand. - During review, you may come across some more nitty-gritties which we expect you to thoroughly cover and share the report.