Jump to content

New AWC site is now live


Recommended Posts

Like to know what you think.  I am having a difficult time using it on my iPhone...it crashes most of the time when I zoom out on the map.  Both Chrome and Safari. The static imagery page is almost unusable.  You have to constantly scroll up/down to choose and view the image you want to view.  

image.png.9578addd6df574ce5108c211a2a9f710.png

image.png.2e7e657de90db49f2ab9a962b6cba2c6.png

 

Edited by Scott Dennstaedt, PhD
Link to comment
Share on other sites

1 hour ago, ohdub said:

Yes, from the Google Play store.

Ah, okay. You must be talking about some other app.  I searched on the Google Play and App Store and did not see any downloadable apps for aviationweather.gov.  Nothing that I can find on aviationweather.gov either to indicate there was a *native* app.  A progressive web app (PWA) for sure, but not a native app for aviationweather.gov.  

 

Edit: Just checked with the folks at the AWC and there's no native app on the Google Play or App Store.  

Edited by Scott Dennstaedt, PhD
Link to comment
Share on other sites

With this new site, the AWC will be eliminating (or has eliminated) much of the "static" imagery.

Right now, the static imagery being kept for a while is:
G-AIRMETs
SIGMETs
WPC Prog charts
SigWx charts
Icing (CIP/FIP)
Turbulence (GTG)
GFA static images (under /gfa/plot on the legacy website)
B&W Fax charts

Static images going away soon/now:
Lowest freezing level from the RAP
TCF, eTCF, ECFP
RAP/NAM Wind/Temp graphics
TAF plots
PIREP plots
METAR plots
Satellite regional plots
Vis/Fog satellite images
Radar regional plots
RCM radar plots

Of course, some of this imagery is encapsulated in the interactive map...which on my iPhone crashes every time when doing a pinch to zoom out gesture. The graphics section is really hard to use. Takes many clicks to get to the images you want to see without a lot of scrolling up/down...pretty much unusable. I will keep as many of the static images available on my site until they turn off the production of those...then I will build my own.

Link to comment
Share on other sites

1 hour ago, Scott Dennstaedt, PhD said:

Ah, okay. You must be talking about some other app.  I searched on the Google Play and App Store and did not see any downloadable apps for aviationweather.gov.  Nothing that I can find on aviationweather.gov either to indicate there was a *native* app.  A progressive web app (PWA) for sure, but not a native app for aviationweather.gov.  

 

Edit: Just checked with the folks at the AWC and there's no native app on the Google Play or App Store.  

When I opened the AWC web page on Chrome a notification popped up to download the app, I clicked it and an AWC app installed. I guess I didn't actually go to the Google store to get it, I just assumed it came from there. Here is a screen shot of it.

 

Screenshot_20231016_141719_Chrome.jpg

Link to comment
Share on other sites

In a word, "sucks".

Now, get off my lawn!

 

P.S. I'm really going to be annoyed if they get rid of the Prog Charts.  Hell, I'm old enough to remember reading them from a tele-fax back when you could actually walk into a weather briefing office!

  • Haha 1
Link to comment
Share on other sites

On 10/16/2023 at 1:18 PM, ohdub said:

When I opened the AWC web page on Chrome a notification popped up to download the app, I clicked it and an AWC app installed. I guess I didn't actually go to the Google store to get it, I just assumed it came from there. Here is a screen shot of it.

Interesting.  When I go to aviationweather.gov on my iPad (Safari), there is no mention of an app.  The top results from a search for apps give me some church or the Army War College.  And, accessing the web site is fairly intuitive with pretty snappy performance.  Not exactly loving it, but it's not too bad.

Link to comment
Share on other sites

On 10/16/2023 at 1:08 PM, Scott Dennstaedt, PhD said:

With this new site, the AWC will be eliminating (or has eliminated) much of the "static" imagery.

So, what if you want to download to look at things like that when internet may not be readily available, such as reviewing weather brief during a flight?

Link to comment
Share on other sites

9 hours ago, MikeOH said:

In a word, "sucks".

Now, get off my lawn!

 

P.S. I'm really going to be annoyed if they get rid of the Prog Charts.  Hell, I'm old enough to remember reading them from a tele-fax back when you could actually walk into a weather briefing office!

The prog charts are expected to remain. However, even if they do, the WPC will have them since they are the organization that generates them.  I import the WPC progs into my app since they are updated more frequently then the ones at the AWC.  

  • Thanks 1
Link to comment
Share on other sites

3 hours ago, Fly Boomer said:

Interesting.  When I go to aviationweather.gov on my iPad (Safari), there is no mention of an app.  The top results from a search for apps give me some church or the Army War College.  And, accessing the web site is fairly intuitive with pretty snappy performance.  Not exactly loving it, but it's not too bad.

The AWC doesn't have a native app that you will find in the Google Play or App Store.  It's a progressive web app like I use for my site. PWA or not, their site is horrible on portable devices like the iPhone. It crashes way too often and just is hard to navigate.  

Edited by Scott Dennstaedt, PhD
Link to comment
Share on other sites

2 hours ago, Scott Dennstaedt, PhD said:

The AWC doesn't have a native app that you will find in the Google Play or App Store.  It's a progressive web app like I use for my site.  It's horrible on portable devices like the iPhone. It crashes way too often and just is hard to navigate.  

I don't see the point.  Why install an app when the native web site works fine?

Link to comment
Share on other sites

1 minute ago, Fly Boomer said:

So the app uses less resources than the browser?  Too complicated for me.

What complexity are you referring to?  You simply install this as a PWA and you are done. It just adds an icon to your desktop or home screen and you can launch it just like any other native app.  Again, how complex is that?  It's actually quicker than searching and downloading from the App Store. And when there are updates, they become available immediately and there's no need to interact with Apple or Google to get those updates  Again, I see that as "less" complex, not more.   

Link to comment
Share on other sites

4 minutes ago, Scott Dennstaedt, PhD said:

What complexity are you referring to?  You simply install this as a PWA and you are done. It just adds an icon to your desktop or home screen and you can launch it just like any other native app.  Again, how complex is that?  It's actually quicker than searching and downloading from the App Store. And when there are updates, they become available immediately and there's no need to interact with Apple or Google to get those updates  Again, I see that as "less" complex, not more.   

So how is this desktop icon for a PWA any different than a simple link to a website? After all, if this ?app? is running on the web what’s the advantage?

Link to comment
Share on other sites

Just now, Scott Dennstaedt, PhD said:

What complexity are you referring to?  You simply install this as a PWA and you are done. It just adds an icon to your desktop or home screen and you can launch it just like any other native app.  Again, how complex is that?  It's actually quicker than searching and downloading from the App Store. And when there are updates, they become available immediately and there's no need to interact with Apple or Google to get those updates  Again, I see that as "less" complex, not more.   

As someone who is a SWE/SRE and professionally manages very large applications and APIs... PWAs have a very small use case list where they are not terrible. Loading everything into a Javascript or Typescript based frame work generally ends poorly. PWAs can only take advantage of whatever the browser supports, where a native application can take advantage of the hardware far more effectively.

PWAs are popular because you can build something quickly and cheaply that works on many browsers. When you need to load a bunch of data, process it, display it, etc. I would not be picking a PWA. Its very easy to consume whatever memory limits the browser allows on a phone, on iPhone I believe its under 515MB. I dont even think Apple publishes an official number either.

  • Like 1
Link to comment
Share on other sites

23 minutes ago, MikeOH said:

So how is this desktop icon for a PWA any different than a simple link to a website? After all, if this ?app? is running on the web what’s the advantage?

Here's what I wrote up when I decided to launch my site as a PWA instead of a native app. You also have to deal with the orientations of smaller devices like an iPhone in both orientations. When you have a browser in landscape, the address bar takes up valuable space that you may want to utilize for other buttons/selections.  

https://www.avwxtraining.com/post/the-scoop-on-progressive-web-apps-pwas-ezwxbrief

Edited by Scott Dennstaedt, PhD
  • Thanks 1
Link to comment
Share on other sites

2 minutes ago, MikeOH said:

So how is this desktop icon for a PWA any different than a simple link to a website? After all, if this ?app? is running on the web what’s the advantage?

The only advantage is they dont need to manage native application tech debt. They can build a single PWA that runs on the browser and hope it works correctly. Its basically a web page using javascript tuned for mobile.

  • Thanks 1
Link to comment
Share on other sites

On 10/18/2023 at 1:59 PM, dzeleski said:

As someone who is a SWE/SRE and professionally manages very large applications and APIs... PWAs have a very small use case list where they are not terrible. Loading everything into a Javascript or Typescript based frame work generally ends poorly. PWAs can only take advantage of whatever the browser supports, where a native application can take advantage of the hardware far more effectively.

PWAs are popular because you can build something quickly and cheaply that works on many browsers. When you need to load a bunch of data, process it, display it, etc. I would not be picking a PWA. Its very easy to consume whatever memory limits the browser allows on a phone, on iPhone I believe its under 515MB. I dont even think Apple publishes an official number either.

With my PWA, I don't need any native operations like some of the heavyweight EFBs use.  In fact, many apps (probably a majority of them) that you download from the App Store are just regular web apps with a wrapper.  

Edited by Scott Dennstaedt, PhD
Link to comment
Share on other sites

6 minutes ago, dzeleski said:

The only advantage is they dont need to manage native application tech debt. They can build a single PWA that runs on the browser and hope it works correctly. Its basically a web page using javascript tuned for mobile.

That's correct...and if the code is designed properly, there are generally little issues and you get compatibility across the different platforms. For now, most browsers support PWAs, so it creates the look and feel of a native app without the costs involved.    

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.