Quote:
Originally Posted by Eurisko
Obviously you don't know how stupid the majority of the populous really is. Sure my examples were extreme to pint out liability, but many people do exactly as they are told.
Additionally, as InspectorGadget pointed out, yes TomTom shows a disclaimer, but that is on TomTom's own hardware, not a 3rd parties. And one last note, for true and precise mapping, the maps would need to be on the phone itself, and TomTom's North American map for example is 1.2 GB. Members of this forum aside, how many people would be willing to use up that much space on their phone for 1 program.
In the US, it definitely would. Google the case of the woman who bought an RV. She was driving one day, then decided to get up and make some breakfast, but made sure to put the cruise control on first. When the RV went off the road and got totaled, she sued the company stating that the manual never said she couldn't leave the drivers seat while the RV was in motion. And she won.
Now every RV manual specifically states these guidelines in the drivers manual. Think I'm joking? You'd be surprised.
|
Don't believe everything you read on the internet. I have yet to see a case number for the mythical "cruise control" lawsuit anywhere, it's urban myth until proven otherwise.
You might use the McDonalds hot coffee lawsuit, but guess what that's real, and MC was serving coffee above a safe temperature.
As for Apple not implimenting navigation due to "liability risk" if someone turns into a building, that's simply rediculous, no offense. Most likely the reasons are most likely due to something like (and this are assumptions like everything else here):
1. The phone's GPS implementation is not yet ready for prime time (hence the rumors around the 2.1 gps update providing a proper gps data feed.
2. GPS apps are simply not ready for prime time. These things do take some time to produce.
3. The charger "inadequacy" issue is real and running the phone as a full time navigation system is not feasible as the phone will run out of power even if plugged in.
As for the "against SDK rules" arguments, care to elaborate? I don't see anything in the rules that rule out GPS navigation. Now if you had said that the current SDK doesn't support the features to properly support turn by turn navigation, that might make sense.