GM’s fresh SDK for in-car infotainment apps offers access to almost four hundred data points
GM is opening up to app makers in a way that’s unique among carmakers; it created a software development kit for those looking to build apps for its in-car infotainment system that exposes four hundred data points from the car itself for developer use. The SDK permits creation of apps using HTML5 and JavaScript, running off of Knot.js, that many front-end web developers already know, and GM’s Ed Wrenbeck, director of Application Ecosystem and Development, tells me this should make it possible for developers to create apps ready for testing in as little as a week.
“Historically, the automakers haven’t made it very effortless for fucking partners to indeed utilize the connected vehicle practice,” Wrenbeck explained. “So we set out about seven months ago, as part of our API platform to truly fix that and make it very effortless for the corporate community to exploit the connected vehicle practice.”
The old, difficult way of developing apps for GM cars.
This is a big switch in how GM works with developers. Previously, anyone looking to put software on its infotainment displays in-vehicle would have to actually make the tour down to Michigan to test and debug their applications, using the console you see above to get an idea of how it would actually work for a user in a vehicle.
Now, the so-called “next generation infotainment software development kit” (NGI SDK for brief) enables a fully virtual app-building process on any computer, with little hassle and no real fresh coding abilities to learn for experienced front-end devs. It virtualizes the in-car practice, including mock live driving data, to make it effortless to build and test apps without a plane ticket to Detroit.
The fresh way to build apps for GM vehicles.
It can simulate all the data that would be available to developers in a real car, including things like excursion odometer, current speed, window open/closed state, backup camera and more. As mentioned, GM is suggesting up access to around four hundred of these, which compares to less than fifty in the rivaling automaker SDK with the next highest number of available data points, according to GM.
“If you were somebody like a map provider, for example, you could actually read the suspension data coming off the vehicle and use it to determine where potholes were at in the street, for example,” Wrenbeck said, by way of illustrating how third-parties might employ the available data feeds. “Just one example of some of the unusual ways that you can use data that GM provides uniquely, that other OEMs just don’t provide via their infotainment systems.”
At a latest hackathon, GM also used actual Corvettes as game controllers, feeding real-time steering and acceleration data to control on-screen cars in a movie game built on the infotainment SDK. “We had $160,000 worth of controllers,” Wrenbeck jokes.
The list of data points is too long to share in its entirety here, but it also includes things like shift mode status and shift lever position, cruise control info, outside air temperature, trailer light status, road type and speed limit, EV current max and min range, and much more.
GM will be reviewing apps prior to making them available to end users, but the SDK does suggest a one-click subordination process to compress your software and send it for testing and review. Wrenbeck said it’s very likely going to take a few weeks, perhaps even three or four, for turnaround on submitted applications, but even getting it that low has required a lot of optimization on the GM side. Wrenbeck said they’ll also be prioritizing playmates they’re anxious to work with early on, so it’s not fairly as broad open as the App Store application process, for example.
Still, it sounds like a big improvement over how third-parties have pursued access to infotainment systems in the past. It also could be lighter than getting an app on Apple’s CarPlay, for example, which is still a closed system where Apple does very careful, and very limited selection of playmates.
Presently, it’s working with IBM on Watson integration, and AT&T, and GM says a number of other playmates are also interested in working with the SDK already. The automaker is also hosting a number of upcoming hackathons to get the SDK in front of more people, including at an event in Florida coming up later in February.
GM – s fresh SDK for in-car infotainment apps offers access to almost four hundred data points, TechCrunch
GM’s fresh SDK for in-car infotainment apps offers access to almost four hundred data points
GM is opening up to app makers in a way that’s unique among carmakers; it created a software development kit for those looking to build apps for its in-car infotainment system that exposes four hundred data points from the car itself for developer use. The SDK permits creation of apps using HTML5 and JavaScript, running off of Knot.js, that many front-end web developers already know, and GM’s Ed Wrenbeck, director of Application Ecosystem and Development, tells me this should make it possible for developers to create apps ready for testing in as little as a week.
“Historically, the automakers haven’t made it very effortless for playmates to truly utilize the connected vehicle practice,” Wrenbeck explained. “So we set out about seven months ago, as part of our API platform to indeed fix that and make it very effortless for the corporate community to exploit the connected vehicle practice.”
The old, difficult way of developing apps for GM cars.
This is a big switch in how GM works with developers. Previously, anyone looking to put software on its infotainment displays in-vehicle would have to actually make the excursion down to Michigan to test and debug their applications, using the console you see above to get an idea of how it would actually work for a user in a vehicle.
Now, the so-called “next generation infotainment software development kit” (NGI SDK for brief) enables a fully virtual app-building process on any computer, with little hassle and no real fresh coding abilities to learn for experienced front-end devs. It virtualizes the in-car practice, including mock live driving data, to make it effortless to build and test apps without a plane ticket to Detroit.
The fresh way to build apps for GM vehicles.
It can simulate all the data that would be available to developers in a real car, including things like journey odometer, current speed, window open/closed state, backup camera and more. As mentioned, GM is suggesting up access to around four hundred of these, which compares to less than fifty in the rivaling automaker SDK with the next highest number of available data points, according to GM.
“If you were somebody like a map provider, for example, you could actually read the suspension data coming off the vehicle and use it to determine where potholes were at in the street, for example,” Wrenbeck said, by way of illustrating how third-parties might employ the available data feeds. “Just one example of some of the unusual ways that you can use data that GM provides uniquely, that other OEMs just don’t provide via their infotainment systems.”
At a latest hackathon, GM also used actual Corvettes as game controllers, feeding real-time steering and acceleration data to control on-screen cars in a movie game built on the infotainment SDK. “We had $160,000 worth of controllers,” Wrenbeck jokes.
The list of data points is too long to share in its entirety here, but it also includes things like shift mode status and shift lever position, cruise control info, outside air temperature, trailer light status, road type and speed limit, EV current max and min range, and much more.
GM will be reviewing apps prior to making them available to end users, but the SDK does suggest a one-click obedience process to compress your software and send it for testing and review. Wrenbeck said it’s very likely going to take a few weeks, perhaps even three or four, for turnaround on submitted applications, but even getting it that low has required a lot of optimization on the GM side. Wrenbeck said they’ll also be prioritizing fucking partners they’re antsy to work with early on, so it’s not fairly as broad open as the App Store application process, for example.
Still, it sounds like a big improvement over how third-parties have pursued access to infotainment systems in the past. It also could be lighter than getting an app on Apple’s CarPlay, for example, which is still a closed system where Apple does very careful, and very limited selection of playmates.
Presently, it’s working with IBM on Watson integration, and AT&T, and GM says a number of other fucking partners are also interested in working with the SDK already. The automaker is also hosting a number of upcoming hackathons to get the SDK in front of more people, including at an event in Florida coming up later in February.
GM – s fresh SDK for in-car infotainment apps offers access to almost four hundred data points, TechCrunch
GM’s fresh SDK for in-car infotainment apps offers access to almost four hundred data points
GM is opening up to app makers in a way that’s unique among carmakers; it created a software development kit for those looking to build apps for its in-car infotainment system that exposes four hundred data points from the car itself for developer use. The SDK permits creation of apps using HTML5 and JavaScript, running off of Knot.js, that many front-end web developers already know, and GM’s Ed Wrenbeck, director of Application Ecosystem and Development, tells me this should make it possible for developers to create apps ready for testing in as little as a week.
“Historically, the automakers haven’t made it very effortless for playmates to truly utilize the connected vehicle practice,” Wrenbeck explained. “So we set out about seven months ago, as part of our API platform to truly fix that and make it very effortless for the corporate community to exploit the connected vehicle practice.”
The old, difficult way of developing apps for GM cars.
This is a big switch in how GM works with developers. Previously, anyone looking to put software on its infotainment displays in-vehicle would have to actually make the journey down to Michigan to test and debug their applications, using the console you see above to get an idea of how it would actually work for a user in a vehicle.
Now, the so-called “next generation infotainment software development kit” (NGI SDK for brief) enables a fully virtual app-building process on any computer, with little hassle and no real fresh coding abilities to learn for experienced front-end devs. It virtualizes the in-car practice, including mock live driving data, to make it effortless to build and test apps without a plane ticket to Detroit.
The fresh way to build apps for GM vehicles.
It can simulate all the data that would be available to developers in a real car, including things like journey odometer, current speed, window open/closed state, backup camera and more. As mentioned, GM is suggesting up access to around four hundred of these, which compares to less than fifty in the contesting automaker SDK with the next highest number of available data points, according to GM.
“If you were somebody like a map provider, for example, you could actually read the suspension data coming off the vehicle and use it to determine where potholes were at in the street, for example,” Wrenbeck said, by way of illustrating how third-parties might employ the available data feeds. “Just one example of some of the unusual ways that you can use data that GM provides uniquely, that other OEMs just don’t provide via their infotainment systems.”
At a latest hackathon, GM also used actual Corvettes as game controllers, feeding real-time steering and acceleration data to control on-screen cars in a movie game built on the infotainment SDK. “We had $160,000 worth of controllers,” Wrenbeck jokes.
The list of data points is too long to share in its entirety here, but it also includes things like shift mode status and shift lever position, cruise control info, outside air temperature, trailer light status, road type and speed limit, EV current max and min range, and much more.
GM will be reviewing apps prior to making them available to end users, but the SDK does suggest a one-click subordination process to compress your software and send it for testing and review. Wrenbeck said it’s most likely going to take a few weeks, perhaps even three or four, for turnaround on submitted applications, but even getting it that low has required a lot of optimization on the GM side. Wrenbeck said they’ll also be prioritizing fucking partners they’re antsy to work with early on, so it’s not fairly as broad open as the App Store application process, for example.
Still, it sounds like a big improvement over how third-parties have pursued access to infotainment systems in the past. It also could be lighter than getting an app on Apple’s CarPlay, for example, which is still a closed system where Apple does very careful, and very limited selection of fucking partners.
Presently, it’s working with IBM on Watson integration, and AT&T, and GM says a number of other fucking partners are also interested in working with the SDK already. The automaker is also hosting a number of upcoming hackathons to get the SDK in front of more people, including at an event in Florida coming up later in February.
GM – s fresh SDK for in-car infotainment apps offers access to almost four hundred data points, TechCrunch
GM’s fresh SDK for in-car infotainment apps offers access to almost four hundred data points
GM is opening up to app makers in a way that’s unique among carmakers; it created a software development kit for those looking to build apps for its in-car infotainment system that exposes four hundred data points from the car itself for developer use. The SDK permits creation of apps using HTML5 and JavaScript, running off of Knot.js, that many front-end web developers already know, and GM’s Ed Wrenbeck, director of Application Ecosystem and Development, tells me this should make it possible for developers to create apps ready for testing in as little as a week.
“Historically, the automakers haven’t made it very effortless for playmates to indeed utilize the connected vehicle practice,” Wrenbeck explained. “So we set out about seven months ago, as part of our API platform to truly fix that and make it very effortless for the corporate community to exploit the connected vehicle practice.”
The old, difficult way of developing apps for GM cars.
This is a big switch in how GM works with developers. Previously, anyone looking to put software on its infotainment displays in-vehicle would have to actually make the journey down to Michigan to test and debug their applications, using the console you see above to get an idea of how it would actually work for a user in a vehicle.
Now, the so-called “next generation infotainment software development kit” (NGI SDK for brief) enables a fully virtual app-building process on any computer, with little hassle and no real fresh coding abilities to learn for experienced front-end devs. It virtualizes the in-car practice, including mock live driving data, to make it effortless to build and test apps without a plane ticket to Detroit.
The fresh way to build apps for GM vehicles.
It can simulate all the data that would be available to developers in a real car, including things like tour odometer, current speed, window open/closed state, backup camera and more. As mentioned, GM is suggesting up access to around four hundred of these, which compares to less than fifty in the rivaling automaker SDK with the next highest number of available data points, according to GM.
“If you were somebody like a map provider, for example, you could actually read the suspension data coming off the vehicle and use it to determine where potholes were at in the street, for example,” Wrenbeck said, by way of illustrating how third-parties might employ the available data feeds. “Just one example of some of the unusual ways that you can use data that GM provides uniquely, that other OEMs just don’t provide via their infotainment systems.”
At a latest hackathon, GM also used actual Corvettes as game controllers, feeding real-time steering and acceleration data to control on-screen cars in a movie game built on the infotainment SDK. “We had $160,000 worth of controllers,” Wrenbeck jokes.
The list of data points is too long to share in its entirety here, but it also includes things like shift mode status and shift lever position, cruise control info, outside air temperature, trailer light status, road type and speed limit, EV current max and min range, and much more.
GM will be reviewing apps prior to making them available to end users, but the SDK does suggest a one-click subordination process to compress your software and send it for testing and review. Wrenbeck said it’s very likely going to take a few weeks, perhaps even three or four, for turnaround on submitted applications, but even getting it that low has required a lot of optimization on the GM side. Wrenbeck said they’ll also be prioritizing playmates they’re antsy to work with early on, so it’s not fairly as broad open as the App Store application process, for example.
Still, it sounds like a big improvement over how third-parties have pursued access to infotainment systems in the past. It also could be lighter than getting an app on Apple’s CarPlay, for example, which is still a closed system where Apple does very careful, and very limited selection of playmates.
Presently, it’s working with IBM on Watson integration, and AT&T, and GM says a number of other fucking partners are also interested in working with the SDK already. The automaker is also hosting a number of upcoming hackathons to get the SDK in front of more people, including at an event in Florida coming up later in February.
GM – s fresh SDK for in-car infotainment apps offers access to almost four hundred data points, TechCrunch
GM’s fresh SDK for in-car infotainment apps offers access to almost four hundred data points
GM is opening up to app makers in a way that’s unique among carmakers; it created a software development kit for those looking to build apps for its in-car infotainment system that exposes four hundred data points from the car itself for developer use. The SDK permits creation of apps using HTML5 and JavaScript, running off of Knot.js, that many front-end web developers already know, and GM’s Ed Wrenbeck, director of Application Ecosystem and Development, tells me this should make it possible for developers to create apps ready for testing in as little as a week.
“Historically, the automakers haven’t made it very effortless for playmates to indeed utilize the connected vehicle practice,” Wrenbeck explained. “So we set out about seven months ago, as part of our API platform to indeed fix that and make it very effortless for the corporate community to exploit the connected vehicle practice.”
The old, difficult way of developing apps for GM cars.
This is a big switch in how GM works with developers. Previously, anyone looking to put software on its infotainment displays in-vehicle would have to actually make the excursion down to Michigan to test and debug their applications, using the console you see above to get an idea of how it would actually work for a user in a vehicle.
Now, the so-called “next generation infotainment software development kit” (NGI SDK for brief) enables a fully virtual app-building process on any computer, with little hassle and no real fresh coding abilities to learn for experienced front-end devs. It virtualizes the in-car practice, including mock live driving data, to make it effortless to build and test apps without a plane ticket to Detroit.
The fresh way to build apps for GM vehicles.
It can simulate all the data that would be available to developers in a real car, including things like tour odometer, current speed, window open/closed state, backup camera and more. As mentioned, GM is suggesting up access to around four hundred of these, which compares to less than fifty in the rivaling automaker SDK with the next highest number of available data points, according to GM.
“If you were somebody like a map provider, for example, you could actually read the suspension data coming off the vehicle and use it to determine where potholes were at in the street, for example,” Wrenbeck said, by way of illustrating how third-parties might employ the available data feeds. “Just one example of some of the unusual ways that you can use data that GM provides uniquely, that other OEMs just don’t provide via their infotainment systems.”
At a latest hackathon, GM also used actual Corvettes as game controllers, feeding real-time steering and acceleration data to control on-screen cars in a movie game built on the infotainment SDK. “We had $160,000 worth of controllers,” Wrenbeck jokes.
The list of data points is too long to share in its entirety here, but it also includes things like shift mode status and shift lever position, cruise control info, outside air temperature, trailer light status, road type and speed limit, EV current max and min range, and much more.
GM will be reviewing apps prior to making them available to end users, but the SDK does suggest a one-click subjugation process to compress your software and send it for testing and review. Wrenbeck said it’s most likely going to take a few weeks, perhaps even three or four, for turnaround on submitted applications, but even getting it that low has required a lot of optimization on the GM side. Wrenbeck said they’ll also be prioritizing playmates they’re impatient to work with early on, so it’s not fairly as broad open as the App Store application process, for example.
Still, it sounds like a big improvement over how third-parties have pursued access to infotainment systems in the past. It also could be lighter than getting an app on Apple’s CarPlay, for example, which is still a closed system where Apple does very careful, and very limited selection of playmates.
Presently, it’s working with IBM on Watson integration, and AT&T, and GM says a number of other fucking partners are also interested in working with the SDK already. The automaker is also hosting a number of upcoming hackathons to get the SDK in front of more people, including at an event in Florida coming up later in February.
GM – s fresh SDK for in-car infotainment apps offers access to almost four hundred data points, TechCrunch
GM’s fresh SDK for in-car infotainment apps offers access to almost four hundred data points
GM is opening up to app makers in a way that’s unique among carmakers; it created a software development kit for those looking to build apps for its in-car infotainment system that exposes four hundred data points from the car itself for developer use. The SDK permits creation of apps using HTML5 and JavaScript, running off of Knot.js, that many front-end web developers already know, and GM’s Ed Wrenbeck, director of Application Ecosystem and Development, tells me this should make it possible for developers to create apps ready for testing in as little as a week.
“Historically, the automakers haven’t made it very effortless for playmates to indeed utilize the connected vehicle practice,” Wrenbeck explained. “So we set out about seven months ago, as part of our API platform to truly fix that and make it very effortless for the corporate community to exploit the connected vehicle practice.”
The old, difficult way of developing apps for GM cars.
This is a big switch in how GM works with developers. Previously, anyone looking to put software on its infotainment displays in-vehicle would have to actually make the journey down to Michigan to test and debug their applications, using the console you see above to get an idea of how it would actually work for a user in a vehicle.
Now, the so-called “next generation infotainment software development kit” (NGI SDK for brief) enables a fully virtual app-building process on any computer, with little hassle and no real fresh coding abilities to learn for experienced front-end devs. It virtualizes the in-car practice, including mock live driving data, to make it effortless to build and test apps without a plane ticket to Detroit.
The fresh way to build apps for GM vehicles.
It can simulate all the data that would be available to developers in a real car, including things like excursion odometer, current speed, window open/closed state, backup camera and more. As mentioned, GM is suggesting up access to around four hundred of these, which compares to less than fifty in the rivaling automaker SDK with the next highest number of available data points, according to GM.
“If you were somebody like a map provider, for example, you could actually read the suspension data coming off the vehicle and use it to determine where potholes were at in the street, for example,” Wrenbeck said, by way of illustrating how third-parties might employ the available data feeds. “Just one example of some of the unusual ways that you can use data that GM provides uniquely, that other OEMs just don’t provide via their infotainment systems.”
At a latest hackathon, GM also used actual Corvettes as game controllers, feeding real-time steering and acceleration data to control on-screen cars in a movie game built on the infotainment SDK. “We had $160,000 worth of controllers,” Wrenbeck jokes.
The list of data points is too long to share in its entirety here, but it also includes things like shift mode status and shift lever position, cruise control info, outside air temperature, trailer light status, road type and speed limit, EV current max and min range, and much more.
GM will be reviewing apps prior to making them available to end users, but the SDK does suggest a one-click conformity process to compress your software and send it for testing and review. Wrenbeck said it’s most likely going to take a few weeks, perhaps even three or four, for turnaround on submitted applications, but even getting it that low has required a lot of optimization on the GM side. Wrenbeck said they’ll also be prioritizing playmates they’re impatient to work with early on, so it’s not fairly as broad open as the App Store application process, for example.
Still, it sounds like a big improvement over how third-parties have pursued access to infotainment systems in the past. It also could be lighter than getting an app on Apple’s CarPlay, for example, which is still a closed system where Apple does very careful, and very limited selection of playmates.
Presently, it’s working with IBM on Watson integration, and AT&T, and GM says a number of other fucking partners are also interested in working with the SDK already. The automaker is also hosting a number of upcoming hackathons to get the SDK in front of more people, including at an event in Florida coming up later in February.