I've reported dozens upon dozens of problems since I first got Apple Maps 5 months ago and not a single one of them has been fixed. There are two possibilities:
1. Apple is saving all the fixes that have been sent and it plans to release them all together in one big update when iOS 7 comes our.
2. Apple is continually fixing them as we speak, but this process is occurring so slowly, that no one notices it.
If #2 is accurate, then the app is completely hopeless. If Apple has actually been updating things and hasn't been stockpiling them, then it is going at such a slow pace that Maps will NEVER be a decent app.
If #1 is accurate, then there's still hope. This still isn't a good idea because it causes people to become disillusioned with the app because people simply won't use the 'Report A Problem' feature if they don't see it doing anything. Apple likes to release things periodically (ie. annually) rather than continually. That's how it functions with its hardware and software releases. The problem is that for a service like Maps, these upgrades should happen continually throughout the year, not on a periodic basis.
I respectfully disagree with both #1 & #2.
Regarding #1, in my opinion, map updates aren't the sort of thing that you "save" for some upcoming software release (assuming you're not limited to doing so). At least not these days. Apple has been hammered on this to an extreme extent (public apology from Tim Cook) that it would be a seriously poor judgement call on their part to do so. They already made one such call when they released Maps in the condition that they did. I very much doubt they'd make the same mistake again...with the same app.
Regarding #2, the "slowness" with which they correct their maps data is entirely relative to how many people they have working on it, how many reports they receive for each error, and how they prioritize those reports, among other things. This is a sentiment I've expressed
before.
Let's take a moment to [very roughly] think about some numbers:
There are
approximately 300 million iOS 6 devices out there right now. Assuming that not every one of them can account for an error report but instead, say, a third of them, that's still 100 million error reports. Heck, make it a 30th of those devices (10 million reports). I'm confident that the majority of users have never submitted a report but I imagine that there are still many who have. And, as this thread shows, at least some of those users have submitted multiple reports. I know I have.
These reports presumably can't fix themselves, no matter how many times they're duplicated. By this I mean to say (read: assume) that someone has to manually verify the accuracy of any one report, even if all 10 million reports were for the same thing. What getting 10 million reports for one thing likely
would do is move that report to the top of the list.
So I'm assuming 10 million reports.
If the team working on these is, for example, a thousand strong and corrections began on day 1 of iOS 6's release 5 months ago, that calculates to approximately 65 corrections per day to be at zero. Of course, many reports are for the same thing so for the sake of argument, I'll assume 10 corrections per day per team member. And still yet, there are likely a more-than-negligible amount of reports that are maliciously bogus, intended to muck things up. These bogus reports further slow the process down in ways we can only speculate about.
To make a long story not as long as it could be, the report that I submitted on day 1 that "moved" the bar nearest to my work to its rightful place is not one that I expect to have corrected anytime soon. But I'm not worried, I still know where that bar is.
And I'm not arguing that any of this is okay. In fact, I think it's a damn shame. But I don't agree that it's "completely hopeless."