Independent developer field notesWeekly Brief
Edition 3Week of Jul 13–Jul 19, 2026

Compliance and conversion start before session two

The highest-leverage work this week sits in release readiness and the first value moment, not in another feature sprint.

Apple has added social-media questions to its age-rating workflow, Google has clarified a September registration deadline, and RevenueCat reports that much of Android subscription underperformance occurs before a trial begins. These are different problems with the same lesson: inspect the path before users or reviewers reach a blocked state.

Week at a glance

What changed

01

Social features now change the App Store age-rating workflow

Apple added questions about social-media capabilities to the App Store Connect age-rating questionnaire. Beginning in September 2026, responses are required when submitting new apps, updates, or apps for notarization for alternative distribution.

Primary sourceApple DeveloperPublished Jul 9, 2026
02

Android app registration is becoming a distribution dependency

Google says developer verification protections take effect on September 30, 2026 in Brazil, Indonesia, Singapore, and Thailand across seven participating stores. Google also says Play developers should register remaining apps in Play Console by that date to avoid removal.

Primary sourceAndroid Developers BlogPublished Jul 15, 2026
03

The Android subscription gap appears before the trial

RevenueCat reports a median day-35 download-to-paid conversion of 0.9% on Android and 2.6% on iOS in its dataset, while trial-to-paid conversion is 32.5% and 32.6% respectively. It argues that much of the difference occurs before an Android user starts a trial and notes a selection-effect caveat.

ReportedRevenueCatPublished Mar 25, 2026
01

Store changes

Confirmed platform, policy, and distribution changes.

Social features now change the App Store age-rating workflow

Apple added questions about social-media capabilities to the App Store Connect age-rating questionnaire. Beginning in September 2026, responses are required when submitting new apps, updates, or apps for notarization for alternative distribution.

Why it matters
The classification depends on product behavior, not only the category selected in App Store Connect. A social feed or similar redistribution and interaction model can create release work even for an app that does not describe itself as social media.
Who should care
Apps with feeds, user-generated content, sharing, reactions, or content discovery features.
Suggested action
Inventory every feature that redistributes, amplifies, or enables interaction with user-generated content. Assign one product owner to confirm the questionnaire before the next submission.
Primary sourceApple DeveloperPublished Jul 9, 2026

Android app registration is becoming a distribution dependency

Google says developer verification protections take effect on September 30, 2026 in Brazil, Indonesia, Singapore, and Thailand across seven participating stores. Google also says Play developers should register remaining apps in Play Console by that date to avoid removal.

Why it matters
Registration is now part of release readiness, including for teams that distribute outside Google Play. Waiting for a blocked installation or removed listing makes the fix an incident instead of routine operations.
Who should care
Android developers distributing in the initial four countries or through multiple stores.
Suggested action
Check Play Console for unregistered package names, record ownership for every signing identity, and add registration state to the release checklist.
Primary sourceAndroid Developers BlogPublished Jul 15, 2026
02

Growth and monetization

Commercial patterns worth examining—not universal prescriptions.

The Android subscription gap appears before the trial

RevenueCat reports a median day-35 download-to-paid conversion of 0.9% on Android and 2.6% on iOS in its dataset, while trial-to-paid conversion is 32.5% and 32.6% respectively. It argues that much of the difference occurs before an Android user starts a trial and notes a selection-effect caveat.

Why it matters
The useful diagnostic is not that Android users are inherently less willing to pay. Teams should first verify whether users reach the paywall, see an eligible offer, understand the value, and begin a trial.
Who should care
Android subscription apps with weak install-to-paid conversion.
Suggested action
Instrument paywall reach, eligible-offer display, trial start, and trial-to-paid as separate events. Inspect the first-session path and Google Play offer configuration before changing trial length.
ReportedRevenueCatPublished Mar 25, 2026
03

Products and categories moving

Observed product movement and the limits of what it proves.

Apple refreshed the design source of truth for platform 27

Apple released Figma and Sketch kits for iOS, iPadOS, and macOS 27. The kits include Liquid Glass updates, broader component and state coverage, names aligned more closely with code, improved resizing, and macOS dark mode.

Why it matters
A shared design source reduces handoff ambiguity and makes it easier to compare an app against current platform behavior before custom styling spreads through the product.
Who should care
Teams preparing interface work for Apple platform 27 releases.
Suggested action
Replace one outdated local component reference with the matching official kit component, then verify its states, resizing, and dark appearance before widening the migration.
Primary sourceApple DeveloperPublished Jun 23, 2026
04

One move this week

A bounded action to consider, grounded in this edition.

Complete the social-capability audit before the next build

Apple says the new age-rating responses become mandatory for new apps, updates, and alternative-distribution notarization beginning in September 2026.

Why it matters
The deadline is known and the review depends on shipped product behavior, so the work belongs in release preparation rather than the final submission hour.
Who should care
Apple-platform teams with any user-generated or socially distributed content.
Suggested action
List the relevant features, capture the responsible owner and under-13 behavior, and save the completed answers with the release evidence this week.
Primary sourceApple DeveloperPublished Jul 9, 2026

Every published edition

Weekly brief archive

New every Monday · permanent issue links

  1. Edition 3Week of Jul 13–Jul 19, 2026

    Compliance and conversion start before session two

    The highest-leverage work this week sits in release readiness and the first value moment, not in another feature sprint.

    Viewing
  2. Edition 2Week of Jun 15–Jun 21, 2026

    Distribution is becoming market specific

    Billing, distribution, and verification can no longer be managed as one universal store configuration.

  3. Edition 1Week of May 18–May 24, 2026

    Discovery is becoming conversational

    Store discovery is moving beyond exact keyword matching, but clear customer language still supplies the evidence those systems need.