Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

Firebase UI Android v10.0.0-beta01 Release

未關閉
#2,285 6 則留言 1 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 2 天內回覆

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
15/100
Issue 類型
文件
描述清晰度
需要釐清
活躍度
停滯
技術堆疊
android, firebase, kotlin

研究方向

公告指向 version-10.0.0-beta01 分支、auth/README.md 和 docs/upgrade-to-10.0.md。先檢視這些已發布的材料;若要視為完成,需要有具體的文件或 release 後續工作,但此 issue 未指定具體內容。

由索引模型根據 Issue 內容生成。

描述

keep open

Firebase UI Android v10.0.0-beta01 Release

We're excited to announce Firebase UI Android v10.0.0-beta01. This major update upgrades this library to natively support Jetpack Compose.

What's New in Beta

This development phase focused on 3 key areas of the Auth module:

  • Compose Upgrade: Removing legacy XML-based components in favor of modern Kotlin-based Composable components.
  • API Redesign: A complete redesign to better support developers and improve maintenance.
  • Feature Development: Build and improve upon a suite of features to provide a complete set of authentication flows, including MFA, custom providers and multi-app support.

Note: There are no major changes to the other Firebase UI Android modules (database, firestore and storage).

Improved Core API

The new API comes packed with a host of new supporting features and utilities for managing authentication in your applications. New features include:

  • FirebaseAuthScreen: A single entry point that manages the entire auth flow based on your configuration i.e AuthUIConfiguration.

  • AuthUIConfiguration: A type-safe configuration object that defines providers, UI theming, MFA, anonymous upgrade, and validation rules for the authentication flow.

  • Custom auth injection: For adding custom authentication via create(app, auth).

Native Compose UI & Theming
  • Fully Themed: With AuthUITheme, buttons and inputs automatically adopt your app’s Material branding. You can override typography, shapes, and colors, or inject your own ProviderStyle for distinct button looks.

  • Slot APIs: The new EmailAuthScreen and PhoneAuthScreen expose slot APIs, giving you access to state (EmailAuthContentState) while letting you render your own UI.

State Management
  • State Management: Access multiple supporting functions for managing authentication state is your application. Included in this release are isSignedIn(), getCurrentUser(), and authStateFlow to expose authentication state reactively.

  • Reactive Streams: Built on Kotlin Flow for improved integration with Compose and modern Android architecture.

  • Lifecycle Management: Controller returned by createAuthFlow(configuration) with start(), cancel(), and dispose() methods.

  • Flow Control: start() drives authentication flow per configuration.

  • Safe Cancellation: cancel() transitions to Cancelled state gracefully.

  • Resource Management: dispose() releases coroutines and listeners to prevent memory leaks

Sample app

The repository's sample application has been upgraded to use the new updates. Updated features include:

  • Upgraded application: A "Quickstart" example using FirebaseAuthScreen to demonstrate how to implement a full authentication flow with just a few lines of code.

  • Advanced Customization (Slot APIs): A deep dive into using the new Slot APIs (EmailAuthScreen, PhoneAuthScreen), showing how to inject your own custom UI layouts while retaining the library's state management and validation logic.

  • Theming & Styling: Examples of using AuthUITheme.fromMaterialTheme() to inherit your app’s branding, and using ProviderStyle to create custom buttons.

  • Feature Walkthroughs: End-to-end demonstrations of complex flows, including federated providers, Custom providers, Multi-Factor Authentication (SMS & TOTP) enrollment and Deep Linking.

Try it out

Documentation and source for the updated library are in the v10.0.0-beta-01 branch.
Check out auth/README.md to get started or upgrade-to-10.0.md to learn how to migrate from v9.

We're seeking your feedback as we continue shaping this project, so let us know what you think by commenting below or opening a new issue!

主要語言
Kotlin
星號
4.8k
分支
1.9k
平均合併
3 天 12 小時
30 天內合併 PR
31

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

相似的 Issue

更多 Kotlin Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。