Google Tests Third-Party App Store Support in Play Store Following Epic Games Antitrust Ruling
Google is currently testing several new features in the Play Store, including an experimental section called Play Labs, support for third-party app stores, and an expanded search bar. These changes have been identified in a recent version of the service, although most of the new capabilities remain inaccessible to regular users at this time.
The most significant development is the planned ability to install alternative app marketplaces directly from Google Play. The company had previously confirmed work on this functionality, which stems from the ongoing antitrust proceedings involving Google and Epic Games. After the settlement between the two companies was withdrawn, the 2024 court ruling once again became active, requiring greater openness to competing stores.
The new menu option for third-party stores was discovered only after direct intervention in the application code. It appears in an additional menu but currently returns an error when users attempt to open an alternative marketplace. In the same area, researchers also found Play Labs, an experimental section where users will likely be able to test upcoming store features before they reach general availability. Google already uses similar experimental sections in other products, including its main search engine.
While Play Labs and the third-party store option are not yet functional, the updated search interface is already working. Google is preparing a two-line search panel designed to accommodate longer natural-language queries, accompanied by an Ask Store prompt. Instead of entering a short app name, users will be encouraged to describe their needs in detail, after which the store will attempt to suggest suitable applications.
These experiments follow recent Play Store improvements such as enhanced search capabilities and the option to test widgets during app installation. Broader rollout of the new search panel is expected in the coming weeks. However, APK analysis only reveals features currently under development, and Google retains the option to modify, postpone, or abandon any of them before release.
The direction of these changes is notable: the main Android app store is preparing to distribute competing marketplaces to users, effectively turning competition itself into a feature that can be installed through Google Play.
Related articles
OAuth Authorization Server Built Without Storing User Profiles
The article details the evolution of an OAuth Authorization Server that deliberately avoids storing user profiles, relying instead on external identity providers for authentication. It addresses three core constraints: hundreds of dynamically created isolated APIs, a public SPA client without a BFF, and the inability of resources to query the AS on every request. The design separates concerns so the AS handles only clients, tenants, grants, audiences, scopes, keys, sessions, and token issuance while the Main API owns profiles and roles. Tokens are managed securely inside a Service Worker using a custom FedCM grant, eliminating races across tabs and reducing XSS exposure. The approach minimizes blast radius, simplifies compliance, and keeps the AS replaceable without affecting product domain logic.
Why a 202-Character License Key Uses ECDSA P-256 Instead of Ed25519 or RSA
A developer building offline license verification for a .NET desktop application evaluated Ed25519, RSA, and ECDSA P-256 before selecting the last option. The decision was driven by the requirement for zero external dependencies, keys short enough for manual entry from email, and support for key rotation without breaking existing licenses. Although Ed25519 offers faster verification and a smaller public key, it is absent from System.Security.Cryptography in both .NET 8 and .NET 10, with API approval only targeted for version 11. RSA-2048 produces signatures too long for practical use, resulting in a 571-character Base32 string that users would find cumbersome. ECDSA P-256 with SHA-256 delivers a fixed 64-byte signature that becomes a manageable 202-character key when encoded in Base32, while remaining fully available in the runtime. The article also covers performance measurements, the risks of ECDSA nonce generation, and the deliberate choice of the IEEE P1363 signature format to guarantee fixed-length output.
Pilcrow Publishes Free Comprehensive Guide on Web Authentication
Author Pilcrow has released a detailed, ad-free handbook covering authentication and authorization practices for web applications. The resource draws on personal experience and includes practical examples in JavaScript and Go. It examines password-based methods, email verification, multi-factor authentication, passwordless flows, and passkeys while highlighting associated risks and usability trade-offs. The book also provides in-depth guidance on session management, token security, expiration policies, and email address handling as account identifiers. Recommendations emphasize choosing methods that match application security requirements and user expectations. Additional context is given on OWASP resources and community support channels.
redb 3.4.0 Adds Replay Checkpoints, Shared Runtime Layer and Declarative Secrets Handling for .NET Ecosystem
redb 3.4.0 delivers operational improvements for the .NET integration platform that includes typed storage over Postgres, MSSQL and SQLite, the redb.Route engine modeled after Apache Camel, the Tsak runtime with dashboard and clustering, and redb.Identity for OIDC and OAuth 2.1. The release focuses on post-deployment resilience with replay checkpoints that capture message state at named points inside routes, allowing safe re-execution of downstream steps without duplicating side effects. A shared runtime layer moves framework assemblies into a separate Libs/shared directory so that individual DLLs can be replaced without rebuilding or redeploying the entire Tsak or Identity packages. Secrets are now declared with a [Sensitive] attribute on endpoint options, ensuring URIs containing passwords or keys are sanitized before they reach logs, metrics or health checks. Additional controls include role-based access to management APIs, persistent audit trails and cryptographic signing of dynamically loaded modules. All Pro features remain free on the entire 3.x line with no licensing server required.