I am not a SD dev, but I could see this being somewhat of a technical hurdle combined with a choice in requirements. If they are rewriting the Nav module for SD to support a new mapping engine, they would also have to write in support for doing traffic overlays. Then there is the issue of getting traffic data from a central source in your car. I realize that some people can do data pass through from telephones and whatnot, but in reality its not a REQUIRED feature to get nav running. You do however need to have the maps loaded locally in the car and basic navigation working in the car offline from the internet.
I could see it as a deliberate choice to leave it out due to the fact that it adds technical difficulty to get working and the fact that its not required for a nav system. I would love to see it, but I would rather have an updated mapset first.
I wish this was the case earlier. A simple "We haven't had time to implement traffic...yet" would have done wonders...but enough with the past...
Maybe we should get the "What would you like to see in streetdeck" thread fired up again...Really glad SD isn't dead by the way...
good idea...
Chuck, I would highly suggest you selling the software directly. I am willing to bet most if not all SD customers who purchased through mp3car no longer would purchase from them again from the way they were treated for the past 6 months. I know I wouldn't purchase v2 if it's only sold through mp3car.
I agree completely and it seems this is where the users come in with the SDK. Anyone who has the know how should deff contribute. I should find time to take up coding again so I can build some stuff.
I like SD because for me it just works 99% of the time. So I say, get a solid base with a good nav and let people add on. Maybe even offer some kind of perks if you are a developer for SD. Free SD bumper stickers or something.![]()
Bookmarks