Does anyone really think Tesla will allow Apps to run in the background, access car systems, and have unrestricted access to the Internet link - car moving or not? I can't imagine they will. The liability and support issues would be horrendous.
I was thinking about this too.. the whole idea of a 17" touch panel in the dash of the car goes deep into the liability territory in my opinion. As interesting as I think the touch panel is, I'm actually kind of spooked by it. Somewhat off topic, when I first started thinking about reserving a Tesla, after sitting in one at the showroom, I tried to imagine using it while driving my current car, an '08 Honda Odyssey Touring. It has a big LCD for the navi, but I like the physical buttons for the radio, the headlights, answering the phone, sunroof, etc. I don't need to take my eyes off the road.
Weird example: Every Tesla demo I've seen so far highlights the fact that we see cover art on the front display, where the speedo is. It is probably the most useless piece of information to place on the most critical display... I mean really, animated cover art next to warning lights? I'm told this will be customizable, so I intend to turn it off.
It would be different if the computer behind that 17" display was completely separate from the vehicle control systems (just a giant iPad embedded in the console), but I doubt it. From what they show, the system has pretty extensive access to several vehicle control systems. I expect it to be something like the VMS/VDS system in the Roadster. Allowing end-users to run custom software in that system would be a nightmare, and jail breakers dream
Clearly the computer has _some_ access to the car, but I'm hoping it has no direct access to anything involved in the drivetrain. The dashboard computer ought not to be able to stop the motor, brakes, steering pump, etc. If I were designing this, those functions would live in a locked-down ECU like modern ICE cars, possibly with some status readout that can be relayed to the big LCD.
Sorry, to be the nay-sayer, but I see the API as something akin to the iOS API v1 (web apps only) or perhaps v2 (very basic native level display-only). I'd be overjoyed to be proven wrong, but expect not to be.
Why be sorry? These are valid points, and hopefully Tesla is thinking about this stuff, or is reading us while we think out loud.
I've been making assumptions about how the onboard systems work, based on how I think I'd do it. Tesla has a bunch of smart people, but the company's not that big and they're under pressure to deliver, so it would be interesting to see if they cut any corners to get the software out.
As I suggested above, I'd think that drivetrain stuff is a separate computer, but we've seen that the touch panel computer has access to plenty of non-drivetrain things that present a safety hazard - it can definitely control the headlights, windows, sunroof, trunk latches, door locks, climate control, air suspension. It can probably interface with the charger. Given that most devices will probably live on one or more CAN buses, there can't be all that much security.
Web apps (like iOS 1.0) might be just fine for many of my needs. I think I'd also be happy with a walled-garden approach, with Tesla vetting apps before sale.
I do know this: I'll go to the dog house permanently the first time an app _I_ wrote disables the car while my wife is in it, and I don't even want to think about what would happen if she was driving!
/Mitch.