<@U0PR0TZ53> I'm relatively new to Clean Arch and ...

# android-architecture

[z0rawar]

@Danilo Herrera I'm relatively new to Clean Arch and have been trying to refactor my app using Clean for a while now, so correct me if i'm wrong, but I've come across this question quite many times.

The idea is to make your codebase as decoupled as possible. That is the reason you'll find Mapper classes to transform models at each layer. But IMO, if you have absolute control over your API and there are no differences between how you model your entities and how you present them, then you might get away with not having 3 data models.

The recommended approach is mostly ApiResponseObject --> PresentationLayerDO--> EntityDO

You can find a good working example in this repo here https://github.com/bufferapp/android-clean-architecture-boilerplate/blob/9a1308c42c0c882fc724a0e579ee1ce4d454f961/mobile-ui/src/main/java/org/buffer/android/boilerplate/ui/mapper/BufferooMapper.kt