mortar

I'm trying to convert an Acticity + Fragments app to Flow + Mortar + Dagger2 I would like to save & restore screen state when jumping from screen to screen (at least backwards). What is the prefered/recommanded way to do that ? I have spent quite a lot of time looking at flow and mortar readmes and samples but couldn't figure it out (the documentation and samples are minimal and only deal with simple/static/unique data). Say, for example, you have a browser-like app that moves from Page to Page Where each Page use the same same PageView class, the same PagePresenter Class but have different

I am looking to integrate an application with Google Play Services and Mortar to retrieve the user's current location. https://developer.android.com/training/location/retrieve-current.html#CheckServices This requires handling onActivityResult() in the case that Google Play Services is not available. My first instinct on how to do this is to make getFirstScreen() in Main.java return a blank loading screen. https://github.com/square/mortar/blob/master/mortar-sample/src/main/java/com/example/mortar/core/Main.java After injection, during onCreate() perform the check to see if Google Play Services

Some third party libraries use hooks into the activity lifecycle to work correctly - for instance, the Facebook SDK ( https://developers.facebook.com/docs/android/login-with-facebook/ ). I'm having some trouble figuring out how to reconcile this model cleanly with a single-activity flow+mortar setup. For instance, if I want to use Facebook login as part of a login Flow (w/ FlowView/FlowOwner), but not otherwise in the activity, what's the smartest way to pull this off if you need hooks for that particular flow in onCreate, onResume, onPause, onDestroy, onSaveInstanceState, onActivityResult,