Dear Apple, Following your guide on Refactor Your Targets to Improve Parallelism, we've recently introduced modularity into our iOS app. We were able to create granular modules containing features and shared functionality. The dilemma we encountered was what should be the type of the modules? Is it static library or dynamic framework? Because we wanted to consume our internal libraries from multiple targets, and we didn't want it to become part of each and every executable inflating the size of our app and creating duplication (which is the case with static libraries.), we went full power with dynamic frameworks. However, the significant amount of dynamic modules has drastically increased the launch times of our app. The tradeoff we're not ready to live with. Is there any other module type that can be consumed directly from multiple targets, not being copied into executables on the one hand but not affecting the app launch times on the other? Any guidance would be appreciated. Regards, German