Mobile entity exposed as public with read/write best practice/recommendation

Mobile entity exposed as public with read/write best practice/recommendation

  

It would be great to collect some thoughts around exposing local storage entities as public and then re-using them between multiple mobile applications.  

I am sure that there are some good experience lessons and thoughts on this topic amongst the community.

From a rate of change perspective, I would not recommend doing this for data which is core to the mobile application.

There may be usage scenarios around creating a persisted "session"  storage to hold values that are common to a specific component.

Please, share your thoughts and questions. . .

My thought? Don't do it.


Despite being somewhat a kind of "Don't Repeat Yourself" principle, I would rather have everything within their own scope.


Cheers!