Apple ships hundreds of new APIs, frameworks, and features with every iOS release. Most of them look great in a demo. Looking at it as someone who maintains 12 production apps day to day, I ask a different question: which ones actually add value?
It has been six months since the iOS 18 release. Here is what I integrated into my apps, what I skipped, and why.
Apple Intelligence: who is it for?
Siri, Notification Summary, Writing Tools, Image Playground. Huge from a marketing angle. What about the practical value?
AI features at the current release (September 2024) are not available to most users. US English first, then other languages slowly. Turkish support landed in 2025 but it is still limited.
On top of that: Apple Intelligence runs on-device, only on iPhone 15 Pro and newer. A large chunk of the install base cannot even use these features.
My call: do not integrate yet. Come back in two or three years when the install base matures and there is a real need. Right now the ROI is marketing, not product.
Control Center redesign
iOS 18 makes Control Center customizable and you can add widgets to it.
Apps can now ship their own Control Center widget via the ControlWidgetButton API.
MVP must have? No. The default behaviour already works. A custom widget is only worth it for a specific use case, like an instant timer start or a quick action trigger.
I tried it in Dentii. A “Start brushing” button from Control Center. Three users used it in a week. Not worth the investment, I pulled it back out.
In a new app it is a 1 to 2 hour task. Retroactively adding it to existing apps is low priority.
Tinted app icons
iOS 18 tints Home Screen icons with the user’s chosen colour. A “tinted mode” on top of dark mode.
Dev impact: ship a grayscale or tintable version of the icon. An AppIcon asset catalog with a “Tinted” variant.
The work is 1 to 2 hours. I updated all of my apps. The user’s Home Screen looks consistent, a small but nice detail.
Going forward I add it by default on new releases. On older apps it is a quick win.
Interactive Widgets (landed in iOS 17)
They arrived in iOS 17 and expanded in iOS 18. Buttons and toggles work inside a widget. App Intents integration.
This one is genuinely valuable. A widget can now support one-tap actions:
Timer start/stop. Task completion. Quick mood logging. Favourite toggle.
Dentii’s “I brushed today” toggle is on the widget. Click, state updates, sync. No need to open the app.
This should be a standard feature in new apps. It lifts retention.
SwiftData improvements
SwiftData landed in iOS 17, and iOS 18 is where it matured:
The @Index macro (indexing is now declarative). A custom DataStore protocol. History tracking (a change tracking API). Better CloudKit integration.
For new projects SwiftData is increasingly the right call. A year on, it is safer in production than it used to be.
Am I switching existing CoreData projects? No, not unless there is a major refactor reason. CoreData still works.
TipKit framework
A framework for giving users hints. “Have you tried this feature?” style tooltips.
“Did you know” notifications after onboarding. Usage rules, eligibility, display logic, all automated.
It was introduced in iOS 17. iOS 18 brought bug fixes and polish.
Evaluation: a good framework with a narrow use case. Built-in onboarding flows are usually enough. TipKit only earns its place on mature products where you add features years after launch.
For a small startup app TipKit is usually overkill. For a 5+ year old mature product it is worth it.
StoreKit improvements
iOS 18 added to StoreKit 2:
Transaction.jwsRepresentation for safer validation. Subscription group management APIs. Win-back offer support.
Win-back offers especially are valuable. You offer a discount specifically to a cancelled subscriber, with native handling by Apple.
I added it to Dentii’s subscription flow. Cancel rate dropped from 12% to 8%.
Any iOS app on a subscription model benefits. One to two days of work, clear ROI.
Live Activities improvements
Live Activities arrived in iOS 16. iOS 18 brought:
More Dynamic Island interactivity. Longer duration (hours stretch to days now). Better customization.
The ideal use case for a Live Activity is time-sensitive ongoing information. Sports scores, order tracking, timers.
Dentii has a “brushing timer” Live Activity. On a locked iPhone screen you see the countdown. On iPhone 14 Pro and newer it is always visible in the Dynamic Island.
In a new app, if there is a time-sensitive feature, Live Activity is worth considering.
Background task improvements
BGTaskScheduler landed in iOS 13 and got wider in iOS 18. A longer background refresh window, improved task prioritization.
More reliable for periodic tasks like email sync, data fetch, or sensor reading.
It is becoming practical to push non-user-facing work to the background. iOS limits are relaxing (still strict, still not abusable).
CarPlay expanded
iOS 18 opens up more car integration (climate control, vehicle status). Automaker implementation will take years.
Impact for an app developer: only relevant if you live in the automotive ecosystem.
For most apps, skip.
App Intents expanded
The AppIntents framework exposes user actions to Siri, Shortcuts, and widgets. iOS 18 added:
File-based AppIntent. Image-based AppIntent. Deep link AppIntent.
A user can tell Siri “start brushing in Dentii”. They can wire it into a Shortcut. They can fire the action from a widget.
High ROI investment. You are moving user workflow outside your app, which is powerful for mature apps.
In a new app, expose the key actions as AppIntents. It is an extra one to two hours on top of the default behaviour.
What I integrated vs skipped
Integrated (across all iOS 17+ apps):
Tinted icons. Interactive widgets (where they make sense). Live Activities (for time-sensitive apps). StoreKit 2 win-back offers. AppIntents for key actions.
Skipped (for now):
Apple Intelligence (install base too small). Control Center widgets (limited use cases). TipKit (overkill for small apps). CarPlay expansion (not relevant).
Watching:
SwiftData (new projects only, more as it matures). Background task improvements (case by case).
Decision framework
For every iOS feature I ask:
- Install base coverage: what percentage of my users does this feature reach? Under 30%, shelve it.
- User value: does the user experience suffer without it? Yes, integrate. No, maybe skip.
- Development cost: implementation plus testing, how much? 1 to 2 days, I can try it. 2+ weeks, be careful.
- Maintenance burden: will Apple deprecate this in two years? Brand new APIs carry that risk.
The answers to those four decide it.
Takeaway
iOS 18 is not a huge release, it is a refinement release. A few important features (tinted icons, interactive widgets, StoreKit improvements) and a few hype features (Apple Intelligence).
You do not have to integrate every feature. Check the use case fit. Decide on install base, user value, development cost, and maintenance.
Apply that discipline to every new iOS release. Apple announces 50+ features per version. Maybe 5 to 10 are relevant to your app. Ignore the rest.