Android MVP模式下避免Presenter暴露变量的邮件发送优化方案咨询

核心问题分析 #

现有实现的问题在于View层承担了不属于它的业务逻辑：既要构建邮件主题，还要主动从Presenter获取内部状态lastKnownObject，导致View与Presenter耦合度高，违背了MVP“View负责UI交互/展示、Presenter负责业务逻辑与数据处理”的关注点分离原则。

优化方案：明确职责边界 #

调整后，View仅负责收集用户输入、提供UI层资源（字符串），Presenter全权负责数据获取、邮件内容组装及发送流程，无需向View暴露内部状态。

1. 调整Contract接口，明确职责

首先定义清晰的契约，规范View与Presenter的交互：

interface ContactContract {
    interface View {
        // 提供用户输入的邮箱
        fun getUserEmail(): String
        // 提供用户输入的问题内容
        fun getQuestionText(): String
        // 提供字符串资源格式化能力（Presenter无法直接访问Android资源）
        fun getFormattedString(resId: Int, vararg args: Any): String
        // 反馈发送结果
        fun showSendSuccess()
        fun showSendError()
    }

    interface Presenter {
        // 响应发送按钮点击
        fun onSendButtonClicked()
        // 绑定View
        fun bindView(view: View)
        // 解绑View
        fun unbindView()
    }
}

2. View层（Fragment）实现

View只做UI相关操作，不再处理业务逻辑：

class ContactFragment : Fragment(), ContactContract.View {
    private lateinit var presenter: ContactContract.Presenter
    private lateinit var emailField: EditText
    private lateinit var questionField: EditText
    private lateinit var sendButton: Button

    override fun onViewCreated(view: View, savedInstanceState: Bundle?) {
        super.onViewCreated(view, savedInstanceState)
        initViews()
        presenter = ContactPresenter(this)
        sendButton.setOnClickListener { presenter.onSendButtonClicked() }
    }

    private fun initViews() {
        emailField = view.findViewById(R.id.email_field)
        questionField = view.findViewById(R.id.question_field)
        sendButton = view.findViewById(R.id.send_btn)
    }

    // 实现View接口方法
    override fun getUserEmail(): String = emailField.text.toString().trim()
    override fun getQuestionText(): String = questionField.text.toString().trim()
    override fun getFormattedString(resId: Int, vararg args: Any): String = getString(resId, *args)
    override fun showSendSuccess() {
        Toast.makeText(context, "邮件发送成功", Toast.LENGTH_SHORT).show()
    }
    override fun showSendError() {
        Toast.makeText(context, "邮件发送失败", Toast.LENGTH_SHORT).show()
    }

    override fun onDestroyView() {
        presenter.unbindView()
        super.onDestroyView()
    }
}

3. Presenter层实现

Presenter负责所有业务逻辑：获取数据、组装邮件主题、触发发送流程，无需暴露内部状态：

class ContactPresenter(private var view: ContactContract.View?) : ContactContract.Presenter {
    private var lastKnownObject: MyObject? = null
    private val timestampFormat = SimpleDateFormat("yyyy-MM-dd HH:mm:ss", Locale.getDefault())
    private val scope = CoroutineScope(Dispatchers.IO + SupervisorJob())

    override fun bindView(view: ContactContract.View) {
        this.view = view
        fetchLastKnownObject()
    }

    override fun unbindView() {
        view = null
        scope.cancel()
    }

    private fun fetchLastKnownObject() {
        scope.launch {
            // 从Interactor获取仓库数据
            lastKnownObject = myObjectInteractor.readLastKnownObject()
        }
    }

    override fun onSendButtonClicked() {
        view?.let { safeView ->
            val userEmail = safeView.getUserEmail()
            val questionText = safeView.getQuestionText()
            val subject = buildMailSubject(safeView)
            
            // 执行邮件发送逻辑
            sendMailAndShowFeedback(userEmail, questionText, subject)
        }
    }

    // 完全由Presenter负责组装邮件主题
    private fun buildMailSubject(view: ContactContract.View): String {
        val timeStamp = timestampFormat.format(Date())
        val appName = view.getFormattedString(R.string.app_name)
        
        return if (lastKnownObject != null) {
            view.getFormattedString(
                R.string.help_contactForm_subject_with_data,
                appName,
                lastKnownObject!!.someInfo,
                timeStamp
            )
        } else {
            view.getFormattedString(
                R.string.help_contactForm_subject,
                appName,
                timeStamp
            )
        }
    }

    private fun sendMailAndShowFeedback(userMail: String, questionText: String, subject: String) {
        scope.launch {
            val sendSuccess = myMailInteractor.sendMail(userMail, questionText, subject)
            withContext(Dispatchers.Main) {
                if (sendSuccess) {
                    view?.showSendSuccess()
                } else {
                    view?.showSendError()
                }
            }
        }
    }
}

优化后的优势 #

• 关注点彻底分离：View只处理UI交互与资源提供，Presenter全权负责业务逻辑与数据流转
• 解耦View与Presenter：View不再依赖Presenter的内部状态，仅通过契约接口交互
• 可维护性提升：邮件主题的组装逻辑集中在Presenter，后续修改只需调整Presenter代码，无需改动View

内容的提问来源于stack exchange，提问作者Ionut Negru