Device Activity or the "Screen Time API": Which One Should You Use?

One of the first questions iPhone developers ask when building a wellbeing or screen-time app is: "Does Apple have a Screen Time API that lets my app access the same information I see in Settings?"

The short answer is no. Apple's Screen Time feature is part of the iPhone's own system. Third-party apps cannot simply open Apple's Screen Time database and read everything inside it. Instead, Apple provides several separate technologies for developers. Each one solves a different problem, and the important thing is to understand what each is actually designed to do.

First, what do people mean by "Screen Time API"?

When people say "Screen Time API," they are usually talking about several different things without realizing it. There are actually different tools for:

• Getting permission from the user
• Letting the user choose apps
• Blocking apps
• Scheduling when apps should be blocked
• Detecting when a usage limit has been reached
• Showing usage information

Apple separates these responsibilities, so there is not one single API that does everything. Think of it like building a car: you do not ask "should I use the engine or the car?" The engine, brakes, steering and wheels all have different jobs. Apple's wellbeing system works the same way.

What is Device Activity?

Device Activity is mainly about monitoring and scheduling. It allows an app to tell the system things such as "watch this group of apps during these hours" or "tell me when this selected group of apps reaches a certain amount of usage."

It is especially useful when the app needs to continue doing something after the main app has been closed. A focus app might want to monitor social media during working hours, detect when a user reaches a daily usage limit, start or stop restrictions at certain times, and keep enforcing a schedule when the user is not in the app. That is where Device Activity becomes useful.

What Device Activity does not do

Device Activity is not Apple's complete Screen Time system. It does not give your app direct access to everything the user sees in the iPhone's Screen Time settings.

There are also important limitations. Apple restricts how short a scheduled monitoring period can be, a developer cannot simply say "start monitoring exactly three minutes from now." And there are situations where the system decides when monitoring and reporting work actually runs. Developers cannot treat Device Activity like an alarm clock that fires at an exact second. It is better to think of it as a system managed monitoring and scheduling service.

What if you want to show usage?

That is the job of another technology: Device Activity Reports. If your app wants to show "you spent 2 hours on social media today" or "your most-used category this week was entertainment," you use Apple's reporting system. The report is generated in a separate part of the app and shares the information with the main app when necessary.

What if you want to block apps?

Device Activity is not responsible for actually blocking anything. That job belongs to Apple's Managed Settings system. A simple way to understand the relationship:

• Family Controls: who can be managed?
• App selection (Family Activity Picker): which apps did the user choose?
• Managed Settings: what should be restricted?
• Device Activity: when should the restriction happen?
• Device Activity Reports: what usage information can be shown?

These systems work together. Imagine a user chooses Instagram and TikTok and says "block these apps from 9 AM to 5 PM." Apple asks for the necessary permission, the user selects the apps, your app stores those selections, Device Activity monitors the schedule, Managed Settings applies the restrictions, and the system keeps enforcing them even when your main app is closed. Device Activity alone is not enough to build a complete wellbeing app.

So which one should you use?

It depends on what your product needs:

For a typical wellbeing or focus app, you will need several of these together. The important point: you do not choose Device Activity instead of Screen Time. Device Activity is one part of Apple's system for building screen-time-related features.

A practical example

Imagine you are building an app called "Focus." Your user wants: "Block social media from 9 AM to 5 PM on weekdays and show me how much time I spend on those apps."

First, the user gives the app permission to manage selected apps. Then the user chooses which apps should be included, and your app remembers those choices. The blocking system handles the restrictions, the scheduling system tells the app when they should apply, and the reporting system provides usage information for the dashboard. The main app brings all of this together.

The user sees one feature: "Focus Mode." Behind the scenes, several Apple technologies are working together to make it possible.

One important warning about historical data

This is one of the easiest mistakes to make when designing the product. On Android, it is possible to access historical app-usage information the phone has already recorded. That can make it tempting to assume iPhone works the same way. It does not.

If someone installs your iPhone app today, do not promise you can show them their complete Screen Time history from the previous month. Your product should clearly communicate when tracking begins, "we'll start tracking your selected apps from today" is much safer and more accurate than pretending your app can access Apple's historical Screen Time database.

If you are coming from Android

The differences become even clearer if you have already built this type of product for Android. There, you can generally access a list of installed apps, retrieve historical usage information, and use accessibility capabilities to detect when another app comes to the foreground.

On iPhone, those concepts do not map directly. There is no equivalent of "give me every installed app," no equivalent of "give me Apple's entire Screen Time history," and no approach where your app simply watches another app open and kicks the user out. Apple expects developers to use its own privacy-controlled system for app selection, restrictions, monitoring and reporting. The full comparison is in our companion guide, what actually changes when you ship the same app on iOS and Android.

The takeaway

There is no single public Apple API that gives third-party apps everything inside the iPhone's Screen Time settings. Instead, Apple gives developers a set of separate tools. For a typical wellbeing or focus product, the combination is roughly:

Permission → App Selection → Restrictions → Scheduling → Reporting

Each part has a different responsibility. So the question should not really be "should I use Device Activity or Screen Time?" The better question is: "What does my product need to do, and which Apple technology is responsible for each part?" Once you look at it that way, Apple's system becomes much easier to understand, and much harder to misuse or promise something the platform cannot actually deliver.