![]() Knowing what I know from my time in automotive, *if* we see any vehicle-enabled weather app, I would venture a guess to say it would be from someone like AccuWeather or TWC (and very consumer grade), but I'd love to be wrong on that. But at the end of the day, how much of the car-buying market do all of us together actually represent? The marketing managers are going to insert themselves (and their $$) into accelerating development of what they think the car-buying market wants, and I don't think the stuff we're talking about is, well, on their radar. If that exact same info is on an infotainment screen, then as long as my driving is fine, everything is A-OK. Heck, I can get stopped (as a primary offense) and issued a ticket in my state just for looking at a phone, tablet, or (presumably) laptop while driving, even if my driving is perfect while doing so. I know that many of us would like a good radar app that shows up on the infotainment screen, myself included. Automakers are going to look at what makes them money, and make decisions based on that. Anyway, I do recall the excitement to get a standardized in-vehicle app platform was tempered when the Pandora's box of rules and regulations that comes with in-vehicle UI got opened and attached to the mix.Ĭlick to expand.and this is the other part. As an app developer, you would need to develop one CarPlay-enabled app, not one for each OEM, so you would have to design your UI to the lowest most restrictive common denominator. Google the VIRTTEX driving simulator to see the one my team used. Automakers do get their say as well, and many (including my former employer) have their own in-house driver distraction mitigation requirements that go beyond government regulations and AAM guidelines, having spent considerable time and money researching and developing them with the goal of avoiding lawsuits. You could argue that navigation (using voice guidance) is even though in practice, we know that the strictly voice-based interaction isn't all that perfect. Radar apps really aren't well suited to work that way. MacOS, iOS, watchOS, and tvOS UI: Human Interface Guidelines - Design - Apple DeveloperĬlick to expand.I don't think that's the only counterargument, although the Apple UI guidelines, as Randy provided a link to, do emphasize minimal interactions, minimal visual display information, and guide developers toward more of a voice-based UI using Siri. It also contains a provision that a developer "must be open and responsive to feedback in the event that Apple or automakers have input to design or functionality." I seems risky for an app developer to spend time and money developing a radar app for CarPlay when Apple will likely reject it and if they do approve it they can always come back and tell you to change something.ĬarPlay UI: Introduction - CarPlay - Human Interface Guidelines - Apple Developer I should note that their navigation guidelines prohibit interactive user interface elements on a map. Now their user interface design guidelines have dropped Navigation, but it still appears in their CarPlay documentation. Originally Apple only allowed Audio, Navigation, Automaker, and Messaging/VOIP apps on CarPlay. Click to expand.There are different design guidelines for CarPlay than for other Apple platforms, so it seems like it would be a waste of time/money for Apple to evaluate every app for CarPlay unless the developer requested it (but since I don't pay $99 a year to be an Apple developer, I can't say for sure since I can't access their submittal form).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |