Changing the local storage from SharedPreferences to Hive to demonstrate the separation of concerns

[Uuttssaavv]

Clean architecture provides a clear separation of concerns, encourages the use of interfaces and abstractions, and facilitates changes in the dependencies without affecting the core logic of the application.
This makes it easier to maintain, test, and extend the system over time.

With clean architecture, you can replace the SharedPreferences with Hive without affecting the core logic of the application. You would simply need to modify the data access layer, which is responsible for interacting with the data storage system. By swapping out the SharedPreferences implementation with the Hive implementation, you can change the data storage system without affecting the rest of the application.

In this PR, we simply changed the implementation and test files to change the data storage system without affecting the core logic of the application.

[WojuadeAA]

i think this should be on a separate branch?

[tariq235]

Regarding the security aspect, would storing the user token in the keychain be a better option? I believe the user token should be stored in the keychain for enhanced security, while the remaining data could be stored in Hive. What are your thoughts on this approach?

[Uuttssaavv]

Regarding the security aspect, would storing the user token in the keychain be a better option? I believe the user token should be stored in the keychain for enhanced security, while the remaining data could be stored in Hive. What are your thoughts on this approach?

Yes, for the sensitive information.
But, the thing I am trying to demonstrate here is how we can switch between the dependencies :)