Urgent.News

What's breaking now, across thousands of outlets.

Tech

What Does App Store and Play Store Review Actually Look for in 2026?

App Store and Play Store review in 2026 is no longer a visual inspection where a human taps through screens. Apple and Google now run automated binary decompilation, require privacy manifests, push apps toward runtime permission elimination, enforce strict generative AI disclosure rules, and demand annual target platform currency, all before a reviewer ever looks at your UI. Store ingestion…

App Store and Play Store review processes in 2026 no longer rely on human visual inspection. Automated systems perform binary decompilation and enforce strict compliance checks before a reviewer looks at the UI. Store ingestion engines analyze compiled code, trace SDK dependencies, inspect network endpoints, and verify privacy labels against executable symbols. Passing review requires treating platform compliance like a continuous integration test.

Teams must modernize third-party dependencies, replace legacy storage calls with system pickers, and build explicit consent flows for AI features. This proactive approach ensures reliable releases and avoids automated rejections or delays.

Apple's App Store Connect scans binaries for approved reasons for calling sensitive platform interfaces, known as required reason APIs. These cover actions like checking file timestamps, querying boot time, reading disk capacity, and accessing user defaults. Privacy manifest verification must be integrated into the CI pipeline. Failure to declare required reasons leads to rejection.

Privacy manifests specify approved justifications for sensitive calls, data categories, and tracking endpoints. Xcode aggregates these manifests across dependencies. Apple flags undeclared APIs to prevent device fingerprinting. Teams should run static binary scans on all dependencies and ensure vendors provide signed binaries with valid manifests.

Generative AI has introduced tighter data governance requirements. Both stores demand disclosure of user data shared with third-party AI platforms and affirmative consent before transmission. UIs must provide clear disclosure and permission before routing prompt text, documents, or context payloads to external models. Google enforces similar requirements on Android, including active content moderation and prevention of prohibited content.

Permission minimization is emphasized, with both platforms penalizing broad storage access. Google blocks apps from requesting READ_MEDIA_IMAGES or READ_MEDIA_VIDEO unless core to the product. Instead, use system level pickers like PHPickerViewController for media selection tasks. Apple applies similar logic, pushing teams toward system pickers and avoiding broad photo library requests.

Target API currency is a hard requirement for staying listed. Both platforms raise minimum target API levels annually, and apps falling behind are hidden from search and install on newer devices. Confirm the exact current threshold in Play Console before planning a release. Apple requires builds compiled with current Xcode releases supporting the latest iOS SDKs and verifiable cryptographic signatures on third-party frameworks.

Both stores require a clear, discoverable account deletion path. Users must be able to permanently delete their account and data within the app. Failure to provide a straightforward deletion mechanism leads to rejection. Google also requires a public web resource for account and data deletion requests.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

A short glossary for a reusable prompt

Most prompts are written once, in a chat box, for one job. A reusable one has a few extra parts, and they have names. Here they are, six terms, with one prompt from the PromptAlo community library as…

  • Backup and Restore Policy defines the prompt's context and purpose
  • Variables are bracketed fields user fills each prompt use
  • Quality checklist ensures answer meets accuracy and reliability criteria

The week everything fell apart

There was a dayslong Outlook outage. A nationwide ground stop for only the second time in 25 years. Banks seemed to suddenly stop working. Even iCloud couldn't stay up and running.

Seedance API in Python: Track the Cost of Each Usable Clip

A job can succeed and still deliver a clip you can't use. If the product changes color halfway through a shot, a second paid render may be the only practical fix.

  • Submit fixed-length test job with single input photo for cost tracking.
  • Poll job status asynchronously until terminal (succeeded, failed, cancelled, expired).
  • Record accepted outputs per asset with corresponding settled charges for cost calculation.

More from Friday 20 November →