third-party app

AppWizard
January 27, 2026
Many new vehicles are opting to forgo Android Auto while still providing essential features through Android Automotive OS, also known as Google Built-In, which is integrated into the vehicle and does not require a smartphone connection. This proprietary software may require additional subscriptions. Samsung DeX allows users with newer Samsung devices to connect to an external monitor or TV, creating a desktop-like experience in the car using AutoPro X, which connects wirelessly to the car's infotainment system. This setup enables access to streaming services when parked but emphasizes driver focus on the road. For vehicles lacking Android Auto support, users can mount their Android phone or tablet on the dashboard for navigation, calls, and music, while third-party applications can enhance the experience. Automakers may discontinue Android Auto to optimize data usage and restrict third-party app installations. Drivers can use their car's built-in browser to access features like phone mirroring or web-based versions of apps, such as Waze, as alternatives to Android Auto.
BetaBeacon
January 26, 2026
- Epic Games and Google have entered into a six-year, 0 million partnership involving joint product development, marketing, and technical collaboration. - The partnership includes closer integration of Unreal Engine, which powers Fortnite and many third-party games. - The judge raised concerns about how the partnership might affect Epic's legal demands in the antitrust lawsuit against Google. - Google has proposed changes to Android monetization, including new fee structures for in-app billing and web payments. - The outcome of the case could shape how monetization works across mobile platforms for years to come.
AppWizard
January 5, 2026
The Google Play Store has introduced several enhancements to improve the app installation and update experience for users. Key features include: 1. Per-app auto-update control: Users can now enable or disable auto-updates for individual apps, allowing essential apps to remain on stable versions while less critical ones update automatically. 2. Built-in download manager shortcut: A new circular icon on the Apps and Games pages provides access to a list of recently installed or updated apps, showing timestamps and allowing users to launch apps directly from this list. 3. Auto-open when ready: A toggle that, when activated, launches an app automatically after installation, accompanied by a notification with a countdown timer for user intervention. 4. Viewing changelogs without opening app pages: Users can now view update changelogs directly from the app management screen without navigating to each app's store listing, enhancing efficiency in reviewing updates. These features collectively enhance user control and transparency in app management.
AppWizard
December 22, 2025
Android Auto allows users to access hidden developer settings that enhance their driving experience by enabling third-party applications. Approximately 27.6% of nearly 5,000 surveyed users utilize these developer settings, with nearly 40% unaware of their existence. About 22.6% expressed interest in unlocking these settings, while just over 11% felt they had no need for them. The developer settings include options like disabling Wireless Android Auto and enabling support for apps from Unknown Sources. A separate poll showed that nearly half of 1,700 respondents use third-party apps for video playback, with notable apps like Fermata Auto and CarStream. Additionally, 50% of 3,459 respondents want official video playback support when parked, and 40% desire it for passengers while driving. Only 2% believe Android Auto should focus on other areas, and 7% wouldn’t use video playback at all.
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 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
December 10, 2025
The upcoming Android 17 update is expected to introduce a native App Lock feature, addressing the lack of built-in app locking solutions for Pixel users. Currently, Android's Private Space feature is cumbersome and not user-friendly, leading many to rely on third-party app lockers, which pose security risks. The new App Lock feature, hinted at in the recent Android Canary build, will include an App Lock API requiring specific permissions and will be accessible to all launchers. It aims to provide a more secure and reliable option for locking apps, potentially utilizing the Biometric Prompt API for authentication. However, the feature is not yet active and is unlikely to be released with the upcoming Android 16 quarterly update, with the earliest expectation for availability being with Android 17. Additionally, it remains uncertain how notifications from locked apps will be managed regarding content visibility.
Search