Contents

조회 수 125247 댓글 0
?

단축키

Prev이전 문서

Next다음 문서

크게 작게 위로 아래로 댓글로 가기 인쇄
?

단축키

Prev이전 문서

Next다음 문서

크게 작게 위로 아래로 댓글로 가기 인쇄

carplay01.jpg



Rejoice! Apple finally announced navigation app access for CarPlay in the 2018 WWDC keynote.


Starting with iOS 12, we get access to the CarPlay framework, that lets us draw interface components and functionality for our iOS navigation app on the CarPlay screen.


Setup

You would probably want to start developing right away, right? Hold on a second, unfortunately it’s not that easy. Apple requires developers to apply for access to the entitlements that are needed to run a CarPlay navigation app on a real device. That includes an entitlements key for your XCode project and a provisioning profile that allows signing of CarPlay navigation apps.


However, there is a way to start developing your CarPlay navigation app in the XCode simulator while you are waiting for access. This involves adding a key to your app’s AppName.entitlements file. If you haven’t got such a file in your XCode project yet, see step 1 below, if you do, skip to step 2.


Step 1

To quickly add an entitlements file to your project, go to your app’s target settings in XCode, then to the capabilities tab and for example switch on the Homekit capability. This creates a .entitlements file in your project and routes it for your build system to see. You can add the key from step 2 and then switch off the Homekit capability.


Step 2

I stumbled on this key when trying a lot of variants by trial & error, as I heard that the only thing that it took to test CarPlay Audio apps on the simulator was a com.apple.developer.playable-content key in the entitlements file.


The key that worked was to set com.apple.developer.carplay-maps to true in the entitlements file. If you follow the CarPlay navigation documentation and you have that key present, you can use the XCode 10 beta with the CarPlay simulator (in the Simulator app, go to Hardware → External displays → CarPlay) to test your CarPlay navigation app.



The CarPlay Framework

What Apple cares about in UX is consistency between apps. That is why, for the CarPlay Framework, only the most fundamental interactions are exposed to developers. This is a restriction that is welcoming for our designers, as they have clear boundaries to work with. It also helps developers make safe apps that don’t distract the user too much from looking at the road behind the wheel.


Therefore, the CarPlay Framework is divided by a Template overlay and a CarPlay window separate from your iPhone’s window that you can set a rootViewController property for your ViewController.


CPMapContentWindow:

This window is the place for you to implement your custom views and navigation tiles. You do not seem to be restricted in what you can draw here, however, I assume Apple will be strict in the review process in what they will allow. This is mainly meant to be flexible to allow developers to implement their existing maps, not to go wild with complex User Interactions, as content in the CPMapContentWindow doesn’t accept user interactions. So how would you allow a user to interact with your CarPlay app? That is where Templates come in.


Templates:

A Template overlay is what you give to your CPInterfaceController that is responsible for your user interaction. You can switch between templates, via replacing an interfaceController’s rootTemplate, or by transitioning to another template via an equivalent pushing/popping like the UINavigationController. There are a couple of different Templates to choose from in the current iOS 12 beta build, but the most important one for CarPlay navigation apps is the CPMapTemplate one, as this both displays navigation interface elements to your user and lets the user interact with the map controls, like panning/pinching the map or important alerts with actions.


HelloWorld XCode project

Here you can find my HelloWorld project (see screenshot of it at the beginning of this post) here. All the magic happens in the AppDelegate.swift, though I do not recommend following that lead when developing your own custom CarPlay app. Note: XCode 10 Beta 4 or later is needed to run this project.


Useful links

Some links that could help you get started:

- Documentation for CarPlay navigation apps: https://developer.apple.com/documentation/carplay

- WWDC 2018 video explaining the basis concepts and some common programming examples: https://developer.apple.com/videos/play/wwdc2018/213/

- To apply for your app to be allowed as a CarPlay navigation app: https://developer.apple.com/contact/carplay/


[ref] https://blog.flitsmeister.nl/start-developing-your-navigation-app-for-carplay-6e4c6c2b4e47



?

List of Articles
번호 분류 제목 글쓴이 날짜 조회 수
481 Develop [ios] UIAlertView 초간단 샘플 ㅎㅎ hooni 2013.10.14 46177
480 Develop [ios] UDID와 UUID (디바이스의 Unique Identifier) file hooni 2013.04.23 27379
479 Develop [ios] UDID 사용 제한에 따른 대안들 hooni 2014.03.13 4009
478 Develop [ios] Touch ID 적용 샘플 코드 (예제) file hooni 2015.02.23 751
477 Develop [ios] Thread Loop 내에서 UI 업데이트 방법 hooni 2015.01.03 916
476 Develop [ios] TextField 특정 문자만 사용하도록 하기 hooni 2014.06.30 2769
475 Develop [ios] Swift 4 String, Date, DateFormatter 예제 hooni 2018.10.18 1503
474 Develop [ios] Swift 4 Singleton inheritance hooni 2018.10.31 1683
473 Develop [ios] Swift 4 Dictionary 사용하기 file hooni 2018.11.29 2111
472 Develop [ios] StoryBoard(xib) 없이 프로젝트 만들기 file hooni 2015.02.12 1146
» Develop [ios] Start developing your navigation app for CarPlay without enrollment file hooni 2020.02.22 125247
470 Develop [ios] SQLite 사용하기(튜토리얼) + 샘플코드 file hooni 2014.03.28 3747
Board Pagination Prev 1 ... 26 27 28 29 30 31 32 33 34 35 ... 71 Next
/ 71