That way you are still persisting partially built ...

# android-architecture

[Davor Maric]

That way you are still persisting partially built appointment, but, since the object is created at runtime and memory is already allocated, there shouldn't be any problems as long as appointment class isn't resource heavy