Add caching of favorites in Wear OS, resulting in prettier loading

[mads03dk]

Summary

Added local caching of the friendly_name and icon properties in the WearOS app, thus avoiding using the entity ID and a bookmark icon whilst waiting for the server to send the current states. Aimed to achieve a prettier visual while waiting for the connection to be established

Screenshots

Before, whilst waiting for a connection:

Now, whilst waiting for a connection:

Settings:

Any other notes

Only favorites are cached, since they're the first entities to be shown. Cached is updated every time the entity is received from the server or added/removed from the list of favorites. Some internals of the getIcon function has also been updated to allow direct usage of icon-strings

Please note;
This is my very first go at native app development (hereby Kotlin), so I expect some - if not all - of my changes to be suboptimal. I'm really open to suggestions and would love to get some constructive feedback, but don't go too harsh, haha!

[home-assistant]

Hi mads03dk

It seems you haven't yet signed a CLA. Please do so here.

Once you do that we will be able to review and accept this pull request.

Thanks!

[jpelgrom]

Hi 👋 This is a really nice idea

For database changes please increase the version as you're changing something for it. Right now, upgrades of existing installs won't work. When increasing the version this also means that the existing JSON files that describe the database don't change, and you can probably use an AutoMigration instead of writing SQL yourself.

[jpelgrom]

In addition to the more general comment about database changes above, a few more specific notes. If anything is unclear feel free to add a comment :)

[jpelgrom]

I've been thinking, do we need a clear cache button in the settings? The app handles adding/updating/deleting on load, when the favorites are edited and on logout.

[jpelgrom]

I've been thinking, do we need a clear cache button in the settings? The app handles adding/updating/deleting on load, when the favorites are edited and on logout.

@mads03dk What is your opinion on this ^ ?

[mads03dk]

Hmm. Since the cache is updated every time data is received, I also deem it unnecessary. If you feel the same way, let me know, and I will remove it :)

[jpelgrom]

Yes it also seems unnecessary to me, so feel free to remove it :)

[jpelgrom]

Thanks, nice first contribution!