These frameworks were shipped as “fat” frameworks, meaning a vendor would build a single framework that contained all the required architectures. The problem stems from the previous way of linking binary frameworks. This all sounds great, so what is the problem with having Macs and iPhones share the same CPU architecture? For users, they are able to use any iPhone app on their Mac.Īdditionally, there are significant performance and power efficiency improvements in M1 compared to any existing architectures.
![latest xcode version latest xcode version](https://i.stack.imgur.com/udVjw.jpg)
They can address an entire new market without doing any work. For developers, their iOS apps can now run on Macs with very few changes.
LATEST XCODE VERSION CODE
This allows Apple’s teams to share code and test coverage.
![latest xcode version latest xcode version](https://renewsingles482.weebly.com/uploads/1/2/6/5/126565413/299625346.png)
Recently, mobile developers have struggled when integrating binary frameworks in their iOS apps.