每日新聞摘要

FitGuru is an Android-first workout coach built for a strict privacy rule: camera video never leaves the device. The app uses CameraX and MediaPipe Pose to track 33 landmarks, then a joint-angle Reflex Engine counts reps and gives live form cues for 18 exercises. After the set, a Cognitive Engine sends only structured numbers to Gemini 2.5 Flash for a biomechanics debrief and recovery protocol. The system also includes Gym Shield to ignore passersby, hands-free voice commands, Room-based local history, optional Wear OS heart rate input, and voice output through ElevenLabs or Android TTS fallback.

FitGuru 是一款以隐私为前提的 Android 健身教练，核心规则是摄像头视频绝不离开设备。它通过 CameraX 和 MediaPipe Pose 获取 33 个姿态关键点，再用基于关节角度的 Reflex Engine 为 18 种动作做实时 rep 计数和动作提示。训练结束后，系统只把结构化数字发送给 Gemini 2.5 Flash，用于生成生物力学复盘和恢复建议。应用还包含 Gym Shield 以避免路人干扰、免手持语音指令、Room 本地记录，以及可选的 Wear OS 心率输入和 ElevenLabs／TTS 语音输出。

The article highlights a quiet production bug in which a card number appears in plain text inside Crashlytics because of a log line that was not treated as a security concern. It frames the problem as a logging and privacy risk for banking apps, where sensitive PII can end up in crash reports if developers do not handle log output carefully. The piece centers on the danger of treating logs as harmless operational data when they may actually expose customer information.

本文指出一个悄然发生的线上问题：某段未被视为安全风险的 log 行，导致卡号以明文出现在 Crashlytics 中。文章聚焦银行 App 的日志与隐私风险，提醒开发者如果不谨慎控制 log 输出，敏感 PII 可能进入崩溃报告。核心意思是不要把 logs 视为无害的运维信息，因为它们也可能直接泄露客户数据。

The article explains that an existing XML-based Android app does not need a full rewrite to adopt Jetpack Compose. Instead, teams can introduce Compose gradually by adding one feature at a time, packaging it as its own module, and placing it behind a single Fragment. This approach lets developers ship Compose incrementally while preserving the existing app structure and avoiding a big-bang migration.

本文说明，已有的基于 XML 的 Android App 不必整体重写，也可以引入 Jetpack Compose。推荐的方式是渐进式推进：一次添加一个功能，将其打包为独立模块，并放在单个 Fragment 之后。这样既能在保留现有应用结构的前提下逐步发布 Compose，也能避免一次性大规模迁移。

This article introduces core Kotlin class features, centered on primary constructors, init blocks, custom getters, and backing fields. It frames these topics for Kotlin Multiplatform readers, suggesting a practical guide to how classes and properties are structured and initialized across platforms. The piece appears to be part of a daily Kotlin series and focuses on mastering these language features rather than on broader platform-specific behavior.

本文介绍 Kotlin 类的核心概念，重点放在主构造函数、init 块、自定义 getter 与 backing field。内容以 Kotlin Multiplatform 为背景，指向如何在不同平台上理解和运用类与属性的初始化及封装方式。文章看起来属于 daily Kotlin 系列，主轴是熟悉这些语言特性，而不是讨论更广泛的平台差异。

The source text does not include the article itself; it only shows a redirect message inviting readers to continue on MobileByteSensei. Because no substantive body content is provided, there are no technical points, examples, or conclusions available to summarize faithfully.

这份原文并未包含文章正文，只显示了一则引导读者前往 MobileByteSensei 继续阅读的消息。由于缺少实际内容，无法可靠整理出技术要点、示例或结论；摘要只能忠实反映当前可见的信息。

The provided input contains only the article title, author, link, and a short continuation prompt, but no substantive article content. As a result, there is no basis to summarize the export engine’s behavior, implementation, limitations, or outcome beyond the title itself. The safest faithful description is that the source text is incomplete and does not include the article’s actual discussion.

输入内容只有文章标题、作者、链接，以及一行“Continue reading”提示，没有提供实际正文。因此无法忠实概括导出引擎的设计、行为、限制或结果，只能确认该来源文本并不完整，缺少足以摘要的正文信息。

The supplied content does not include the article body, only a prompt to continue reading on MobileByteSensei. As a result, there are no verifiable technical details, arguments, or implementation notes to summarize from the provided text. The title indicates a theme about a retry queue being useless without something to execute it, but that inference comes only from the title, not from the missing article content.

这次提供的内容只有“Continue reading on MobileByteSensei”的跳转提示，没有文章正文，因此无法从原文提取可验证的技术细节、论点或实现说明。标题显示主题可能在讨论：如果没有执行它的机制，重试队列就形同虚设；但这只能视为标题传达的含义，不能当作正文中的具体事实。

CinematiQ’s landscape videos were displayed sideways because its shader depended solely on the MP4 rotation hint. The article explains that this hint was only correct for portrait video, while the phone’s release path had never been exercised with landscape content. As a result, the orientation issue appeared only when landscape playback entered the real release flow.

CinematiQ 的横向视频会侧着显示，原因在于 shader 只依据 MP4 的旋转提示来处理方向。文章说明，这个提示只在竖屏情况下才正确，而手机上的 release 流程此前也从未测试过横屏内容。于是，当横向视频进入正式播放路径时，方向问题才被暴露出来。

The article’s teaser says Android has steadily reduced the ability to run background code across releases, leaving developers with a much narrower set of options. Its title points to WorkManager as a production-oriented way to schedule work that can survive Doze, device reboots, and aggressive OEM process killing. However, the provided excerpt contains only the intro teaser and does not include the article’s full technical discussion or implementation details.

这篇文章的导语指出，Android 在过去十年里持续收紧后台执行限制，使开发者可用的后台运行方式越来越少。标题则表明主题聚焦于 WorkManager，讨论如何在生产环境中调度能够抵御 Doze、设备重启以及部分 OEM 激进杀进程的工作。不过目前给出的只有开头简介，没有包含完整的技术分析或实现细节。

Android is no longer just a phone platform; the same app may now run on tablets, foldables, desktop windowing environments, and ChromeOS. This piece introduces the need for adaptive UI in a world where screen sizes and form factors vary widely. It frames Android development as increasingly multi-device, and sets up the broader discussion around building interfaces that can respond to large screens and folding devices.

Android 早已不只是手机平台，同一个应用现在也可能运行在平板、折叠设备、桌面窗口环境和 ChromeOS 上。本文从这一现实出发，说明自适应 UI 的必要性：当屏幕尺寸和设备形态差异越来越大，界面就必须能够按场景调整。文章主要是在铺垫 Android 开发正走向多设备时代，并引出面向大屏和折叠设备的设计问题。

The article explains that Kotlin companion blocks compile to static members, but moving Android code from companion objects to companion blocks is not always a drop-in change. Such a migration can affect Java callers, reflection, R8 rules, and library releases. The key takeaway is that even if the generated bytecode looks convenient, teams need to consider compatibility and tooling impacts before making the switch.

文章指出，Kotlin 的 companion blocks 会编译成 static 成员，但把 Android 代码从 companion objects 迁移到 companion blocks 并不一定能直接替换。这样的迁移可能影响 Java 调用方、反射、R8 规则以及库发布流程。核心结论是：即使生成的字节码看起来更方便，团队也应先评估兼容性和工具链影响，再决定是否切换。

This article describes how the author built Muffle’s custom geofencing engine without relying on Google Play Services. To keep the solution offline, privacy-first, and battery-conscious, it combines passive location updates, coarse proximity checks, and the Haversine formula to decide when sound settings should change. The implementation runs in a ForegroundService, uses a BroadcastReceiver for significant movement, and adds debouncing to avoid false exits caused by volatile network-based location changes. It also accounts for Android power limits by using AlarmManager with setExactAndAllowWhileIdle, while acknowledging edge cases such as signal loss in tunnels or basements. The main lesson is to treat location as noisy and failure-prone, and to design automation that works invisibly without burdening the user.

本文介绍作者如何在不依赖 Google Play Services 的情况下，为 Muffle 构建自定义地理围栏引擎。为了兼顾离线、隐私和电量，方案结合被动位置更新、粗略距离判断与 Haversine 公式，在设备进入或离开范围时切换声音状态。核心逻辑运行在 ForegroundService 中，并通过 BroadcastReceiver 监听明显移动；同时加入去抖机制，避免因网络定位波动而误判。作者还使用 AlarmManager 与 setExactAndAllowWhileIdle 对抗 Doze Mode 的限制，并指出隧道、地下室等信号消失场景仍需要更完善的缓存设计。

The article argues that double-entry bookkeeping offers a useful model for AI agent verification. In a multi-step agent workflow, each step may succeed individually while the overall system ends up inconsistent, such as when a payment succeeds but the order is never created. To prevent silent failures, each critical action should produce two opposing events, such as Reserved and Committed, so the state machine can automatically detect mismatches. This makes rollback, replay, and audit easier because the event log preserves the full transition history. The same idea is applied to StareBrain’s on-device Android agent, where an ActionConfirmed event must match an ActionDispatched event or the action remains unresolved. The core idea is that imbalance itself becomes the proof of failure.

文章认为，复式记账可以作为 AI agent 验证的设计模型。对于多步骤的 agent 动作，单个步骤可能都成功，但整体系统仍可能因“付款成功、订单未创建”之类的情况而变得不一致。为避免这种静默失败，关键动作应产生两条相互对应的事件，例如 Reserved 和 Committed，让状态机自动检查是否配对。这样就不需要额外审计器，也能借由不可变事件日志支持回放、审计与回滚。文章还以 StareBrain 的 Android 端 AI agent 为例：ActionConfirmed 必须对应 ActionDispatched，否则动作会保持在未解析状态。核心观点是，失衡本身就是失败的证据。

This piece points readers toward mastering Kotlin’s when expression and pattern matching techniques, with an emphasis on exhaustive conditional logic and smart casting. The goal is to support more robust MVI state architectures in Kotlin Multiplatform. The provided excerpt is brief and frames the topic as a practical guide for engineers working with state-driven application design, without introducing additional implementation details or claims.

本文聚焦 Kotlin 的 when 表达式与模式匹配，强调如何利用完整的条件逻辑与 smart casting，来支持更稳固的 MVI 状态架构。原文摘录虽然很短，但已经点明主题是面向 Kotlin Multiplatform 的实务方法，并未提供额外实现细节或性能结论。对于熟悉 Kotlin 生态的工程师来说，这更像是一篇围绕状态驱动设计的导读。

The article reflects on how Kotlin developers have long used companion object to organize class-level members such as constants and factory methods. Framed as a discussion of the evolution of statics, it questions whether companion objects are still the best default pattern or whether newer approaches may reduce the need for them. Based on the excerpt, the piece is about rethinking a familiar Kotlin construct rather than announcing a confirmed replacement.

这篇文章回顾了 Kotlin 开发者长期以来如何使用 companion object 来组织类级成员，例如常量和工厂方法，并以“静态概念的演进”为主题，探讨这种常见模式是否仍然合适。就当前提供的内容来看，文章重点在于重新审视 companion object 的角色与必要性，而不是确认某种新的替代方案已经正式取代它。

This article introduces a comparison between REST APIs and GraphQL, framing them as two different approaches to how applications communicate and fetch data. The piece positions the discussion around choosing a smarter way to retrieve information, but the provided excerpt does not include technical details, implementation guidance, or a conclusion. It mainly sets up the topic and invites readers to continue on Medium.

本文以 REST API 和 GraphQL 的对比为主线，说明两者如何影响应用程序之间的通信和数据获取方式。标题强调“更聪明”的数据获取方法，但当前提供的内容只有开头引言，并未包含技术细节、实现建议或结论。整体来看，这篇文章主要用于引出主题，并邀请读者前往 Medium 继续阅读。