title: Does event wrapper pattern replace the use of SingleLiveEvent?
body: <p>I'm adopting MVVM to my Android apps recently. In order to solve the problems underlying with the lifecycle of an app, Google had released LiveData. </p>
  
  <p>The usage of LiveData has different scenarios, as pointed out in the <a href="https://medium.com/androiddevelopers/livedata-with-snackbar-navigation-and-other-events-the-singleliveevent-case-ac2622673150" rel="noreferrer">medium article wrote by Jose Alcérreca</a>, you can use SingleLiveEvent or something like the event wrapper pattern.</p>
  
  <p>I want to make sure the <a href="https://github.com/googlesamples/android-architecture/blob/dev-todo-mvvm-live/todoapp/app/src/main/java/com/example/android/architecture/blueprints/todoapp/SingleLiveEvent.java" rel="noreferrer"><strong>SingleLiveEvent</strong></a>, or the <a href="https://gist.github.com/JoseAlcerreca/5b661f1800e1e654f07cc54fe87441af#file-event-kt" rel="noreferrer"><strong>event wrapper pattern</strong></a>, which one would be the best practice to use with LiveData in Android MVVM architecture. And I found the <a href="https://github.com/google/iosched" rel="noreferrer">Google I/O app</a> of this year(2018) have no usages of <strong>SingleLiveEvent</strong>, it uses <strong>event wrapper pattern</strong> instead.</p>
  
  <p>Previously I have opened an <a href="https://github.com/googlesamples/android-architecture/issues/593" rel="noreferrer">issue</a> on the project <a href="https://github.com/googlesamples/android-architecture" rel="noreferrer">android-architecture</a>, at first I'm seeking an official reply, but it seems to have no comments at all. As a result, I would like to hear the advice from the developers who already use these stuff and have reflections on it. </p>
  
  <p>Please share your precious experiences, thank you in advance.</p>