{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreia3mfloub5x4wdexvpis73bzrvtnyqzd4rqaplmsc4rlzhswvmrua",
    "uri": "at://did:plc:dmpmpvgbtnjd7pz4pxvvcwle/app.bsky.feed.post/3mhiqfsrlabt2"
  },
  "path": "/2026/03/20/certified-android-devices-wont-let-user-sideload-apk-app-files-anymore-or-at-least-it-wont-be-straightforward/",
  "publishedAt": "2026-03-20T11:01:45.000Z",
  "site": "https://www.cnx-software.com",
  "tags": [
    "Android",
    "security",
    "Certified Android devices won’t let user sideload APK app files anymore, or at least it won’t be straightforward",
    "CNX Software - Embedded Systems News"
  ],
  "textContent": "Google won’t allow people to (easily) sideload apps through APK files on certified Android devices starting in September 2026. It will still be possible, but either require “developer verification” and an “advanced flow” for power users. I was recently made aware of the issue after a BravePipe (previously BraveNewPipe) update, where I was greeted by a pop-up entitled “Keep Android Open” and linking to a website for more details. The “Keep Android Open” website explains that the following will be required to install and update an app (APK) on a certified device: Paying a fee to Google Agreeing to Google’s Terms and Conditions Providing government identification Uploading evidence of the developer’s private signing key Listing all current and future application identifiers This afternoon, I saw an X post about the topic providing more details, and appearing to follow a new post on the Android Developers Blog entitled “Android developer verification: [...]\n\nThe post Certified Android devices won’t let user sideload APK app files anymore, or at least it won’t be straightforward appeared first on CNX Software - Embedded Systems News.",
  "title": "Certified Android devices won’t let user sideload APK app files anymore, or at least it won’t be straightforward"
}