在 Android 开发中,良好的用户反馈机制至关重要。Jetpack Compose 提供了现代化的 UI 构建方式,但提示信息(Toast/Snackbar)的管理往往显得分散。本文将介绍如何优雅地封装提示信息,提升代码可维护性。
一、基础封装方案
1. 简单 Snackbar 封装
@Composable
fun SnackbarHelper(hostState: SnackbarHostState,message: String?,duration: SnackbarDuration = SnackbarDuration.Short,actionLabel: String? = null,onAction: (() -> Unit)? = null,onDismiss: () -> Unit = {}
) {val scope = rememberCoroutineScope()LaunchedEffect(message) {message?.let {hostState.showSnackbar(message = it,duration = duration,actionLabel = actionLabel).also { result ->if (result == SnackbarResult.ActionPerformed) {onAction?.invoke()}}onDismiss()}}
}
2. 简单 Toast 封装
@Composable
fun ToastHelper(message: String?) {val context = LocalContext.currentLaunchedEffect(message) {message?.let {Toast.makeText(context, it, Toast.LENGTH_SHORT).show()}}
}
二、进阶状态管理方案
1. 消息状态模型
sealed class MessageState {object Idle : MessageState()data class Snackbar(val message: String,val duration: SnackbarDuration = SnackbarDuration.Short,val action: SnackbarAction? = null) : MessageState()data class Toast(val message: String) : MessageState()
}data class SnackbarAction(val label: String,val onClick: () -> Unit,val withDismiss: Boolean = true
)
2. 消息管理器 ViewModel
class MessageManager : ViewModel() {private val _messageState = mutableStateOf<MessageState>(MessageState.Idle)val messageState: State<MessageState> = _messageStatefun showSnackbar(message: String,duration: SnackbarDuration = SnackbarDuration.Short,action: SnackbarAction? = null) {_messageState.value = MessageState.Snackbar(message, duration, action)}fun showToast(message: String) {_messageState.value = MessageState.Toast(message)}fun reset() {_messageState.value = MessageState.Idle}
}
3. 消息处理器组件
@Composable
fun MessageHandler(state: MessageState,snackbarHostState: SnackbarHostState,onMessageShown: () -> Unit
) {val context = LocalContext.currentLaunchedEffect(state) {when (state) {is MessageState.Snackbar -> {val result = snackbarHostState.showSnackbar(message = state.message,duration = state.duration,actionLabel = state.action?.label)if (result == SnackbarResult.ActionPerformed) {state.action?.onClick?.invoke()}if (state.action?.withDismiss != false) {onMessageShown()}}is MessageState.Toast -> {Toast.makeText(context, state.message, Toast.LENGTH_SHORT).show()onMessageShown()}MessageState.Idle -> Unit}}
}
三、完整使用示例
1. 项目级封装
@Composable
fun MessageScaffold(messageManager: MessageManager = viewModel(),content: @Composable (PaddingValues) -> Unit
) {val snackbarHostState = remember { SnackbarHostState() }Scaffold(snackbarHost = { SnackbarHost(hostState = snackbarHostState) }) { padding ->Box(modifier = Modifier.fillMaxSize()) {content(padding)MessageHandler(state = messageManager.messageState.value,snackbarHostState = snackbarHostState,onMessageShown = { messageManager.reset() })}}
}
2. 具体页面使用
@Composable
fun ProductDetailScreen() {val messageManager: MessageManager = viewModel()MessageScaffold {Column(modifier = Modifier.padding(it)) {// 页面内容...Button(onClick = {messageManager.showSnackbar(message = "商品已加入购物车",action = SnackbarAction(label = "查看",onClick = { /* 导航到购物车 */ }))}) {Text("加入购物车")}Button(onClick = {messageManager.showToast("收藏成功")}) {Text("收藏商品")}}}
}
四、高级功能扩展
1. 消息队列支持
class QueuedMessageManager : ViewModel() {private val _messageQueue = mutableStateListOf<MessageState>()private var isProcessing = falsefun sendMessage(message: MessageState) {_messageQueue.add(message)processNext()}private fun processNext() {if (isProcessing || _messageQueue.isEmpty()) returnisProcessing = true_currentMessage.value = _messageQueue.removeAt(0)}fun onMessageProcessed() {isProcessing = falseprocessNext()}// 其余实现与基础MessageManager类似...
}
2. 自动消失控制
fun MessageManager.showTimedSnackbar(message: String,durationMillis: Long = 3000,action: SnackbarAction? = null
) {showSnackbar(message = message,duration = if (action != null) SnackbarDuration.Indefinite else SnackbarDuration.Short,action = action)if (action == null) {viewModelScope.launch {delay(durationMillis)reset()}}
}
五、最佳实践建议
- 统一入口:所有提示信息通过同一管理器发出
- 状态集中:使用密封类管理所有提示状态
- 自动清理:消息显示后自动重置状态
- 可扩展性:设计应考虑未来可能的消息类型扩展
- 测试友好:ViewModel 应易于单元测试
六、总结
通过这种封装方式,我们获得了:
- 统一的提示信息管理入口
- 类型安全的提示状态处理
- 良好的代码组织和可维护性
- 易于扩展的新消息类型支持
- 简化的业务代码调用方式
这种模式特别适合中大型项目,能够有效管理应用中的各种用户反馈信息,使开发者可以更专注于核心业务逻辑的实现。