Multiple modules referencing same local entity

I am developing a mobile application that supports offline feature and it has two end user modules. Both modules make use of same local entity. If I keep this local entity in one of the end user modules then this would result in side reference in end user layer violating 4layer architecture.

To handle this, like server entities, I plan to keep this local entity in a common module in core layer which can then be referenced in both end user modules. Please let me know if this is the right approach and would there be any implementation challenges?



Yes, that is the right way to approach.

It does not matter if you are developing mobile or web: this is the way to go for both.