software is good for management presentation, where things like "common code base" sound better than "we will develop two different implementations". In reality, the extra work you have to put in just to implement some functions that are common to the native environment and frameworks is more or less equal to work you would need for a clean implementation of the application design for each platform.
The parts, which seem to be the biggest problem for the others (like OBDII) are. Others (navigation engine) will be.Is it open source?
No, it is not. Why should it?Is it free?
Well, it does not provide more torque. And you need a lot of extra adapters and interfaces to actually make it work with the rest of the car :-)I would then make the analogy that a Flex/Flash front end (backed by Java) is like buying a Porche and putting a hybrid engine in that runs on any fuel source (and provides more torque than the stock engine):
Nonsense. For the USA, you can get very decent free vector maps. Even getting the maps from Navteq and TeleAtlas for reasonable prices is not that difficult. In my opinion, the biggest problem with navigation is that it requires a little knowledge of "real" programming, not just click + drag & drop in Interface builder. From my own experience, the single most difficult task when making a navigation app is to create a map format, that would not take up too much disk space and would provide quick access to the data - even smaller countries like the Netherlands contain hundreds of thousands of road elements and to work with this amount of data is no fun.Anyways, this collaboration is seeming more and more possible as we get into it. The hard part with GPS is still the maps.