Skip to content
WEPSTechnologies

Service

Apple TV app development

tvOS applications in SwiftUI or UIKit, built around the focus engine, the Siri Remote and Top Shelf, through to App Store review.

An iOS build at a larger size gets rejected, and a layout the focus engine cannot reach has controls that, for the viewer, do not exist.

An iOS app does not become an Apple TV app by changing the deployment target. The code compiles, the screens appear, and then nobody can use it, because everything the app knew about the user's finger is now wrong. What transfers cleanly is everything under the interface: your models, your networking, your persistence, your business rules. If those are already separated from the view layer, a tvOS app is a new front end on a codebase you already own — and that is a genuinely different budget from starting over. What does not transfer is the interface, and not because of screen size. On iPhone the user touches the thing they want. On Apple TV there is no pointer: there is focus, a highlight the system moves between elements, and the focus engine decides where it goes. You do not move focus; you describe a layout the engine can reason about. That inversion is the whole job. The Siri Remote makes it sharper. Swiping is fast and imprecise, and newer remotes with a directional pad behave differently again from the glass touch surface. Both have to feel right. Then there are the things that exist only here: Top Shelf, the large area above your app in the top row of the home screen, which is a separate extension you have to build; sign-in without a keyboard, which is a design decision made early rather than a login screen ported from iOS; and on-device storage limits that mean content is streamed or fetched on demand by design.

Scope

How we deliver

  1. 01Read the existing iOS codebase to see how much is reusable below the view layer
  2. 02Design the focus model and the ten-foot layout before the screens
  3. 03Implement in SwiftUI or UIKit, with Top Shelf where it earns its place
  4. 04Test on real Apple TV hardware through TestFlight
  5. 05App Store submission, then a support path

Technologies

tvOS · Swift, SwiftUI, UIKit and TVUIKit · Focus engine and Top Shelf extensions · AVPlayer · TestFlight and App Store Connect

Questions

Can you port our iOS app to Apple TV?

Everything below the interface ports: models, networking, persistence, business rules. The interface does not, and not because of screen size — it is because there is no pointer. If your iOS app already separates view from logic, this is a new front end on code you own. If it does not, that separation is the first piece of work.

Why was our Apple TV app rejected?

The usual reasons are an interface that is obviously an iOS build at a larger size, focus that cannot reach part of the screen, a remote that does not behave the way the system remote behaves, or a sign-in nobody can realistically complete with a remote. Send us the rejection and we will tell you which.

Do we need the Top Shelf extension?

Not to ship. But it is the largest piece of screen your app will ever get, and it only appears if you build it. Most apps that skip it regret it later.

How long does a tvOS app take?

It depends almost entirely on how much of the existing app is reusable and how much has to be designed for focus from scratch. We give a range after looking at the codebase, not before.

Do you handle App Store submission?

Yes, including TestFlight on real hardware before it goes anywhere near review.

Related products: RecoraEdTech

Related services: tv application developmentwebos tv app developmentandroid tv app development

We use Google Tag Manager, Analytics, and an optional Facebook pixel to understand useful traffic. Ads appear on blog articles. See our privacy policy.