MVP에서 모델 상태를 복원하는 방법은 무엇입니까?

앱 설명

메시지(메시지 풀에서 가져옴)가 표시되고 사용자가 화면을 클릭할 때 변경되는 MVP가 있는 Android 앱을 처음으로 구현하려고 합니다. 모든 메시지가 표시되면 프로세스가 다시 시작됩니다(같은 메시지 순서에 따라). 요구 사항은 앱이 닫히거나 다시 열릴 때 동일한 메시지를 표시하는 것입니다. 따라서 MVP 모델에서 일부 저장/복원 상태 메커니즘을 구현해야 합니다.

다음은 앱의 기본 데모입니다.

MVP 디자인

이 앱에 대해 이 MVP를 다음과 같이 구현했습니다.

1. The Model takes care of what it will be the next message (it implements the application state).
2. The Presenter decides when to ask for the next message (to update the state), depending on the received events from the user (through the View).
3. The View decides how to show the actual message and communicates events from the user (clicks on the screen) to the presenter. In addition, since the View is also the MainActivity, it takes care to instantiate the Presenter and Model implementations. Finally, it saves the Model state (as a Parcelable) with onSaveInstanceState (and also restores it).

Some Code

(Partial) View implementation:

class MainActivity : AppCompatActivity(), ViewMVC {

    private lateinit var presenter: Presenter
    private var model: Model? = CircularModel(LinkedList<State>(Arrays.asList(
            State("First"),
            State("Second"),
            State("Third")

    )))

    override fun onCreate(savedInstanceState: Bundle?) {
        if (savedInstanceState != null) {
            model = savedInstanceState.getParcelable("model")
        }

        presenter = PresenterImpl(this, model!!)
    }

    override fun onSaveInstanceState(outState: Bundle?) {
        outState?.putParcelable("model", model!!)
        super.onSaveInstanceState(outState)
    }

(Partial) Model implementation:

@Parcelize
class CircularModel constructor(var states: @RawValue Deque<State>?) : Model, Parcelable {

    override fun getModelState(): State {
        return states!!.peekFirst()
    }

    override fun getModelNextState(): State {
        // Black magic happening here!
        return getModelState()
    }
}

The Problem / My question

Since Presenter and Model should be "Android agnostic", saving the app state (i.e., the Model object) is taken care by the View. However, this breaks the principle where the View doesn't know the Model. My question is: how to save the Model object, without the View knowing the actual implementation of it? What is the best way to deal with the Model state in this scenario?

An actual solution could be to write the code to serialize the Model in the Model itself and save it for each getNextState(), but this would mean use Android calls in the Model (and reduce its testability).