SShortSingh.
Back to feed

Developer Builds Offline Geofencing App That Auto-Silences Phones Without Server Tracking

0
·2 views

After a loud phone interrupted a Friday prayer service, a developer created Muffle, an Android utility that adjusts sound settings automatically. Human memory often fails to switch phones to silent in places like meetings or religious services, and many existing apps collect location data on remote servers. Muffle instead uses Android's GeofencingClient API, which lets the operating system detect when a device crosses a defined boundary and notify the app. All triggering logic stays on the device, so no location history is stored on a backend. The developer also noted that Android's Doze power-management mode can make location updates inconsistent when a phone stays stationary for long periods.

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)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Measuring one website change with the Google Search Console Performance report

The article explains how to use the Search Console Performance report to track clicks, impressions, CTR and average position before and after a single website update. It stresses defining the page, filters and comparison periods in advance, and recording the exact date the change went live. A before-and-after comparison shows only an association, since seasonality, shifting search demand and other events can affect the same metrics. Missing report rows are described as an evidence gap rather than proof a page never appeared in search. The author recommends keeping a change log of any other site modifications made in the same week so they can be considered as alternative explanations.

0
ProgrammingDEV Community ·

Sled Volt uses deterministic server replays to make its leaderboard tamper-proof

Sled Volt is a free 3D downhill sled game that runs in a browser tab and can be added to a phone's home screen. Its simulation runs on a fixed 60 Hz tick using only basic arithmetic, so identical inputs produce identical runs on any device. Instead of trusting submitted scores, the game uploads the player's inputs, and the server replays the run and ranks only the score it calculates itself. The same approach powers the Daily Run, where the course is generated from the date so players share a mountain and can race friends' ghost runs. The developers also capped run length to manage the server CPU cost of replaying long runs.

0
ProgrammingDEV Community ·

Tips for finding a remote internship and avoiding common pitfalls

The article offers guidance for students seeking remote internships, which are harder to find as competition for good roles has grown. It explains that postings labeled remote can differ, ranging from fully remote to region-restricted, hybrid, or remote only for part of the term, so applicants should verify the arrangement. Recommended search strategies include filtering job boards by remote location, checking employer career pages directly, and setting alerts to apply early. The piece also advises highlighting independent projects and remote collaboration experience in applications, preparing a reliable setup for video interviews, and watching for scam signs such as requests for payment. Finally, it suggests habits like weekly manager check-ins to help remote interns stay visible and build strong references.

0
ProgrammingDEV Community ·

New Frontier AI Coding Models Aim to Improve Price-Performance for Software Teams

A public signal suggests a new generation of frontier AI models is being designed to balance cost and performance for production software engineering. The focus reportedly centers on routine work such as writing, reviewing, debugging and maintaining code rather than research demonstrations. The available material, however, does not name the models, disclose pricing, or say when teams could access them. Analysts note that such tools are most useful when output quality, speed and running cost suit everyday development workflows, especially for smaller teams. Experts advise evaluating these tools against real workplace tasks, usage costs and existing review practices before assuming a lower-cost model is suitable for production use.