Urgent.News

What's breaking now, across thousands of outlets.

Tech

How I ship a private Android app through Google Play to testers' phones

Some apps have no business being searchable. A tool built for one company, a client demo, a closed beta you want a dozen people to poke at — none of these belong in public Play search. Google still lets you ship them through Play; the listing just stays invisible to everyone who wasn't invited. Here's the loop I follow: create the app record, finish every declaration, push an AAB to the internal…

Developing a private Android application for internal testing can be achieved through Google Play without the application appearing in public search results. This method involves creating an app record on the Google Play Console and uploading an AAB (Android App Bundle) file to the internal testing track. To access the app, testers are provided with an opt-in URL that grants them permission to download the app, with the Store verifying the tester's account and test eligibility before displaying the download button.

The process requires a Google account enrolled in the Play Console developer program, with identity and payment verification, as well as a release build signed with a personal upload key. The package name should remain consistent, and Play App Signing must be enabled. The tester's Gmail addresses, along with privacy policy and data safety forms, must be provided. A minimum of one tester account should be available for a smoke test before distributing the app to the team.

The internal testing process is straightforward, taking approximately 30 minutes for initial setup and only five minutes for each subsequent release. The app record is created in the Play Console, followed by completing the app content, including privacy policy, data safety, ads, content rating questionnaire, and target audience.

The store listing must be filled out with the app name, descriptions, icon, feature graphic, and screenshots. The internal release is then created, and the release status is set to Available to internal testers within a few minutes, as it bypasses the full review queue.

To build the tester list, create an email list in the Testers tab, paste Gmail addresses, and generate the opt-in link. Testers are then invited to download the app by signing in to the provided accounts. Installing the app without the Play Store involves building an APK and pushing it over USB using the adb command-line tool, bypassing the Play Store altogether. Common issues include opt-in link failures, signing errors during upload, and ensuring the tester is signed into the correct Gmail account.

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

Also reported by 1 other outlet

Read the original at dev.to →

More in Tech

RAG Pipeline Utils v3.8: Testing RAG Answers in TypeScript

v3.8.0 is about testing RAG in TypeScript. The answer matchers now compile with types, and a new guide walks through the whole setup with Vitest, from a unit test to a test set that fails CI when…

  • RAG Pipeline Utils 3.8 introduces TypeScript support for testing RAG answers.
  • New matchers toBeGroundedIn, toCite, and toContainNoPII enable early error detection.
  • Guide provides step-by-step setup using Vitest for unit, answer, and evaluation tests.

The hardest websites to scrape in 2026: what the benchmarks show

Disclosure: I'm a co-founder of ScrapeUnblocker, one of the APIs measured below. Every number here has a public source you can check. A lot of websites are still simple to scrape.

  • Shein, G2, and Hyatt identified as hardest websites to scrape in 2026
  • Success rates of 21.88%, 36.63%, and 43.75% for these sites
  • Established scraping API providers face challenges with protected targets

Testing Broken Access Control Without Guessing

Broken access control has been at or near the top of the OWASP Top 10 for a decade, and it is still the category most automated tools handle worst.

  • Create two accounts, A and B, each owning one object
  • Record stable fingerprint of B's object with B's token
  • Compare fingerprint against response to validate test

How to Keep Product Information in Sync Across a Multilingual Website

1. Sync Is Not “Translating Once” — It Is Managing Three Different Kinds of Drift After turning a website into a multilingual version, the most common complaints are “the specs on the English page are…

  • Single source of truth maintains main language product info
  • Automatic sync ideal for marketing copy, manual sync for structured fields
  • AI website builders vary sync methods, require human oversight

More from Friday 6 November →