Indicate warnings in widget #92

Open
opened 4 months ago by F_Thoma · 3 comments
F_Thoma commented 4 months ago

If there are any warnings for the set location, there should be a symbol in the widget that indicates this.
It could work the same way as in the app, where you can tap on the symbol to show the text of the warning (maybe it is necessary to temporarily hide some other information to get enough space).

If there are any warnings for the set location, there should be a symbol in the widget that indicates this. It could work the same way as in the app, where you can tap on the symbol to show the text of the warning (maybe it is necessary to temporarily hide some other information to get enough space).
Starfish added the
enhancement
label 4 months ago
Owner

This could be done, but would need some overhead work.

Currently, warnings are polled only when the app is actively opened by the user.

  • When I put warnings in the widget(s), warnings would need to be polled at least every 30 minutes. This would increase battery use and data volume use significantly.

  • There is a significant danger that widgets don't update properly due to evil battery saving features of certain devices/roms, see the faq .

  • at the end, this feature might need a foreground service permanently running, this is something I managed to circumvent up to now with some very innovative java coding. :-) This will come with a penalty on device performance & battery use.

  • To avoid unnecessary data polling, the app would need to reliably check if at least one widget that is supposed to display warnings is visible on the home screen. Downside: all official methods to check if a widget is on the home screen are broken to my knowledge. Before implementing warnings in widgets, this needs to be solved.

By the way: none of the issues is specific to this app. Other apps suffer the same.

TL;DR: can be done, but is not straight forward and requires a good deal of work.

Please give positive or negative feedback: is this a feature you all really want???

This could be done, but would need some overhead work. Currently, warnings are polled only when the app is actively opened by the user. * When I put warnings in the widget(s), warnings would need to be polled at least every 30 minutes. This would increase battery use and data volume use significantly. * There is a significant danger that widgets don't update properly due to evil *battery saving features* of certain devices/roms, see the [faq](https://codeberg.org/Starfish/TinyWeatherForecastGermany#my-widgets-don-t-get-updated-unless-i-open-the-app) . * at the end, this feature might need a *foreground service permanently running*, this is something I managed to circumvent up to now with some very innovative java coding. :-) This will come with a penalty on device performance & battery use. * To avoid unnecessary data polling, the app would need to reliably check if at least one widget that is supposed to display warnings is visible on the home screen. Downside: all official methods to check if a widget is on the home screen are **broken** to my knowledge. Before implementing warnings in widgets, this needs to be solved. By the way: none of the issues is specific to this app. Other apps suffer the same. TL;DR: can be done, but is *not* straight forward and requires a good deal of work. **Please give positive or negative feedback: is this a feature you all really want???**

There was also some discussion on this in #33

Initially, I found the idea very interesting. However, entering the warnings domain is a sensitive thing, something that sort of has to work, otherwise it's useless to dangerous. One can argue, that this is done by some official channels and whatever fancy service were invented recently, so no need to reimplement this functionality.

It seems simple to show the orange cloud from the main screen also in the widget, if I know there has to be one. But as disussed in the thread mentioned, and also above, it might be difficult for users to understand: this cloud is there cause there was something 6h ago, when your device last fetched data, or even worse there would be a very dark cloud here if you had just updated, but you didn't refresh. (It's somewhat similar to #72.)

warnings would need to be polled at least every 30 minutes

Depending on the kind of warning this might not be sufficient. IOW I am pretty sure that my device looses on quite some warnings in Warnwetter, if I don't look at it all the time. (I'm not sure how these push-notifications should work.)

To avoid unnecessary data polling

My gut feeling is, that if you enter the domain where the app actively should forward warnings (this would be the point of the widget getting the icon, so issuing an alert would be the next logical step) you will have to leave this strict data conservation. Most likely usage could be minimized if the service gives only the warnings for the currently selected region, but you'd either need to allow a push or poll pretty frequently.

can be done, but is not straight forward and requires a good deal of work.

Given your estimate for a good deal of work I have to admit, that I would prefer progress on #23, instead. For the warning notification there is sort of a solution using official stuff, while for this I don't know of anything (decent) yet. So there is a chance for some unique characteristics here.

There was also some discussion on this in https://codeberg.org/Starfish/TinyWeatherForecastGermany/issues/33#issuecomment-178761 Initially, I found the idea very interesting. However, entering the warnings domain is a sensitive thing, something that sort of _has to work_, otherwise it's useless to dangerous. One can argue, that this is done by some official channels and whatever fancy service were invented recently, so no need to reimplement this functionality. It seems simple to show the orange cloud from the main screen also in the widget, if I know there has to be one. But as disussed in the thread mentioned, and also above, it might be difficult for users to understand: _this cloud is there cause there was something 6h ago, when your device last fetched data_, or even worse _there would be a very dark cloud here if you had just updated, but you didn't refresh_. (It's somewhat similar to #72.) > warnings would need to be polled at least every 30 minutes Depending on the kind of warning this might not be sufficient. IOW I am pretty sure that my device looses on quite some warnings in Warnwetter, if I don't look at it all the time. (I'm not sure how these push-notifications should work.) > To avoid unnecessary data polling My gut feeling is, that if you enter the domain where the app actively should forward warnings (this would be the point of the widget getting the icon, so issuing an alert would be the next logical step) you will have to leave this strict data conservation. Most likely usage could be minimized if the service gives only the warnings for the currently selected region, but you'd either need to allow a push or poll pretty frequently. > can be done, but is not straight forward and requires a good deal of work. Given your estimate for a _good deal of work_ I have to admit, that I would prefer progress on #23, instead. For the warning notification there is sort of a solution using official stuff, while for this I don't know of anything (decent) yet. So there is a chance for some unique characteristics here.
Poster

For me personally this feature is not really needed. I think I came across this because I wanted to check the weather and just used the widget. I missed a warning but got a text from somebody else about the warning.

I think people expect the widget to work the same way as the app. For that reason it should maybe be mentioned in an introduction that warnings are only shown in the app.

For me personally this feature is not really needed. I think I came across this because I wanted to check the weather and just used the widget. I missed a warning but got a text from somebody else about the warning. I think people expect the widget to work the same way as the app. For that reason it should maybe be mentioned in an introduction that warnings are only shown in the app.
Sign in to join this conversation.
No Milestone
No Assignees
3 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.