GJakutonis

[ghost]

Some design assumptions:

• token is short lived and can not be reused for a long period
• servers list is short enough (up to 100 items) to be stored after each remote fetch as is and listed without filtering option

Some design simplifications (based on context of the task):

• Application used as central access point for singleton Room database (could be injected)
• All server records are swapped after each remote result (could be updated based on unique key)
• Remote vs Local load logic in ViewModel layer (could be in injectable Repository)
• Instrumentation tests only (could be some unit tests for Repository, see point above)
• Backend SSL certificate is verified by well known CA and there is no need to limit acceptable certificates (could be additional work on OkHttp client)
• Proguard turned off
• Remote logging and tracking not applied