I'm working on a rather complex web application that includes 3D terrain, 2D mapping, and SVG animations. Both Safari and the Swift app I've built using WkWebKit reload the page after some period of time. Safari pops up a small text block that says: This webpage was reloaded because it was using significant memory. Yes. That's true. It's also true that the M1 Max Mac was in now way experiencing issues, nor were any of the other web pages running in other tabs or windows. The memory limit is simply too low for modern web apps. So far I've not found any way to adjust the parameters in Safari or WkWebView. Apple, help a brother out. It's not 1997 anymore. Web apps are big. And resetting them at some arbitrary point causes more problems that is solves. Anyone have any suggestions? Quinn, any way (other than casting a stone into the one-way abyss of Radar) of getting help from the big A here?

Looking for community feedback on an iOS feature request idea... My company builds business applications that run on iOS, frequently on "stock" (not managed via any kind of MDM) systems. It would be very nice to be able to flag the applications as "Business" or "Mission Critical" or something, and have that temporarily block the display of various modal system popups including: Update Available Turning On Wifi Can Improve Location Accuracy Cellular Data is Turned Off Cellular Data is Turned Off for Wi-Fi is Turned Off for Turn Off Airplane Mode Accessory Not Certified Low Battery: Accessory Storage Almost Full Trust This Computer (and any other blocking pop-ups) I get why iOS has those pop-ups, but there are times and places where they are inappropriate: when someone using an iPad for point-of-sale is trying to ring up a customer; when someone using an iPad as their electronic chart system is trying to navigate an airplane; when an attorney is using an iPad to record a deposition. There may be logic down in the OS that heuristically attempts to prevent those kinds of interruptions, but if so, it's not perfect and they happen. Adding a "Do Not Interrupt" flag - with an appropriate developer-provided explanation for the need - seems a small step to preventing some very aggravating situations. Thoughts? If you like the idea, you might head over to the Feedback page and let them know.