Suggested ways to handle object persistence on Android activity recreation -

Suggested ways to handle object persistence on Android activity recreation -

in android application there many instances multiple activities phone call mutual service passing callback if activity destroyed , recreated (say due orientation change) there every chance callback reference lost. know normal ways of using onsavedinstance method or headless fragment of persisting. in way activities have handle it. there mutual way handle this.

note : want have simple , reusable code persistence happen

i want have simple , reusable code persistence happen

you can create activity class write state management boilerplate code , create other activities inherit base of operations activity.

android android-activity