I suppose the widget uses some kind of static cache that shares its lifetime of the widget itself, and loads nothing anymore. I simply don't see why it works so. it's not like users need a huge amount of data on their home screen, hence optimization; or the widget has problem accessing the local libraries, the app's own data. If it is complicated for the widget to decide when to update, why not leave it to us? We could do it by, for example, just pressing refresh button on the widget or (preferably) setting the update schedule when adding it.
Miles supported this idea ·
I suppose the widget uses some kind of static cache that shares its lifetime of the widget itself, and loads nothing anymore. I simply don't see why it works so. it's not like users need a huge amount of data on their home screen, hence optimization; or the widget has problem accessing the local libraries, the app's own data. If it is complicated for the widget to decide when to update, why not leave it to us? We could do it by, for example, just pressing refresh button on the widget or (preferably) setting the update schedule when adding it.