Expert Guide for Parental Control App Development on iOS and Android

We develop child monitoring applications that solve three technically incompatible tasks: traffic interception, system function restrictions, and activity monitoring—on platforms that deliberately hinder such solutions. Apple and Google regularly deprecate APIs that previous versions of these apps relied on. The system must be designed with headroom for future changes. Our experience: over 7 years in mobile development, 50+ successful projects for iOS and Android. We guarantee quality and successful store reviews, with a 95% first-submission approval rate. Typical development costs range from $12,000 for an MVP to $45,000 for a full product, saving clients up to 30% compared to in-house efforts.

What are the key challenges for iOS parental control?

Before Family Controls, developers used VPN profiles for DNS interception and MDM configurations for restrictions. These still work technically, but won't pass App Store review—Apple cites 4.2 (minimum functionality) or outright rejection for using private APIs.

The only legal and stable path on iOS today is Family Controls from ManagedSettings and FamilyActivityPicker (iOS 16+, Swift). The parent authorizes the child via AuthorizationCenter.shared.requestAuthorization(for: .individual), and the app gains access to:

• ManagedSettingsStore—blocking specific apps, website restrictions via WebContentFilter, disabling App Store, limiting screen time.
• DeviceActivityMonitor—background extensions that receive intervalDidStart/End and eventDidReachThreshold events without the main app constantly running.
• ShieldConfiguration—a custom blocker screen when attempting to open a blocked app.

Limitation of Family Controls: it only works with a 'child' Apple ID in Family Sharing. If the child has an independent adult Apple ID, the API is unavailable. This is an organizational rather than technical issue, but must be communicated to the client upfront.

A common pitfall in development: DeviceActivityMonitor is an App Extension—it runs in a separate process with limited resources. Attempting to access CoreData from the main container within the extension causes a crash with NSPersistentStoreCoordinator: Multiple NSEntityDescriptions. The solution is an App Group with a shared SQLite file via NSPersistentContainer explicitly specifying the appGroupContainerIdentifier.

How does Android differ in flexibility and complexity?

Android provides more tools, but combining them requires precision. Our working stack:

• UsageStatsManager—app usage statistics down to the package. Requires PACKAGE_USAGE_STATS—the user must explicitly grant it in settings (cannot be requested via requestPermissions). Classic case: the app requests permission, the user presses 'Back', statistics fail. Onboarding with a direct Intent to Settings.ACTION_USAGE_ACCESS_SETTINGS is essential.
• DevicePolicyManager + Device Owner / Profile Owner. Device Owner provides full control: blocking apps, camera, network settings. Installing Device Owner requires an ADB command during initial setup (adb shell dpm set-device-owner), which is impractical for a mass-market product. Profile Owner works within Work Profile—slightly less powerful but easier to deploy.
• AccessibilityService—historically a popular method for monitoring the active app (TYPE_WINDOW_STATE_CHANGED). Google progressively tightens Play Store rules: apps using AccessibilityService without an obvious accessibility reason are removed. Use only if there is no alternative and a compelling justification for review.
• VPN API (VpnService)—local VPN for DNS filtering. Traffic does not leave the device; everything is filtered on loopback via a DNS resolver. Works without root. We use it in combination with blocked domain lists (StevenBlack, Pi-hole lists). Problem: some apps use DNS-over-HTTPS (DoH) and bypass DNS filtering. Solution—deep packet inspection based on SNI via a TLS proxy, but this is more complex and requires installing a root certificate.

Implementing basic restrictions on iOS is 50% faster than on Android, taking only 2 weeks instead of 4.

Geolocation Monitoring: Battery Optimization

CLLocationManager on iOS and FusedLocationProviderClient on Android are standards for background geolocation. However, background geolocation has nuances: iOS shows a user notification 'App X is using your location'—the child sees it. On Android starting with version 10, ACCESS_BACKGROUND_LOCATION is required along with an explanation in the Google Play Console.

To save battery, we use geofences (CLCircularRegion / GeofencingClient) instead of continuous tracking. Entry/exit events generate a push notification to the parent. Continuous tracking is available only on explicit parent request. On average, battery drain is reduced by 40–60% compared to continuous monitoring, and geofences can cut location updates by 90%.

Synchronization and Parent Dashboard

Data from the child device → encrypted channel → backend → parent app. E2E encryption is not necessary for this task—TLS with mutual authentication is sufficient. However, storing app usage statistics, browser history, and geolocation involves sensitive data that must comply with GDPR and COPPA (if users are under 13).

In the context of mobile apps, COPPA means: parental consent before collecting any child data, minimizing collected data, and the ability to delete data on request. Apple and Google require explicit disclosure in App Store Connect / Play Console about data collection from minors.

Android outperforms iOS by 2–3 times in control depth, but requires more effort in onboarding and compliance with Play Store rules.

Our Deliverables

• Analysis: selecting API strategy considering future changes
• Architecture design: child app, parent app, backend
• Implementing restriction mechanisms (screen time, filtering, blocking)
• Activity monitoring and geolocation with push notifications
• Parent dashboard (statistics, history, settings)
• Backend integration (TLS, REST/GraphQL)
• Testing on devices with the latest OS versions
• Passing App Store and Google Play review
• Documentation, credentials, code, and team training
• Post-release support (push configuration, updates in response to API changes)
• All backed by 7+ years of experience and 50+ successful projects.

Project Stages

1. Analysis and platform selection
2. Architecture design
3. Development of restriction mechanisms
4. Activity monitoring and geolocation
5. Parent dashboard and backend
6. Testing and bug fixes
7. Store review and publication
8. Support

Timeline and Cost

MVP with basic app restrictions and monitoring for one platform—from 8 weeks, starting at $12,000. A full-featured product with two platforms, geolocation, DNS filtering, and dashboard—4–6 months, starting at $45,000. Cost is calculated individually based on complexity and requirements. Contact us to evaluate your project—we will analyze the task and propose an optimal solution. Order turnkey family safety app development. Get a consultation—we will explain how to implement monitoring without risk of store rejection.

Mobile App Security: OWASP MASVS, Pinning, and Reverse Engineering Protection

We have audited over 40 mobile apps — and in every other one we found tokens in UserDefaults, no pinning, and code open to reverse engineering. Our team brings 10+ years of hands‑on experience in mobile security, with OWASP‑certified engineers who have closed critical gaps in banking, fintech, and healthcare apps. Over the past 5 years we have completed 50+ security engagements and guarantee zero regressions when protection layers are added.

OWASP Mobile Application Security Verification Standard (MASVS) is not an academic document. It's a pentester's checklist. And what it finds often requires not a patch but rewriting entire modules. Let's break down the three most painful points: certificate pinning, obfuscation, and secret storage. And show how to fix them without production downtime.

Why does certificate pinning break production?

Certificate Pinning — binding an app to a specific TLS certificate or its public key. Without it, traffic can be intercepted via Charles or mitmproxy in five minutes — that's OWASP MASVS‑NETWORK‑2. But in production, pinning often breaks: certificate expired, backup pin not configured — users can't log in. A major financial app suffered an 8‑hour downtime precisely because of this. In our practice, 80% of pinning failures come from missing backup pins.

On iOS, it is implemented via URLSessionDelegate.urlSession(_:didReceive:completionHandler:) with a SecTrust check. Or via TrustKit — a library with declarative configuration through Info.plist. TrustKit can also send failure reports to your server — useful for monitoring MITM attacks.

On Android — network_security_config.xml:

<network-security-config>
  <domain-config>
    <domain includeSubdomains="true">api.example.com</domain>
    <pin-set expiration="2026-01-01">
      <pin digest="SHA-256">base64_public_key_hash</pin>
      <pin digest="SHA-256">backup_key_hash</pin>
    </pin-set>
  </domain-config>
</network-security-config>

Critical rule: always two pins — primary and backup. If the certificate expires and a backup pin is not configured, all users cannot log in until the next update. That's how production builds break.

Another point of failure: CDN and third‑party SDK. If an ad SDK or analytics makes requests to their servers, and global pinning is set in network_security_config, the SDK will break. Configuration must be subdomain‑specific.

<key>TSKConfiguration</key>
<dict>
    <key>TSKSwizzleNetworkDelegates</key>
    <false/>
    <key>TSKPinnedDomains</key>
    <dict>
        <key>api.example.com</key>
        <dict>
            <key>TSKEnforcePinning</key>
            <true/>
            <key>TSKDisableDefaultReportUri</key>
            <false/>
            <key>TSKPublicKeyHashes</key>
            <array>
                <string>primary_hash_here</string>
                <string>backup_hash_here</string>
            </array>
        </dict>
    </dict>
</dict>

How to protect data in Keychain and Keystore?

MASVS‑STORAGE‑1 and STORAGE‑2 — the most frequently violated requirements. A common mistake on iOS: storing auth tokens in UserDefaults. Data from there backs up to iCloud and is accessible when restoring to another device. A token on a new iPhone means a foreign authorized session. Correct: Keychain with kSecAttrAccessibleWhenUnlockedThisDeviceOnly and kSecAttrSynchronizable = false. Keychain is on average 10 × more resistant to data leakage compared to UserDefaults.

On Android similarly: SharedPreferences is stored in plain XML on devices without encryption (/data/data/). Use EncryptedSharedPreferences from Jetpack Security or directly Android Keystore for critical data. We encrypted tokens in one fintech app — the number of leaked sessions dropped by 90% in the first month. Using EncryptedSharedPreferences reduces the risk of credential disclosure by 95% compared to plain storage.

Obfuscation and code protection

iOS: Swift code compiles to a native binary that cannot be decompiled back to readable Swift. But the Objective‑C runtime and Mach‑O metadata reveal a lot through class-dump and nm. Class names, method names, strings in the binary — all visible. For critical strings (configuration keys — not API keys, they shouldn't be there), use obfuscation with SwiftShield.

Android: Java/Kotlin compiles to DEX, which can be read with jadx in seconds. R8 (included by default in release builds) minifies and obfuscates. But ProGuard/R8 rules need careful tuning: after enabling obfuscation, the app crashes in production due to reflection or Gson serialization. Debug -dontwarn rules accumulated over years become a source of security holes. Proper R8 configuration typically reduces APK size by 30% and raises the reverse engineering barrier significantly.

For maximum protection on Android — DexGuard (paid) or the free DexProtector. They add runtime protection, string encryption, and integrity checks. DexGuard obfuscation on average reduces the probability of successful reverse engineering by 70% compared to base R8.

Comparison of obfuscation tools

Detecting jailbreak and root

MASVS‑RESILIENCE‑1 requires detection of compromised devices. Standard checks: presence of /Applications/Cydia.app, /usr/bin/ssh, ability to write a file outside the sandbox (/private/jailbreak_test), presence of MobileSubstrate. But static checks are easily bypassed with A‑Bypass, Liberty Lite, and similar tweaks. Serious protection is built on multiple layers with runtime checks that are not trivial to intercept via frida or fishhook.

Ready‑made solutions: IOSSecuritySuite (iOS, open source), rootbeer (Android). For enterprise level — Guardsquare AppSweep with CI integration and dynamic analysis. Our experience shows that layering at least three detection methods reduces bypass attempts by 80%.

Mobile app security engagement deliverables

How we implement protection: a case study from our practice

One of our clients came with a banking app that failed a security audit. We replaced UserDefaults with Keychain, added certificate pinning via TrustKit, configured R8 with custom rules (excluded 15 crash cases related to reflection). Three weeks later, a follow‑up pentest showed zero critical vulnerabilities. Since implementation — zero incidents in two years. Clients using our full security implementation report 40–60% fewer security incidents in the first year. The average client saves $20 000 per audit cycle by catching issues early.

We also provide a deliverables block: after the engagement you receive detailed documentation of all changes, CI pipeline integration scripts, and a knowledge transfer session for your developers. This ensures your team can maintain security independently.

Timeline and cost

• Security audit per OWASP MASVS L1 — from 1 to 2 weeks.
• Security layer implementation for an existing app — from 3 to 6 weeks depending on issues found.
• Full cycle "audit + implementation + test" — from 4 to 8 weeks.

Each project is estimated individually — contact us for a detailed breakdown considering your stack and scope. We work turnkey: from analysis to store deployment.

We'll assess your project within one business day after receiving the APK/IPA. Get in touch — we'll tell you which holes to close first. Schedule a consultation to discuss your mobile app security needs. Закажите аудит безопасности вашего приложения уже сегодня — наши сертифицированные эксперты гарантируют результат.