<img src="https://img.shields.io/badge/%20-ENTERPRISE-B10031" style="float:left"/><br /> <img src="https://img.shields.io/badge/iOS-V4-009727?logo=apple" style="float:left"/><br />

To set up a player, use `JWPlayerViewController`(iOS). Like any `UIViewController`, our view controller can be presented in the following ways:

• Presented directly (full screen)

• Embedded in a container view (partial screen)

The view controller uses the default JWP user interface. If you subclass the view controller, you can listen for all of the events related to the player and the user interface.

<br /> <hr />

## Implementation

Use the following steps to set up a player with the `JWPlayerViewController`:

<br /> <hr />

## Using Player APIs

### Content Handling APIs

To use the player content handling APIs, the `playerIsReady` (<a href="https://sdk.jwplayer.com/ios/v4/reference/Classes/JWPlayerViewController.html#/c:@M@JWPlayerKit@objc(pl)JWPlayerDelegate(im)jwplayerIsReady:" target="_blank">iOS</a>) event must have already been initiated. The `playerIsReady` event is called once the player property of the `JWPlayerViewController` object has finished setup. Then, the event is sent to the `JWPlayerDelegate`.

Unless set to another object, the `JWPlayerDelegate` is set to the `JWPlayerViewController`.

🚧



When subclassing either view controller, <strong>do not override the delegates in `JWPlayerView` or `JWPlayer`</strong>.

<br />

Values related to the currently loaded item such as `player.currentItem` will be set once the `didLoadPlaylistItem` delegate method is called.

<br />

The content handling APIs are listed below:

<br />

### Non-content Handling APIs

APIs that do not relate to content handling can be accessed and used prior to the `playerIsReady` event being initiated.

The non-content handling APIs are listed in the following table.

<br />