What you need to know
- A new upgrade to Apple's iPhone and iPad software will bring big performance updates to some apps.
- Developers can now request access to more RAM on certain devices.
- It could mean more powerful apps can unlock the full potential of devices like the M1 iPad Pro with 16GB of RAM.
A new developer tool (opens in new tab) noted by MacRumors will let developers request access to more RAM on iPhone and iPad. Currently, apps are limited by Apple, on the iPad apps can only use 5GB of RAM, despite the fact Apple's M1 iPad Pro comes with as much as 16GB of RAM. Apple states:
It seems from the description that apps might have access to differing amounts of RAM depending on the device at play, and developers can use the above function to find out how much is available on any given device.
In May we reported how apps across iPadOS 15 are limited to 5GB of RAM, leading to much speculation that Apple would eventually unlock more RAM for apps on iPad, as this latest beta feature now confirms.
Apple released beta 2 of iPadOS 15 to developers Thursday, you can find out how to install iPadOS 15 developer beta 2 on your iPad here.
Stephen Warwick has written about Apple for five years at iMore and previously elsewhere. He covers all of iMore's latest breaking news regarding all of Apple's products and services, both hardware and software. Stephen has interviewed industry experts in a range of fields including finance, litigation, security, and more. He also specializes in curating and reviewing audio hardware and has experience beyond journalism in sound engineering, production, and design.
Before becoming a writer Stephen studied Ancient History at University and also worked at Apple for more than two years. Stephen is also a host on the iMore show, a weekly podcast recorded live that discusses the latest in breaking Apple news, as well as featuring fun trivia about all things Apple. Follow him on Twitter @stephenwarwick9
Thank you for signing up to iMore. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.