I uploaded latest Windy app for iOS along with current iOS for iPhone and iPad. I plotted a route. Asked to Share the plotted route. The “on.Windy” address failed. Safari reports the link is bad.

I then went on Safari and created the same route. The browser plot was created and the “Share” new link then worked.

Here is the working link… https://on.windy.com/8bavk
This is the non working link… https://on.windy.com/4vp8p

I want to use Windy.com on my iPad in my Safari Browser. When I bring it up the Windy App is offered/encouraged. (See image). The issue is it uses up space that I want for my weather map. I have the APP. I want to use the browser. How do I stop this APP advertisement?

@idefix37 Thanks. That resolved the issue.

When using the Safari browser on iPad, Windy posts a reminder at the top of the page to get the Windy App. This consumes map space. Sometimes it is more important to use Windy in the browser than the app. Especially when communicating locations and routes with a person using the internet browser version.

How do I remove the "Get WINDY app" from the browser screen.

This frustration was found when trying to share a windy screen from the app to a browser.
The "share" function of the app does not work with Safari. The link returns error message... "Safari cannot open the page because the address is invalid."

Here is the link produced by the app.
https://on.windy.com/4vp8p

Here is the link produced by the browser.
https://on.windy.com/8a5of

When using the planning option why does the wind direction (in the bottom forecast section) show the wind is coming out of the NE but the weather map and wind motion show the wind is coming out of the NW. It appears disconnected.

Currents Feature:
Real cool. Like the ability to get current data with my weather. Makes planing a cruise easier. Looking in the Puget Sound you have a glitch . The location of a current is not accurate. Attached is a clipped image from the app. The Skagit Bay is not in the middle of the land (island) displayed.
Tried to get you an image of the error but it was too big for you report here.