To beta test the functionality of the app why would they need the most current dataset? It just now got realeased to developers. Data precision is not a key factor at this time for what they are actually trying to do.
Do you just not understand the data is seperate from the application?
My thoughts exactly. Theres another thread just like this from a native new yorker crying about how he depends on google maps.
I can't for the life of me figure out as to why he's even running a beta 1 as his primary. Especially if he depends on his iphone for commuting purposes.
Few weeks of launch vs years (google)
Seriously, you guys??
This forum is a bunch of whiners and low life kids..
And fanboys that can't stand anyone criticising Apple? Few weeks vs years? What kind of an excuse is that for putting out a crappy app?
Few weeks of launch vs years (google)
Seriously, you guys??
This forum is a bunch of whiners and low life kids..
Few weeks of launch vs years (google)
Seriously, you guys??
This forum is a bunch of whiners and low life kids..
So wait, because Apple only had a "Few weeks" (3 years btw...) we should excuse them for downgrading our map data vs what they currently offer with iOS 5 ?
Hum... no.
Dude, ios5 is google maps lol...
I'd actually agree...if they had released iOS 6.... What part of "BETA" do people have such trouble with? I guess Google messed it all up as they just slapped "BETA" on any thing and everything.![]()
This has been quite the amusing thread, primarily because so many people refuse to get over their own lack of understanding of what "beta" software means. As others have pointed out, it's fine for the Maps application to have bugs and crashes here and there - that's the point of letting people beta test your software, to find those things. It is not an accepted practice for entire chunks of data to be missing from the software at this stage of development. That's only inviting a whole new slew of potential bugs and such at whatever later date the entire "live" dataset introduced into the software (IF it's going to be introduced). If this is indeed the route that Apple is taking, it will be closer to the actual launch date, giving Apple far less time to correct any problems that arise from the introduction of said live data. That is extremely risky for an application of this magnitude.
You'd have a point if the map data was based on the device in the app, but what you and many other people here seem to forget is the map data is server side. That can be updated anytime, google maps, bing maps, they all update their map data regularly, so why do people seem to think that this is not easily done for apple?! All that needs to be in place for the beta for the devs to test the API's is for the app to be working, which it does......
For an initial release of something, you would normally place a full copy of the live data on the server.
Do you work in software development? Do you know how risky it is, not to use real, updated data so late in the development cycle?
Using updated or old data can break an application / product. It could cause a lot of other problems.
If it makes anybody feel better, I read somewhere Google maps will now be an optional downloadable app in the app store. So if Apples app does not fully deliver by the time iOS 6 is launched Google maps will be able to point you in the right direction.
Yes pun intended.
As much as I like maps it's always nice to have choices
If it makes anybody feel better, I read somewhere Google maps will now be an optional downloadable app in the app store. So if Apples app does not fully deliver by the time iOS 6 is launched Google maps will be able to point you in the right direction.
Yes pun intended.
Where do you read this for a fact? I've seen this thrown around by a lot of people but I have yet to see s statement by Google saying they are releasing an ios Google maps app. And of course Apple won't say anything on the subject or how long it will take them to "approve" the app. Google currently has had Chrome and Google Drive done and awaiting approval in the App store for months.
I don't remember exactly and I do not wish to lead people in the wrong direction. My apologies for that. But I want to say I read it before Google's map announcement or in the same time frame. I believe it MAY have been The Verge. But I'm not positive.
I work in SW development - and I don't see the issue. With a large enough test/dev team and environment, you can easily have multiple testing groups. For the large public beta - they might be using a limited dataset (first reason might be the production servers might still be getting built/setup etc) while using the full dataset with smaller set of internal testers.
There are lot of scenarios where this is fine - some where it might not be.
The maps data is an online service Apple will be providing. 6 month prior to release, if the servers are not in place and already ready to accept the predicted load, you have a problem.
Working along side dev teams and solution builders, I can tell you that "live" production environnements are present at least 1 year prior to launch, Q&A environnements are built from copies of the production data set, anonymized to prevent information leaks (though with maps I doubt the anonymization step is required), and everything is ready quite a few months in advance.
At this point, I think anyone wishing Apple has some secret stash of data just don't want this to be what is real, as much as everyone else. I think everyone can agree (no matter which side of the "beta" debate you're on) that this dataset just isn't production quality.
But to me, that comes as no surprise. Apple has never been good at online services.