Skip to main content
added 1 character in body
Source Link

I'm working on a tvOS application that plays videos. On the bottom of the screen are a set of buttons I've created; Previous, Next, Pause, Play. Coming from an iOS background I'm so used to creating buttons for everything that it didn't even occur to me that maybe including the Play and Pause buttons is redundant as the Apple TV remote already contains this functionality.

I'm unsure if removing the buttons from the UI would help more than hurt. The new Apple TV remote contains a touch pad and I'm anticipating that users will be using that more than the physical buttons on the remote.

Are having both physical and UI buttons beneficialdetrimental in anyway?

I'm working on a tvOS application that plays videos. On the bottom of the screen are a set of buttons I've created; Previous, Next, Pause, Play. Coming from an iOS background I'm so used to creating buttons for everything that it didn't even occur to me that maybe including the Play and Pause buttons is redundant as the Apple TV remote already contains this functionality.

I'm unsure if removing the buttons from the UI would help more than hurt. The new Apple TV remote contains a touch pad and I'm anticipating that users will be using that more than the physical buttons on the remote.

Are having both physical and UI buttons beneficial in anyway?

I'm working on a tvOS application that plays videos. On the bottom of the screen are a set of buttons I've created; Previous, Next, Pause, Play. Coming from an iOS background I'm so used to creating buttons for everything that it didn't even occur to me that maybe including the Play and Pause buttons is redundant as the Apple TV remote already contains this functionality.

I'm unsure if removing the buttons from the UI would help more than hurt. The new Apple TV remote contains a touch pad and I'm anticipating that users will be using that more than the physical buttons on the remote.

Are having both physical and UI buttons detrimental in anyway?

Source Link

Include UI Play/Pause buttons even though remote contains same functionality?

I'm working on a tvOS application that plays videos. On the bottom of the screen are a set of buttons I've created; Previous, Next, Pause, Play. Coming from an iOS background I'm so used to creating buttons for everything that it didn't even occur to me that maybe including the Play and Pause buttons is redundant as the Apple TV remote already contains this functionality.

I'm unsure if removing the buttons from the UI would help more than hurt. The new Apple TV remote contains a touch pad and I'm anticipating that users will be using that more than the physical buttons on the remote.

Are having both physical and UI buttons beneficial in anyway?