Android platform

AppWizard
December 20, 2025
Google is complying with a court injunction requiring it to open its Android platform to third-party app stores and to separate its Google Play Billing system from its app store. Developers must enroll in new programs for "alternative billing" and "external content links" by January 28th, which will incur fees. Google plans to charge [openai_gpt model="gpt-4o-mini" prompt="Summarize the content and extract only the fact described in the text bellow. The summary shall NOT include a title, introduction and conclusion. Text: Google has taken steps to comply with the recent injunction issued by Judge James Donato, which mandates the company to open up its Android platform for third-party app stores and to stop tying its Google Play Billing system to its app store. As part of this compliance, Google has introduced new programs and associated fees that will affect app developers. In a subtle update to its support pages, Google has set a deadline of January 28th for developers to enroll in specific programs designed for “alternative billing” and “external content links.” These programs will not be fee-free; developers can expect to incur substantial alternative fees unless Judge Donato opts for a proposed settlement between Epic and Google. Although Google has not yet begun collecting these fees, it has outlined a structure where developers will be charged .85 for every app and .65 for every game installed within 24 hours of a user clicking a link that leads outside of Google’s app store. Additionally, Google will take a 20% cut of any in-app purchases and 10% from auto-renewing subscriptions. Developers will still need to submit their apps for review, utilize a Google API for tracking, and report all transactions, including free trials, to participate in these new programs. For those developers wishing to implement their own billing solutions, the financial incentive may be minimal. Google has indicated that they will offer only a 5% discount compared to their existing fees, which might render the effort to pursue alternative billing unappealing. Specifically, Google will charge 25% for in-app purchases and 10% for auto-renewing subscriptions, requiring developers to integrate a Google API for tracking and to report transactions within a 24-hour window. To ease the burden on smaller developers, Google has introduced a cap on some of these fees, limiting them to 10% of a developer’s first million in earnings. However, this is only a slight improvement over the existing cap of 15%, which raises questions about its effectiveness in truly alleviating financial pressures for smaller entities. The upcoming response from Judge Donato remains uncertain. In a parallel case involving Apple, Judge Yvonne Gonzalez Rogers found Apple in contempt of court for imposing a 27% fee on external payments. An appeals court supported this decision but suggested that Apple could charge a commission based on reasonable costs associated with coordinating external links for purchases. Google asserts that the fees tied to its external content links program reflect the value provided by the Android ecosystem and support ongoing investments in both Android and Play. However, the company has clarified that it will not be collecting any fees at this moment, stating, “In the future, Google intends to apply a service fee on successful transactions and downloads completed via external content links.” Currently, developers in this program are not required to report transactions or downloads to Google. In a joint progress report, Epic and Google’s legal teams acknowledged the January 28th deadline and other stipulations, but Epic has expressed its opposition to the service fees that Google plans to implement, indicating a readiness to challenge these fees if they come into effect. The fate of these developments may hinge on whether Judge Donato accepts the proposed settlement between Google and Epic, which would establish a broader application of the rules worldwide and potentially lower transaction fees. As the situation evolves, Google’s support pages continue to change, reflecting the dynamic nature of the ongoing Epic v. Google case. An evidentiary hearing is scheduled for January 22nd, where further clarity may emerge regarding the future landscape of app billing and developer fees." max_tokens="3500" temperature="0.3" top_p="1.0" best_of="1" presence_penalty="0.1" frequency_penalty="frequency_penalty"].85 for every app and [openai_gpt model="gpt-4o-mini" prompt="Summarize the content and extract only the fact described in the text bellow. The summary shall NOT include a title, introduction and conclusion. Text: Google has taken steps to comply with the recent injunction issued by Judge James Donato, which mandates the company to open up its Android platform for third-party app stores and to stop tying its Google Play Billing system to its app store. As part of this compliance, Google has introduced new programs and associated fees that will affect app developers. In a subtle update to its support pages, Google has set a deadline of January 28th for developers to enroll in specific programs designed for “alternative billing” and “external content links.” These programs will not be fee-free; developers can expect to incur substantial alternative fees unless Judge Donato opts for a proposed settlement between Epic and Google. Although Google has not yet begun collecting these fees, it has outlined a structure where developers will be charged .85 for every app and .65 for every game installed within 24 hours of a user clicking a link that leads outside of Google’s app store. Additionally, Google will take a 20% cut of any in-app purchases and 10% from auto-renewing subscriptions. Developers will still need to submit their apps for review, utilize a Google API for tracking, and report all transactions, including free trials, to participate in these new programs. For those developers wishing to implement their own billing solutions, the financial incentive may be minimal. Google has indicated that they will offer only a 5% discount compared to their existing fees, which might render the effort to pursue alternative billing unappealing. Specifically, Google will charge 25% for in-app purchases and 10% for auto-renewing subscriptions, requiring developers to integrate a Google API for tracking and to report transactions within a 24-hour window. To ease the burden on smaller developers, Google has introduced a cap on some of these fees, limiting them to 10% of a developer’s first million in earnings. However, this is only a slight improvement over the existing cap of 15%, which raises questions about its effectiveness in truly alleviating financial pressures for smaller entities. The upcoming response from Judge Donato remains uncertain. In a parallel case involving Apple, Judge Yvonne Gonzalez Rogers found Apple in contempt of court for imposing a 27% fee on external payments. An appeals court supported this decision but suggested that Apple could charge a commission based on reasonable costs associated with coordinating external links for purchases. Google asserts that the fees tied to its external content links program reflect the value provided by the Android ecosystem and support ongoing investments in both Android and Play. However, the company has clarified that it will not be collecting any fees at this moment, stating, “In the future, Google intends to apply a service fee on successful transactions and downloads completed via external content links.” Currently, developers in this program are not required to report transactions or downloads to Google. In a joint progress report, Epic and Google’s legal teams acknowledged the January 28th deadline and other stipulations, but Epic has expressed its opposition to the service fees that Google plans to implement, indicating a readiness to challenge these fees if they come into effect. The fate of these developments may hinge on whether Judge Donato accepts the proposed settlement between Google and Epic, which would establish a broader application of the rules worldwide and potentially lower transaction fees. As the situation evolves, Google’s support pages continue to change, reflecting the dynamic nature of the ongoing Epic v. Google case. An evidentiary hearing is scheduled for January 22nd, where further clarity may emerge regarding the future landscape of app billing and developer fees." max_tokens="3500" temperature="0.3" top_p="1.0" best_of="1" presence_penalty="0.1" frequency_penalty="frequency_penalty"].65 for every game installed within 24 hours of an external link click, along with a 20% cut of in-app purchases and 10% from auto-renewing subscriptions. Developers must submit apps for review, use a Google API for tracking, and report transactions to participate. A 5% discount on fees for implementing alternative billing solutions is offered, but the overall financial incentive may be minimal. Google has capped some fees at 10% of a developer's first million in earnings, slightly improved from a previous cap of 15%. Currently, Google is not collecting fees but intends to apply them in the future. Epic has opposed the service fees and is prepared to challenge them. An evidentiary hearing is scheduled for January 22nd.
AppWizard
December 15, 2025
Android is introducing a feature called Expressive Calling in the Phone by Google app, allowing users to specify the reason for their calls, including marking them as urgent. This feature is currently available to select beta testers. When a call is marked as urgent, the recipient receives a notification that reads “It’s urgent!” along with an animated siren emoji, and the urgent designation remains in the call log if the call is missed. This feature aims to improve the calling experience by providing context and is particularly useful for users with Do Not Disturb mode activated. However, both the caller and recipient must be using the Phone app beta for the feature to work, limiting its current availability.
AppWizard
December 11, 2025
Android 17 introduces a system app locking feature, enhancing mobile security with a new permission structure called LOCK_APPS, allowing only system apps and designated launchers to execute this functionality. This feature utilizes the Biometric Prompt API for user authentication via fingerprint, facial recognition, or PIN. Users can lock or unlock apps by long-pressing the app icon on the launcher, which sends a SETAPPLOCK request to Android's core security service. The app lock will only be available on handheld devices, excluding Android Automotive, Wear OS, and Android TV. The feature is expected to debut later in the rollout of Android 17, benefiting Xiaomi devices and HyperOS.
AppWizard
November 26, 2025
Google is considering a new initiative called Aluminium, which aims to adapt Android's features for laptops and desktops, focusing on ARM architecture and improving multitasking, keyboard-and-mouse input, and file management. Android has over 3 billion active devices globally, while ChromeOS has a low market share in the PC sector. Android has evolved with updates like Android 12L, enhancing usability on large screens, and real-world implementations like Samsung DeX show its potential as a desktop OS. However, challenges remain regarding app usability on larger displays, and improvements in performance, security, and enterprise readiness are needed. Google plans to develop a refined Desktop Mode, implement UX guidelines, establish a native Linux workspace, enhance file access, integrate audio features, and collaborate with OEMs for compatible hardware.
AppWizard
November 16, 2025
Google has launched a "Developer Verification" initiative requiring developers to verify their identities when distributing applications outside the Google Play Store. This program aims to enhance user safety while allowing advanced users to install unverified apps. The early access phase has begun, with invitations for Play Store developers starting November 25, 2025. Simplified verification pathways will be available for students and hobbyists. Advanced users can still sideload apps but will receive explicit warnings about potential risks. The initiative seeks to reduce the distribution of malware by increasing the complexity and cost for malicious developers, while maintaining user choice for technically skilled individuals.
BetaBeacon
November 14, 2025
Valve has announced the Steam Frame, a new VR headset that aims to allow users to play as many VR and non-VR games as possible. The headset runs Steam games from its own onboard storage and uses controllers with a more conventional layout. The Frame's ARM-based Snapdragon chip poses challenges and opportunities for compatibility with Android VR games. Valve is working on platform crossover plans to allow Android VR titles on Steam, using an x86-to-ARM emulator called FEX. The Frame will be able to run PC games as well as Android VR games due to its SteamOS platform. Valve is focusing on providing a seamless gaming experience for customers without them having to worry about technical details. The Frame will also support mixed reality with the right third-party hardware additions.
AppWizard
November 13, 2025
Google has initiated a rollout of a new safety feature for developers distributing apps outside the Play Store, requiring them to verify their identities for sideloading capabilities. Currently, select developers are invited to participate in the early access phase through the Android Developer Console. Experienced users will still have the option to sideload unverified apps, and Google is developing an “advanced flow” to allow these users to accept the risks associated with installing unverified software. The company is soliciting feedback to refine the process and emphasizes user awareness with clear warnings about potential risks. Google aims to complicate malware distribution by requiring verified identities from developers. Widespread implementation of this verification requirement is not expected until late 2026.
Search