>Any memory allocation will break Clean Archite...
# android-architecture
g
Any memory allocation will break Clean Architecture
that sounds a bit dogmatic, imho) So, probably an in-memory Store/Cache below Repository? I mean, @morganbovi described a pretty common, concrete use case. It doesn't help much to say "be careful" or generic stuff about SOLID. How would you structure this app if you don't have to persist a partially built appointment, only the final one?