1-parcelable and serializable technique both are sending data from one activity to another activity. -> In Parcelable, developers write custom code for marshaling and unmarshaling so it creates less garbage objects in comparison to Serialization. -> Android Inter-Process Communication (AIPC) file to tell Android how is should marshal and unmarshal your object .It is less generic and doesn't use reflection so it should have much less overhead and be a lot faster.
The performance of Parcelable over Serialization dramatically improves (around two times faster), because of this custom implementation. Android Parcelable came out to be faster than the Java Serialization technique . one of the main reasons was the fact that Parcelable is fully customizable, allowing developers to convert required data into Parcelable. Serialization is a marker interface as it converts an object into a stream using the Java reflection API. Due to this it ends up creating a number of garbage objects during the stream conversation process.
