Android Developer Drops Google Play Over Call Log Permission Restrictions

·4 views

An Android developer behind the long-running app TKWeek was forced to remove missed-call functionality from Google Play builds in 2021 after Google enforced strict policies on the READ_CALL_LOG permission, restricting its use to default phone, SMS, or assistant handler apps. While Android's own platform allows users to grant or deny sensitive permissions at runtime, Google Play adds a separate policy layer that prohibits certain features regardless of user consent. The developer chose to leave the Play Store rather than permanently strip the feature, later restoring it through alternative distribution channels F-Droid and Obtainium. Google has since extended similar restrictions further, announcing in April 2026 a dedicated Contacts Permission policy for apps targeting Android 17 and above. The case raises broader questions about whether app store policies should be able to override legitimate features that users are otherwise free to permit on their own devices.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Developer Surveys Best News APIs for Building a Football Live Score Site in 2026

A software developer has published the first part of a multi-part guide evaluating public APIs suitable for building a football live score site in 2026. The series draws exclusively from the public-apis GitHub repository, which has over 400,000 stars, to maintain a consistent and transparent selection process. For this opening installment, the author screened all 23 entries in the repository's News section, shortlisting seven APIs that could realistically supply football-related news content. Key criteria included keyword search, language filters, publication freshness, pagination reliability, and whether free-tier licenses permit production use. Among the candidates reviewed, Currents API emerged as a strong contender due to its 250 daily free requests, no artificial content delay, and permissible terms for displaying headlines and links.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Why portable Linux handhelds like the uConsole are security risks on untrusted networks

The Clockwork uConsole is a handheld Linux computer built around a Raspberry Pi Compute Module 4, designed for on-the-go development. A security audit using the RoamSwitch suite scored the device 90 out of 100, but deeper inspection revealed significant structural vulnerabilities common to edge hardware. The Raspberry Pi's proprietary bootloader means UEFI Secure Boot is unavailable, and most single-board computers lack full-disk encryption on their microSD or eMMC storage, leaving them physically unprotected. When developers run local servers or dashboards on such devices, many frameworks bind to all network interfaces by default, exposing open ports to anyone on the same subnet. This means connecting a portable Linux terminal to a public hotspot or shared network can make its development services instantly discoverable and accessible to other users on that network.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How to Build a Jumia Product Performance Dashboard in Excel

A data analyst walkthrough published on DEV Community demonstrates how to build a product performance dashboard for Jumia using Microsoft Excel. The project involves analyzing customer engagement, pricing models, and promotional effectiveness to uncover factors driving product success. Before analysis, the dataset underwent thorough cleaning to fix issues such as misspelled headers, duplicate records, negative review values, and improper data types. Excel functions including TRIM, CLEAN, and PROPER were used to standardize and correct the raw data. The cleaned dataset was then structured as a formatted table in preparation for deeper analysis and dashboard creation.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Why Financial Systems Need Independent Proof Layers, Not Self-Auditing Tools

Modern financial infrastructure has developed a critical flaw: institutions rely on self-attestation and internal audit logs to verify transactions they themselves execute. A veteran fintech architect argues that no single bank or automated system can serve as a neutral verifier across multi-bank or multi-processor ledgers, since each participant holds only a self-serving record of events. This problem is compounded by the rise of AI-driven payment pipelines, where automated systems are increasingly asked to verify their own outputs — a practice regulators and audit committees explicitly reject. When an automated process contains an error, a self-check built on the same logic will reproduce the same blind spot. The proposed remedy is a strict architectural separation: deterministic reconciliation engines governed by fixed business logic must establish transactional truth independently of the AI agents or payment rails that initiated the transactions.

0 comments Read more at DEV Community