Below is the text I will be sending to iPad Today. I am sure that there will be as many ways of describing the problem as there are members of this forum but it is a start. Feel free to copy, paste, bin or modify for your own use as you see fit.
Chris
<clip>
Given your involvement in all things iPad and iOS-related, I thought you might be interested in a serious iOS 7 bug that has somehow managed to escape the attention of the tech press. This bug is widely discussed in the following Apple forum (https://discussions.apple.com/thread/5380124) and has reached 20 pages of discussion and references at least two other threads discussing the same problem.
The problem
The issue is an inability of iOS 7 to adequately maintain the state of apps that have been suspended when you swap to another app. When returning to that suspended app there is often a refresh that may take several seconds and/or may not fully restore the state of the app. This all worked fine in iOS 6. Some examples:
When coming back to iBooks from another app, iBooks emerges from the background only to close the open book, then open it again, sometimes but not always at the same page. (This is easy to reproduce. Open a book in iBooks then swap to Safari. Open about 6 pages and swap between them a few times, opening another couple of pages along the way. Swap back to iBooks.)
When returning to a Safari page after swapping to Mail to get some info, the page will often refresh taking the user to the top of the page. This is particularly annoying when returning to a partially filled form in Safari only to lose all the data.
Others have reported problems returning to Google Maps when driving where taking a call or swapping to another app will reset the route.
The list goes on with an increasing number of very frustrated users. The problem appears to be a memory management issue and if you reset or turn the device off and on again, it seems to clear the memory giving improved app swapping until things start to degrade again. This is why each minor iOS 7 upgrade has appeared to fix the problem for a short time - it's the reset that does it. There have been suggestions that the older devices that only have 500MB memory are particularly vulnerable to the problem.
Why does the issue have such a low profile?
There are perhaps two main reasons why the profile of this problem is not greater:
It's a hard problem to describe so users often fail to find appropriate forums via Google searches.
The problem manifests itself mainly with power-users, i.e. those users who fequently swap between apps. This will often be the case for those who use their devices for work. Many have reported that their devices are no longer fit for business use.
In general it appears to be power-users who are IT-literate enough to know how to describe the problem who are reporting it.
Apple's response
A number of us have been to Genius Bars for advice where we have been encouraged to carry out a DFU reset and restore. No Genius has admitted to encountering the problem before. The reset and restores failed to fix the problem.
Many more of us have contacted Apple support to log the problem. At least one has been requested to provide logging information but not one of us has had a response back from Apple on this.
It's not just older machines
Interestingly, according to a recent study, the iPad 2 accounts for some 38 percent of all active iOS tablets and Apple continues to sell the iPad 2 so one would assume that iOS 7 has been tested against such models and would be expected to run on them satisfactorily.
However, users have reported similar problems with the iPad Air and new iPad Mini. One user had an iPad 2 on iOS 6 with no problems and an iPad Air on 7 exhibiting these problems. He then upgraded the iPad 2 to iOS 7 and has the same issues.
Will it be fixed in the next release?
Unlikely. Initial reports on Beta versions of iOS 7.1, due for release in March 2014, suggest that Safari has been fixed so that the tabs maintain their states thus preventing forms from losing their data when swapping back to them. Apparently, however, the general 'refresh' problem is still there, i.e. other apps are often unable to maintain their states.
What has happened to Apple?
It used to be that Apple kit just worked. After Steve Jobs died, we have seen decreased innovation and an increase in the number of bugs in iOS releases. iOS 6 was riddled with problems including the infamous Maps debacle. iOS 7 has not been much better; it has been equally bug-ridden and has been associated with performance problems on older machines. Many of the iPhone users on the forum are planning to jump ship after their contracts expire. If it were not for the fact that there is still no viable alternative to the iPad Air, I would be looking elsewhere too.
It used to be that Apple was proactive. Now they appear reactive; perhaps the artificial deadline of including iOS 7 with the new phones led to sloppy coding and poor testing. Whatever the reason for Apple's drop in standards, it shows cynical disregard for its customers.
Will Apple become the next Blackberry? I certainly hope not but I do know that, along with many others, my confidence in Apple's ability to deliver quality software has taken a large knock.
</clip>