@idefix37 thanks for pointing out the browser offline mode. I just tried it with iOS via Opera (in my experience the most enforcing mobile browser to request a non-mobile website representation) but fell victim to the stuck download bug.

This experimental browser feature already goes in the right direction.
What I imagine is more automatic and not limited to the browser version. In pictures, substituting the following example screens automatically with last fetched data would be the objective:

Does such an automatic offline mode for mobile devices fit on the roadmap? How can the user base help to approach this?

Hi @Suty , I too as an app user have interest for the change. I created Feature Request: Enable Offline Access to Last Displayed Data and was guided here.
Can you shed light on how demand of app users was measured? I imagine just deducing that from an experimental browser feature is not taking the right sample to measure for interest of app users.
Would this not be a perfect USP for premium users? Offline support is a very common premium incentive for tons of other apps - so something what potential premium candidates will understand quickly. And to my knowledge no other forecast app is so far offering this. Thus, cost/benefit analysis outcome could already be very demanding for the change

@idefix37 true, I imagine too that who decides to bring a computer instead of just a mobile device might be less frequently affected by disconnect cases.
The reasoning for postponing it for the app is hard to follow. I’ll follow this up in the thread where the decision was communicated

@idefix37 thanks for pointing out the browser offline mode. I just tried it with iOS via Opera (in my experience the most enforcing mobile browser to request a non-mobile website representation) but fell victim to the stuck download bug.

This experimental browser feature already goes in the right direction.
What I imagine is more automatic and not limited to the browser version. In pictures, substituting the following example screens automatically with last fetched data would be the objective:

Does such an automatic offline mode for mobile devices fit on the roadmap? How can the user base help to approach this?

Hi,

Why does Windy require an active internet connection to display previously loaded data? When I go offline, I find myself relying on screenshots to recall the last weather forecast, which seems counterintuitive for an app designed for active users who might frequently lose connectivity.

Would it be possible to show the last fetched data even when offline? This could be done with an offline-specific UI, like a greyed-out interface or an info text indicating that the data is out of sync and showing when it was last updated.

I'm not suggesting that everything be stored constantly, but perhaps a limited set of features for a few locations could be retained. This would not only enhance usability but also eliminate the need for clunky error screens that take up space unnecessarily. The current iOS widgets, which display cut-off error texts, highlight the need for this improvement.

Implementing this feature would benefit many users and set Windy apart from other apps that overlook this functionality.