Developer builds privacy-first screen time blocker with no account, server, or data collection

·1 views

A software developer frustrated by three hours of daily doomscrolling built SproutGuard, a free iOS app that blocks distracting apps and websites without requiring any user account or cloud connectivity. Existing screen time apps either mimic parental controls or collect usage data via subscriptions, neither of which suited an adult seeking self-imposed limits. SproutGuard leverages Apple's on-device Screen Time API, which uses opaque app tokens that prevent even the developer from identifying which apps a user has blocked. All data including streaks, session history, and settings is stored locally, meaning there are no network calls and nothing to leak or sell. The app includes daily streaks and usage trends to help habits stick, and is available for free on the App Store.

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)

US Citizen Faces Federal Charges After GrapheneOS Phone Auto-Wiped at Airport

A US citizen was federally charged with obstruction of justice and destruction of evidence after their GrapheneOS-powered smartphone automatically wiped itself during a Customs and Border Protection search at a US airport in early 2026. CBP agents were attempting to access the device during a secondary inspection when the phone erased all its data, which prosecutors claim was a deliberate act to obstruct a lawful search. The defense argues the wipe was an automated security feature built into GrapheneOS, not a manual action by the traveler. The case is being closely monitored by digital rights groups including the EFF and ACLU, as it raises unresolved Fourth and Fifth Amendment questions about border search authority and encrypted devices. Legal experts believe this is among the first federal cases where a US citizen has been charged specifically in connection with a GrapheneOS auto-wipe at a border checkpoint.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

DEV Community Members Share Weekly Goals: Job Hunting, Coding, and Events

DEV Community's weekly goal-setting thread, now in its 189th edition, invites developers to share what they are building, learning, and attending that week. Contributors this week focused on job searching, networking, side project content, and exploring AI tools like GitHub Copilot and Claude. Coding challenges such as CSS Battles and platform maintenance on Python Anywhere also featured among completed and planned tasks. Virtual community events, including Virtual Coffee sessions and a Python Memphis meetup, were attended or planned throughout the week. The recurring thread serves as a lightweight accountability space for developers to reflect on progress and set intentions.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Batch Compression Over RabbitMQ Cuts IIoT Payload Size by 90% in Spring Boot

Industrial IoT deployments with thousands of devices can generate hundreds of millions of small telemetry messages daily, creating significant network and storage costs. A key optimization technique involves compressing batches of messages together rather than compressing each message individually before sending over a broker like RabbitMQ. Benchmarks using standard Java gzip tools show that per-message compression actually increases payload size by around 9%, while batching 500 messages before compression reduces total size by nearly 90%. This efficiency gain occurs because compression algorithms rely on recognizing repeated patterns, which only become visible when multiple similar messages are processed together. Batch compression also proved significantly faster in testing, completing in under 1 millisecond compared to nearly 50 milliseconds for 500 individual compression operations.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

C++ Move Semantics Can Be Avoided Using Custom Memory Allocators

A technical breakdown explores the hidden performance cost of C++ move semantics, focusing on the overhead introduced by move constructors and destructors when inserting objects into containers like std::vector. When a temporary object is pushed into a vector, the compiler generates both a move constructor call and an extra destructor invocation, adding unnecessary overhead. To avoid this, the author demonstrates using a custom memory allocator that returns a raw pointer, bypassing C++ RAII and automatic stack restoration entirely. Storing a pointer instead of the full object means the vector holds only 8 bytes per entry and insertion requires just a single assembly instruction. The tradeoff is that developers must manually invoke destructors, since the compiler no longer handles memory cleanup automatically.

0 comments Read more at DEV Community