Serialization is persisting an object from memory to a sequence of bits, for instance for saving onto the disk. Deserialization is the opposite – reading data from the disk to hydrate/create an object. In the context of your question, it is an interface that if implemented in a class, this class can automatically be serialized … Read more
From the javadoc: The serialization runtime associates with each serializable class a version number, called a serialVersionUID, which is used during deserialization to verify that the sender and receiver of a serialized object have loaded classes for that object that are compatible with respect to serialization. If the receiver has loaded a class for the … Read more
To add to the other answers, by implementating java.io.Serializable, you get “automatic” serialization capability for objects of your class. No need to implement any other logic, it’ll just work. The Java runtime will use reflection to figure out how to marshal and unmarshal your objects. In earlier version of Java, reflection was very slow, and … Read more
In Android we cannot just pass objects to activities. To do this the objects must either implement Serializable or Parcelable interface. Serializable Serializable is a standard Java interface. You can just implement Serializable interface and add override methods. The problem with this approach is that reflection is used and it is a slow process. This … Read more
A JavaBean is just a standard. It is a regular Java class, except it follows certain conventions: All properties are private (use getters/setters) A public no-argument constructor Implements Serializable. That’s it. It’s just a convention. Lots of libraries depend on it though. With respect to Serializable, from the API documentation: Serializability of a class is … Read more