The first ticket after a new iPhone is rarely a feature. It is whether the screen change means an app change, what to quote for development, and whether testing has to be laid out again. The sections below line up the numbers Apple has already printed, then split development hours from test cost. The rate stays yours. There is no total in this opening.
What the spec page actually says
iPhone 18 Pro is still a 6.3-inch Super Retina XDR at 2622 by 1206, 460 ppi. iPhone 18 Pro Max is still 6.9 inches at 2868 by 1320, 460 ppi. Those rows match the iPhone 17 Pro tech specs and the 6.9-inch grid Apple published for that generation. Divide by 3 for @3x and the logical sizes are still 402 by 874 pt and 440 by 956 pt. Apple does not print points. The division is ours, so you can search the repo for those numbers.
Brightness matches the previous generation too: 1000 nits typical, 1600 peak HDR, 3000 outdoor, 1 nit minimum. ProMotion still goes to 120Hz, with Always-On, P3, and the anti-reflective coating. None of that is a new layout constant. Size, battery, and list-price gaps between Pro and Pro Max are in our six-point comparison. Keep them off the adaptation timesheet.
What changed is the Dynamic Island. Apple’s September 2026 newsroom post calls it smaller and able to show three Live Activities at once, with Face ID still there. Neither that post nor the spec page gives the island’s width or height in points. An unchanged pixel grid does not prove the top safe-area inset is unchanged. Read safeAreaInsets in the new simulator. Do not reuse a constant measured on 17 Pro.
| iPhone 17 Pro / Pro Max | iPhone 18 Pro / Pro Max | |
|---|---|---|
| Pixels | 2622×1206 and 2868×1320, both 460 ppi | The same numbers. See the 18 Pro tech specs |
| Points (pixels ÷ 3) | 402×874 pt and 440×956 pt | Unchanged. The spec page does not print this row |
| Brightness and refresh | 1000 / 1600 / 3000 nits, 1 nit minimum, up to 120Hz | The same figures on the spec page |
| Dynamic Island | Present. Point size not listed on its own | Newsroom: smaller, up to three Live Activities |
Take the island’s point size from the simulator
Posts that claim the island grew by tens of percent disagree with Apple’s own word, smaller. This piece does not use a width or height that is absent from the spec page and the newsroom post.
Which apps must change code
An unchanged resolution does not close the ticket. Separate “redraw the asset catalog” from “check that the safe area still clears this island.”
- Constraints already follow the safe area, or SwiftUI does. You usually do not export a new @3x set for 2622×1206. You still open the iPhone 18 Pro and Pro Max simulators in portrait and landscape and look for controls under the island.
- Frames are hardcoded.
UIScreen.main.bounds, fixed 402, 874, 440, or 956, and splash or full-screen video cropped to the old island, all need code or asset work. A game locked to that point size may still fill a slab Pro, but the safe area and landscape still need a look. - You use ActivityKit. The island can hold three Live Activities. Check compact, minimal, and the case where yours sits next to another app’s. If you have none, record 0 hours on that row below.
- The folding iPhone Duo. Outer and inner displays are a different screen. Do not merge those hours into the slab table. See the iOS 27 device comparison.
iOS 27 adds a test path that is not about new pixels. WWDC26’s Modernize your UIKit app treats supported orientations as a preference the system can ignore in resizable environments such as iPhone Mirroring. If layout math assumes “always portrait, always this width,” run that path too.
# Use the hardcoded column only when this search is noisy rg -n "UIScreen\.main\.bounds|nativeBounds|874|402" --glob "*.swift"
How to count development
Hours below are one pass for the slab 18 Pro and Pro Max. No new features, no design-system rewrite. The left column already follows the safe area. The right column is what you use when the search above hits. Keep the Live Activities row only if you ship them; otherwise subtract 4 and 12. The sample rate is $70 per person-hour, a reading figure rounded from ¥500. Replace it. Do not scale the hours when you do.
| Development package | Already adaptive | Hardcoded layout |
|---|---|---|
| Both simulators, portrait and landscape, safe area | 4 h | 8 h |
| Remove fixed widths, heights, and nav bar height | 0 | 24 h |
| Dynamic Island and Live Activities | 4 h | 12 h |
| Splash, full-screen video, assets cropped to the old island | 0 | 8 h |
| App Store screenshots and preview | 4 h | 8 h |
| Development total | 12 h · about $840 | 60 h · about $4,200 |
How to count testing
Do not bill the safe-area glance twice. This sheet is the main-path regression, plus what the simulator does not show well.
| Test | Already adaptive | Hardcoded layout |
|---|---|---|
| Main path: sign-in, home, one core action. Pro and Pro Max, portrait and landscape | 8 h | 16 h |
| One device: island, three Live Activities, outdoor brightness | 4 h | 4 h |
| One smaller phone you still support, so the fix is not new-phone-only | 2 h | 4 h |
| Test total | 14 h · about $980 | 24 h · about $1,680 |
Three cash items stay off the hours:
- The phone. Layout starts in the simulator. The island, Live Activities, and outdoor brightness need one device after that. Price it from the local store, or from our four-market price note. Do not add it to $1,820 or $5,880.
- Apple Developer Program, $99 a year. This display did not create it. Teams already paying should not add it again.
- The Mac that runs the simulator. You need macOS with the iOS 27 simulator. If the office machine cannot take that Xcode, rent a cloud Mac for the window. The boundary for a Windows build is in the cloud Mac build guide. Rent is cash, not hours.
Do not buy a phone to read one inset
The first point-size reading is the simulator’s safe area. A device confirms the cutout, whether three Live Activities cover each other, and whether light controls survive the 3000-nit outdoor step. Reverse that order and the hardware budget leaves before the hours do.
Both ledgers together
Hours travel. The dollar figures are $70 an hour, rounded from ¥500 so an English reader can scan them. Replace the rate. If there are no Live Activities, subtract those development hours. The four test hours for “three activities” can shrink to a cutout check.
| Already adaptive | Hardcoded layout | |
|---|---|---|
| Development | 12 h · about $840 | 60 h · about $4,200 |
| Test | 14 h · about $980 | 24 h · about $1,680 |
| Hours total | 26 h · about $1,820 | 84 h · about $5,880 |
| Extra cash, not in the rows above | Phone price, $99 a year, cloud Mac rent | Same. A hardcoded layout does not justify a second phone |
Written on October 13, 2026. Pixels and brightness are from the iPhone 18 Pro tech specs, the 18 Pro and Pro Max spec page, and the iPhone 17 Pro tech specs. The island wording is from Apple’s September 2026 newsroom post. Hours are an example. $70 is a reading rate.
Questions
Does the new iPhone 18 Pro screen force a code change?
The pixel grid matches 17 Pro. Apps that follow the safe area usually do not redraw for resolution. Check the top inset in the new simulator anyway: the island is smaller, it can show three Live Activities, and Apple did not publish its point size. Hardcoded frames do need code changes.
What should development and test cost?
About 26 person-hours if the layout is already adaptive, about 84 if it is hardcoded. At the sample $70, that is about $1,820 and $5,880. Subtract 4 or 12 development hours when there are no Live Activities. Leave the phone and the yearly $99 off this sheet.
Can you test without the new iPhone?
Yes. Use the iOS 27 simulator for 18 Pro and Pro Max. Use one device for the island, three Live Activities, and outdoor brightness. If you have no Mac for that simulator, rent a cloud Mac for the window instead of buying another computer.
ZavCloud Cloud Mac
This simulator pass does not start with a new computer
The iPhone 18 Pro pixel grid did not move. The test still needs a Mac that can open the iOS 27 simulator. A dedicated cloud Mac can cover that window.
Keep the phone budget off the timesheet. The cloud node replaces the build and simulator machine, not the handset.