每日新聞摘要

This article recounts implementing Firebase Google Login across Android, iOS, JVM (desktop), and web within a Kotlin Multiplatform project. Because Firebase lacks official KMP support, the author uses the community GitLive SDK; however, GitLive’s JVM Auth implementation is minimal, so the JVM path requires obtaining a Google ID token via OAuth 2.0 and exchanging it with Firebase’s REST API, then injecting the resulting session into GitLive’s internal storage. For Android and iOS the flow obtains a Google ID token via platform SDKs (Credential Manager on Android, Swift Google SDK on iOS) and authenticates with Firebase through GitLive’s signInWithCredential; JS leverages signInWithPopup from the Firebase Web SDK. To keep shared code clean, the author abstracts platform-specific token acquisition with a GoogleAuthenticator interface and warns that JVM workarounds rely on internal SDK behavior and may break with updates.

本文介绍了在 Kotlin Multiplatform 项目中实现跨平台 Firebase Google 登录的实践。由于 Firebase 尚未正式支持 KMP，作者选用社区维护的 GitLive SDK，但其在 JVM 平台的 Auth 支持有限，因此 JVM 路径需通过 OAuth 2.0 获取 Google ID Token，再调用 Firebase REST API 或将生成的会话数据手动注入到 GitLive 的内部存储中以完成认证。Android 使用 Credential Manager API 获取 idToken，iOS 使用 Swift Google SDK，Web 则直接借助 Firebase Web SDK 的 signInWithPopup。作者通过 GoogleAuthenticator 接口统一抽象各平台的授权细节，同时警示 JVM 的手动注入依赖于 SDK 内部实现，可能在未来更新时失效。

Kotlin Weekly #495 (25 January 2026) aggregates recent Kotlin ecosystem news: nominations opened for the Golden Kodee Community Awards; Ktor 3.4.0 was released with OpenAPI generation, structured-concurrency HTTP lifecycle integrations, duplex OkHttp streaming, and other improvements; Exposed 1.0 delivers a stable API, R2DBC support, better Spring integration and performance optimizations. JetBrains also invites Android developers to take a survey. The issue links several technical articles—on Koin dependency injection with interfaces and qualifiers, a practical guide to Kotlin generics (in/out/reified), coroutines cancellation and exception handling, and a fourth installment on building Kotlin AI agents with delegation and sub-agents. Featured are an Android Compose CameraX QR scanner tutorial, conference videos about compiler plugins and Kotlin 2.3, sponsored Compose learning resources and RevenueCat paywall tools, plus new libraries like KMP Wizard Template, KRelay, ksrc, Variist, and TechDebt. The newsletter closes with contribution and sponsorship invitations and thanks JetBrains for support.

Kotlin Weekly 第495期（2026年1月25日）汇总近期 Kotlin 生态要闻：Golden Kodee 社区奖开始接受提名；Ktor 3.4.0 发布，带来 OpenAPI 生成、压缩插件 Ztsd 支持、OkHttp 双工流以及将 HTTP 请求生命周期与结构化并发整合等特性；Exposed 1.0 提供稳定 API、期待已久的 R2DBC 支持、改进的 Spring 集成及性能提升。JetBrains 也发起面向 Android 开发者的调查。期内推荐若干技术文章，涵盖 Koin 依赖注入（介面与限定符）、Kotlin 泛型（in/out/reified）、协程取消与异常处理，以及构建 Kotlin AI 代理的分工与子代理等；并列出 Compose 教程、CameraX QR 扫描实现、会议视频、赞助学习资源与多个新开源库（如 KMP Wizard Template、KRelay、ksrc、Variist、TechDebt），同时邀请投稿与感谢 JetBrains 支持。

This article examines a common misconception about Android Activities: that an Activity is simply "a screen." While an Activity often appears as a visible UI, the author argues this is an oversimplification. An Activity is an application component that not only displays UI but also coordinates user interaction, handles lifecycle events, and communicates with the system and other components. Treating it only as a visual layer can lead to poor architecture and misplaced logic. By clarifying the Activity's roles and responsibilities, the piece helps developers decide what code belongs in an Activity versus other components, promoting clearer separation of concerns and more maintainable Android apps.

本文讨论了关于 Android Activity 的常见误解：许多人把 Activity 简单称作“一个界面”，因为它呈现给用户的就是一个画面，但作者认为这种理解过于片面。Activity 不仅负责显示 UI，还要协调用户交互、处理生命周期事件，并与系统及其他组件通信。仅把它看作视觉层可能导致设计不良与逻辑错位。通过澄清 Activity 的职责，文章旨在帮助开发者把相关逻辑放在合适的位置，从而改善应用架构与可维护性。

The article reviews five years of enthusiasm around GraalVM and native compilation and argues that the technology ultimately failed to restore Java's momentum. While GraalVM promised faster startup, smaller footprints, and standalone native binaries, the author contends adoption ran into engineering complexity, compatibility gaps, and insufficient ecosystem shift. By 2026 the piece asserts that Rust, Go, and Kotlin have already occupied many of the areas Java hoped to reclaim—systems programming, cloud-native services, and more modern developer ergonomics—so GraalVM remains an incremental option rather than a platform-saving breakthrough. The retrospective frames native compilation as a useful tool but not a cure for broader market and ecosystem trends that favored newer languages.

本文回顾过去五年社区对 GraalVM 与原生编译的期待，并主张该技术未能拯救 Java。作者认为，尽管 GraalVM 在启动速度、二进制体积与独立部署上有吸引力，但在实践中遭遇工程复杂性、兼容性差距与生态迁移不足等问题。到 2026 年，文章指出 Rust、Go 与 Kotlin 已占据许多 Java 希望重夺的领域，包括系统编程、云原生服务与更现代的开发体验，使 GraalVM 更像是一个增量选项而非改变局势的突破。结论提醒读者将原生编译视为众多工具之一，而非扭转语言流行趋势的灵丹妙药。

This article explains how combining Kotlin's sealed classes and when expressions enables compile-time-safe state management. Sealed classes restrict subclassing to the same file or module, making them suitable for modeling distinct state variants, while when expressions over a sealed type can be exhaustive so the compiler enforces that every state branch is handled. Together they let you represent state machines or UI states with explicit variants and catch missing branches at compile time, reducing runtime errors and improving maintainability. The piece emphasizes modeling states as sealed hierarchies, using exhaustive when checks (and avoiding else unless needed), and highlights benefits such as clearer intent, safer refactoring, and earlier detection of unhandled cases for Kotlin developers.

本文说明如何在 Kotlin 中结合 sealed class 与 when 表达式实现编译时安全的状态管理。sealed class 限制子类只能在同一文件或模块定义，适合建模具体的状态变体；对封闭类型使用 when 可以强制穷尽性检查，让编译器确认每种状态都有对应处理。二者配合可用于状态机或 UI 状态的明确建模，减少运行时错误并提升可维护性。文章强调以封闭层级表达状态、利用 when 的穷尽性避免遗漏分支，以及该模式对重构和早期检测未处理情况的好处。

The article explains how to take an existing Android MVVM application and progressively convert it into a Kotlin Multiplatform (KMP) app so it can run on iOS. It advocates a gradual migration approach intended to maximize reuse of business logic and data layers while keeping platform-specific UIs native. The write-up highlights the value of KMP for reducing duplicated code between Android and iOS and outlines a stepwise, low-risk path for adapting an MVVM architecture across platforms. Aimed at Android developers exploring cross-platform reuse, the piece provides a conceptual roadmap for integrating shared modules alongside native interfaces and emphasizes incremental changes that preserve existing functionality during the migration.

本文示范如何将既有的 Android MVVM 应用逐步转换为 Kotlin Multiplatform（KMP）应用以在 iOS 上运行。文章采取渐进式迁移策略，复用共享的业务逻辑和数据层，同时保留平台特定的 UI。目标是减少 Android 与 iOS 之间的重复代码，并说明在保持 MVVM 架构下迁移时的实践考量与步骤。对于有兴趣通过 KMP 共享核心功能、降低维护成本的 Android 开发者，本文提供了一个概念性路径，强调通过分阶段整合共享模块与原生界面来降低风险。

The supplied excerpt for "Queue — Deque (Double Ended Queue)" by Yogendra on Medium includes only the title line and a brief prompt directing readers to "continue reading on Medium." No substantive body content or technical exposition is present in the provided text. Accordingly, this summary is limited to noting the article's topic—queues and double-ended queues—and that the complete content must be accessed via the Medium link. Any definitions, operational details, examples, implementations, or use cases that the full article may contain are not available in the excerpt; readers interested in the full explanation should follow the original Medium link to read the author's complete post.

所提供的摘录来自 Yogendra 在 Medium 发布的《队列 — Deque（双端队列）》，内容仅有标题和一句提示“继续在 Medium 阅读”，并未包含正文或技术内容。因此，本摘要仅能说明该篇文章的主题为队列与双端队列，完整内容需通过原文链接在 Medium 上查看。摘录未提供定义、操作说明、示例或实现细节等信息，想获取完整讲解请访问原始文章页面。

This piece, titled "Elevating Android Engineering: A Modern Treatise on Test-Driven Development with Kotlin," introduces a discussion about a paradigm shift in mobile reliability. It signals an emphasis on test-driven development (TDD) applied to Android projects using Kotlin and frames these practices as part of modern engineering approaches to raise the quality and reliability of mobile applications. As an introductory note, the article highlights the importance of adopting disciplined testing and contemporary tooling to improve engineering outcomes. The entry serves as an invitation to read further on Medium for a deeper exploration of how TDD and Kotlin can influence Android development workflows and team practices.

本文题为《提升 Android 工程：关于用 Kotlin 实现测试驱动开发的现代论述》，导言提到移动可靠性正经历一场范式转变。文章聚焦于在 Android 开发中应用测试驱动开发（TDD）与 Kotlin，主张通过规范化测试与现代工程实践来提升移动应用的质量与稳定性。作为简介，文本强调采用 TDD 与现代工具链能够改善开发流程和团队表现，并引导读者到 Medium 查看更深入的讨论与实现细节。

This article introduces Koin as a lightweight dependency-injection (DI) solution that Android developers should know about. It opens by recognizing that many Android developers have struggled with DI frameworks, noting that Dagger — while powerful — can be complex to work with. The piece positions Koin as an alternative worth considering, emphasizing its lighter, more pragmatic approach to DI for app development. Rather than providing exhaustive technical detail in the excerpt, the article aims to make the case that developers who found traditional DI tooling heavy or cumbersome should at least evaluate Koin as a simpler option for managing dependencies in Android projects.

文章把 Koin 推荐为一种轻量级的依赖注入（DI）方案，值得 Android 开发者关注。文中首先承认许多开发者在处理 DI 框架时遇到困难，并指出 Dagger 虽然功能强大，但可能过于复杂。基于这种背景，作者提出 Koin 是一个更精简、务实的替代选择，建议对于觉得传统 DI 工具过于繁重或难以上手的开发者，可以考虑评估 Koin 是否更适合其项目需求。