How to disable app installs on a child’s phone
17 mins read

How to disable app installs on a child’s phone

Last updated: October 22, 2026

Key Takeaways

  • Blocking app installs keeps new apps off the phone; it is different from hiding apps, limiting use, or filtering websites.
  • On an iPhone, Screen Time can block installs, and Ask to Buy can add approval for downloads.
  • On Android, Family Link and Google Play approval settings are the usual way to stop new installs.
  • Approval is often the middle ground when you do not want a full lockout.

Quick Answer

Father and toddler using a smartphone on the floor

Use the store controls, not just screen-time limits, if you want to stop app installs on a child’s phone. On iPhone, Screen Time can set Installing Apps to Don’t Allow. On Android, Family Link can require approval for Google Play downloads. Apple and Google both document these controls in their support pages, and families should check the exact menus on the device or consult a professional if the phone uses a custom setup.

Want to stop new apps from landing on the phone? Then the fix is app store purchase and install restrictions, not general screen-time limits. This is the setting that blocks downloads from the App Store or Google Play before they appear on the device.

A child can often slip around app-time rules by grabbing a new app, signing up again, or switching to a different video, chat, or game app. Because the phone already has the app store account on it, the right restriction is usually purchase approval or a password requirement for installs. For Apple devices, that lives in Screen Time and Family Sharing. For Android, it usually runs through Google Play and Family Link.

What app install blocking actually does

App install blocking stops new apps from being added through the store, which is different from hiding apps, limiting usage, or filtering websites. On an iPhone, the child can still use apps already installed unless you also set time limits or other controls. On Android, the split is the same: new installs can be blocked while existing apps stay put.

This distinction trips up a lot of parents. “Parental controls” sounds like one switch that handles everything, but it does not. A child with an existing messaging app may still use it for 15 minutes, 2 hours, or longer unless you also set app limits. This article stays on the install gate itself, since that is the part that prevents a new app from appearing in the first place. If the setup is unusually complex, consult Apple Support, Google Support, or a qualified technician.

Honestly, the trade-off is clear: tighter install control adds friction when a child needs a legitimate app for school, travel, or family use. If you want fewer surprises, this is the right restriction. If you want the child to add apps freely and only manage time spent, this is the wrong tool.

On Apple, the key terms are Screen Time, Ask to Buy, and Allowed Apps. On Android, the terms are Family Link, Google Play parental controls, and approval for purchases and downloads. These are the controls to look for in the device menus, not “screen time” alone. For a broader setup path, this guide fits under the hub on child device access and privacy controls.

How to disable app installs on an iPhone with Screen Time

Adult showing a smartphone to a child

On an iPhone, you can block app installs by turning off app installation in Screen Time and, if needed, forcing a passcode for the App Store. This is the cleanest way to stop new apps from appearing without removing the child’s existing apps.

Start in Settings and move to Screen Time. Not set up yet? Turn it on first, then create a Screen Time passcode the child does not know. Next, open Content & Privacy Restrictions and switch it on. From there, go to iTunes & App Store Purchases. Set Installing Apps to Don’t Allow. That blocks new app installs from the App Store on that device.

Need a second layer? Set Password Settings so the phone asks for the Apple account password or approval for every purchase. In family setups, Ask to Buy is the approval flow that sends a request to the parent’s device before the child can download paid or free apps, depending on the account setup. Apple’s own Screen Time and Family Sharing documentation describes these controls and how they interact.

If the goal is “no new apps at all,” the important step is Installing Apps: Don’t Allow. If the goal is “allow installs only when I approve,” the important step is Ask to Buy. Those are not the same. One can exist without the other.

A common slip is leaving the App Store icon visible and assuming that covers it. It does not. If installs are still allowed, the child can still add apps whenever the password is known or the approval flow is off. The sturdier setup is: Screen Time passcode, content restrictions on, app installs disabled, and account approval turned on if the family uses it.

For Apple’s terminology, the most relevant references are Apple Support’s pages on Screen Time and Ask to Buy. Those are the right source pages because the menus and labels change less often than blog advice does. Google search results about “parental controls” often mix together app blocking, web filtering, and usage timers, which are different jobs.

How to stop new apps on Android with Google Play and Family Link

On Android, the usual way to stop app installs is through Family Link and the Google Play approval settings tied to the child’s account. That setup lets a parent require approval before new apps are downloaded.

Open the Family Link app on the parent’s device and choose the child’s account. Then look for Controls or Google Play settings. The exact labels vary by phone maker and Android version, but the goal is the same: turn on approval for downloads and purchases, including free apps if the menu offers that option. The child then has to request approval before an app is installed from Google Play.

If the child’s phone is managed through a supervised Google account, the approval prompt can appear on the parent’s device. That is the key difference from simply setting a PIN on the phone itself. A phone PIN can stop someone from changing settings, but it does not by itself control app-store downloads. Family Link does.

One point gets missed often: Android devices can have more than one store or installer path, depending on the brand and region. If the child uses a Google Play install path, the Family Link and Play approval settings are the first place to lock down. If there is another app source on the device, you may need to review that source separately, because Google Play controls do not govern every third-party store. The path can split like a fork in the road.

Flexibility versus consistency is the trade-off here. Family Link is practical if the child uses one supervised Google account and you want installs to require permission. It is less tidy if the child uses multiple accounts, a second profile, or a manufacturer-specific app store. In those cases, the same app can come in through a different door.

For the official terminology, Google’s support pages for Family Link and Google Play parental controls are the source terms to look up. They explain the approval flow and how it applies to downloads and purchases. That is more reliable than a generic “block apps” setting, which may only hide icons or restrict content ratings.

How to require approval for app installs and purchases

Requiring approval is often the middle ground when you do not want a total lockout. It blocks surprise installs while still letting a parent approve a useful app in under a minute when needed.

On Apple devices, this is usually Ask to Buy through Family Sharing. When it is enabled, the child sends a request and the parent approves or declines from their own device. That approval flow can cover free apps, paid apps, and some in-app purchases depending on the account setup.

On Android, the equivalent is approval in Google Play through Family Link. The parent can often choose whether approval is needed for all purchases and downloads or only paid items. If you want to prevent a child from quietly adding a new game, the safer setting is approval for both free and paid downloads, not just paid ones.

Here is the practical order that keeps the setup from breaking later:

  1. Turn on the parent control app or account first, such as Screen Time on Apple or Family Link on Android.
  2. Set a passcode, Apple account password, or parent sign-in that the child cannot change.
  3. Open the app-store purchase settings and require approval for downloads.
  4. Set app installation to Don’t Allow if you want a hard block instead of an approval prompt.
  5. Check that the child’s device is signed into the supervised account you meant to control.

The last step matters because a device signed into the wrong account can bypass the restriction you just set. A child may also use an old account that is not under family control. That is why “the setting is on” and “the child is actually covered” are not the same thing.

Delay is the main drawback of approval-based control. If the child needs a new homework app on the way to school or a tool for a class assignment, somebody has to respond. On a family phone that is shared across a few children, a full block is often simpler. For many families, approval is still acceptable because it avoids a blanket lockout.

Common setup mistakes that let installs slip through

Usually, the failure is not the wrong setting; it is the wrong account. If the child can sign into a second Apple ID or Google account that is not in the family group, your restriction may not apply there. That is the fastest way around install limits.

Another mistake is using only content ratings. Age ratings can reduce what shows up in the store, but they do not always block app installs entirely. A store can still show approved-age apps, and a child can still download them unless you also set install permissions or approval requirements. Ratings are a filter, not a gate.

A third mistake is forgetting in-app purchases. You may block new installs and still allow a child to spend money inside an existing app. If the goal is to stop surprise spending as well as surprise downloads, turn on purchase approval for in-app buys too. On Apple, that is tied to Screen Time and family approval settings. On Android, that is tied to Google Play purchase controls.

A fourth mistake is assuming a device PIN is enough. A 4-digit or 6-digit device passcode can stop casual access, but it does not automatically control the store. Store controls live in the Apple and Google account layers, not just the lock screen.

One useful check is to try the exact path a child would use: open the App Store or Google Play, search for a free app, and see whether the device asks for approval. If it opens straight into download, the restriction is not tight enough yet. If it asks for a parent password or sends a request, the gate is working.

For Apple, Screen Time and Ask to Buy are the right terms. For Android, Family Link and Google Play purchase approvals are the right ones. Those names matter because support articles and menu labels use them, and the wrong search term can send you to screen-time limits when you needed install blocking.

What to do if the app store still lets downloads through

If downloads still work, check the account, the store, and the approval setting in that order. That usually finds the gap in under 5 minutes.

First, confirm the child is using the supervised Apple ID or Google account you intended. If not, sign out the extra account or remove it from the device where appropriate. Second, reopen the install setting: Installing Apps: Don’t Allow on Apple, or the Google Play approval setting in Family Link on Android. Third, test with a free app, because free apps reveal whether approval is truly required.

If the child’s device still bypasses the control, look for a second app source. Some Android phones include another store or a manufacturer app manager. A control on Google Play does not automatically reach every store that came preloaded on the device. On iPhone, the App Store is the main path, which makes the setup simpler.

This is also the point where many parents decide whether they want a hard block or an approval flow. A hard block is easier to enforce and harder for a child to poke at. Approval is more convenient and more adaptable, but it depends on fast parent response. Neither is universally better.

If you want the simplest rule for a younger child, use a full block on installs and keep in-app purchases off too. If you want some independence for an older child, use approval instead of a full block. That choice is the real policy decision behind the setting.

The core idea is simple: app install controls are the gate, not the whole house. If the only thing you change is screen time, the child can still install the app and use it later. If you change the store permissions, purchase approval, and in-app purchase settings together, the boundary is much harder to cross.

Can I stop my child from downloading new apps?

Yes. The cleanest way is to disable app installs in the store settings or require parent approval for every download. On iPhone, that is usually done through Screen Time and Ask to Buy. On Android, Family Link and Google Play approval settings do the same job. A device passcode alone is not enough.

How do I require approval for app installs?

Turn on the family approval feature tied to the app store account. On Apple, that is Ask to Buy in Family Sharing. On Android, it is Google Play approval through Family Link. Then test with a free app, because free downloads are the easiest way to confirm the approval prompt is actually active.

Can I block in-app purchases too?

Yes. In-app purchases are controlled separately from app installs, so they need their own setting. On iPhone, use Screen Time and the purchase controls tied to the account. On Android, use Google Play purchase approval settings. If you only block installs, a child may still buy things inside apps already on the phone.

Drafted with AI; not yet reviewed by a person.

Leave a Reply

Your email address will not be published. Required fields are marked *