I want to improve the performance of my application. One thing that comes to my mind is to replace all serializable options for merging with options.
I found this topic: The advantage of using Parcelable instead of serializing an object
There, someone says, from a book, that parcelable is only for interprocess communication? This is probably not up to date, is it? Because it is at least technically possible.
Then it’s also a statement that parcelable is not reliable, since the implementation varies on different devices, this, of course, is a characteristic of killing, since I want it to always work, all devices and apis, starting with API 7.
And I also read some tips on using Externalizable or implementing a user protocol ... but I don’t understand why Parcelable is not reliable, why are Android developers so noisy around something that won't work on all devices? Or is the comment untrue?
Is it worth implementing Parcelable? Am I Serializable? Or a custom serialization / external approach to the right approach?
Please don’t tell me “just try”, I don’t have time for this, especially for checking the reliability of Parcelable (and also not enough devices) ... the experience is being set ...
Thank.
P.S. , "Serializable ". , , Parcelable ( - ), .