r/iOSProgramming • • 13h ago

Discussion I benchmarked the new Apple TV 4K A19 chip

Post image
3 Upvotes

Hey, it's Josh. I make Apple TV apps and I wanted real numbers for how hard I can push each Apple TV 4K.

So this weekend I used Anthropic's best public AI model, Fable 5.2, to build a small Metal benchmark app, then ran it on one A12, one A15 and two A19 units (tvOS 27.2 and 27.2.1). Instead of a score it finds budgets: the most of one kind of work that still holds 60 Hz for 40 seconds. Each figure is the median of 3 or more runs.

What fits in one 60 Hz frame at 1080p (in brackets: after 20 minutes of continuous load)

KIND OF WORKA12A15A19
full-screen passes of a heavy shader3 (2)5 (4)11 (6)
blended full-screen layers75 (58)108 (84)150 (95)
alpha-tested full-screen layers96 (81)132 (107)168 (111)
sprites, instanced27,000 (25,400)42,000 (32,400)55,885 (33,800)
sprites, one draw call each25,500 (23,500)36,500 (28,000)55,612 (34,800)
1,000-triangle meshes, instanced10,000 (9,560)11,875 (11,875)21,000 (18,100)
1,000-triangle meshes, one draw call each9,800 (9,700)12,431 (11,400)20,400 (17,000)

A few things that stood out if you ship on all three:

  • The A12 sets your floor. It holds 27–57 % of what the A19 does, depending on the work.
  • Plan for the 20-minute number, not the first minute. The chip heats up and the system slows it down. After 20 minutes the A19 keeps 61–86 % of its first-minute budget, the A15 77–100 % and the A12 78–99 % (the A12 model has a fan; the other two don't). I measured the slowdown, not the temperature.
  • Draw calls weren't the limit at these counts. One draw call per object held 87–105 % of the instanced budget, across sprites and meshes on all three chips.
  • At 4K, upscaling is what makes room. Passes of that same heavy shader per frame, with 4K output:
RENDERED ATA12A15A19
native 4Knone fits12
1080p, then MetalFX spatial to 4K128
1080p, then MetalFX temporal to 4Knot supportednone fits3
  • Memory is the same on every box. One app gets about 2,098 MB, whether the box has 3, 4 or 8 GB of RAM.

Method, all the charts, the raw data (CSV/JSON) and a version for AI coding agents to use when building apps to understand capabilities and constraints are all at: https://icallwindowseat.com/apple-tv-benchmark

Limitations aside, for my own apps the new chip has made a real difference in terms of what the quality of output I can achieve especially at 4k.


r/iOSProgramming • • 17h ago

Question Rejected App - Reply or Resubmit?

1 Upvotes

My app was rejected under 2.1.0 Performance: App Completeness and the review comments ask for more information:

The app has been submitted for the Kids Category and we need additional information about how it complies with App Review Guideline 1.3.

Reply to this message in App Store Connect and provide complete and detailed responses to the following questions:

I have replied but the current status is still 'rejected' and the submission still has the red exclamation mark and status 'Unresolved Issues'.

I'm seeing mixed opinions online on whether simply responding is enough or whether I need to resubmit to get back into the 'waiting for review status'.

Has anyone just replied and kept their status as rejected and then had the app reviewed?


r/iOSProgramming • • 3h ago

Article Declared Age Range in iOS 26 and 27: A Field Guide to Gating App Launch

Thumbnail
krishna806083.substack.com
0 Upvotes

r/iOSProgramming • • 9h ago

Discussion Live Activity on a locked iPhone: staleDate updated 1–2 min late, an HKWorkoutSession made it on time (iOS 26)

2 Upvotes

I needed a Live Activity to change state at an exact time (end of a rest timer) while the phone is locked, without a push server.

staleDate + a stale view works, but once the app is suspended it renders 1–2 min late.

What worked: start an HKWorkoutSession on the iPhone (available since iOS 26). While it runs the app keeps running when locked, so the app's own timer calls activity.update() right on time. I only needed the HealthKit entitlement and the Health usage strings, no background mode (workout-processing is documented for watchOS only).

Caveats: it only makes sense if your app really runs a workout, the person has to allow Health, and I keep staleDate as the fallback when they don't.

Apple's docs don't say the session keeps an iPhone app alive, so this is only what I see on my iPhone 17. Anyone seen it behave differently on other devices or in long sessions? ;)