Could the main information screen also indicate whether non-standard parameters have been changed? E.g. modified serial baud rate, airport serial device enabled, etc? And/or hide those options behind the Advanced flag? Currently, we have to ask for multiple screenshots from the WebUI to verify no other options have been changed.

Could the main information screen also indicate whether non-standard parameters have been changed? E.g. modified serial baud rate, airport serial device enabled, etc? And/or hide those options behind the Advanced flag? Currently, we have to ask for multiple screenshots from the WebUI to verify no other options have been changed.

Yes, good idea. This is exactly the stuff I'm after.

Added a custom setting detected area in the main info screen to help with supporting users. Different things appear in the list if they are NOT set to their usual defaults, as these may be a cause for a user having difficulty.

This looks so good! Really moved us from the tabs era to the sidebar era :-D

Serial tab: Selecting any item SUMD or below makes the list pop up too high so some options go below the header

In Firefox (linux) the hamburger menu is too high for some reason, but it is fine on mobile. Chrome on the right it looks ok. If I add the mui--align-middle class to the SVG, then firefox makes it come out too low for some reason. The A tag is centered in firefox but the svg just floats above it. I hate web ui :(

• Page title is "ExpressLRS App". This is probably just a placeholder but I think we should avoid the use of the word "App" due to confusion. It would be great if this would include the type too, receiver vs transmitter
• Options screen: "Permanently arm DJI air units" is only relevant if serial protocol selected is DisplayPort, and should be grouped with that. I realize internally this is an "option" but it belongs in a panel with the DisplayPort serial settings
• The first time I went into the webui it showed "Custom Settings Detected" but with nothing in it, which confused me, but every time after that it was fine, despite me not flashing the RX again :/
• I think starting the Information page is awesome but there's nothing to do on this page so I think it is more helpful to start on any other page so on mobile you don't have to load the page, click the menu, go to the binding screen
• The socials section on the bottom of the page is huge and it really dominates the display on mobile. I think it should be smaller than the title, as this is the least important thing on the page
• Options -> Model Match - I think I wrote the text here but it is a mess. Maybe instead? "Model Match is used to prevent accidentally selecting the wrong model in the handset and flying with an unexpected handset or ELRS configuration. When enabled, Model Match restricts this receiver to only connect fully with the specific Receiver ID below. Set the transmitter's Receiver ID in EdgeTX's model settings, and enable Model Match in the ExpressLRS lua." Also rename model ID to "Receiver ID" for the edit box, and can we get a validator on the field to make sure it is only between 0-63 inclusive?
• Update screen: Don't we generate firmware.bin only now for everyone, even though it is compressed? The 8285 page requires me to upload a bin.gz extension. I feel like we gotta take the opportunity to change this clunky text here too, but I have no suggestion unless we decide to change it :-D
• Connections screen: I made a bunch of changes, didn't save, but wanted to go check and see if the Serial screen updated to allow me to change serial2 without rebooting. However, because I didn't save, when I went back to the connections screen, I lost all my changes. I guess this is true of every screen. Do we have to lose the changes just because we switch between them? Or warn someone? I know this is a lot of work so I would say this is something that could be added later.

Functionality-wise though, everything I could think of to test worked apart from like one issue above. Incredible glow up!

I've made most of the changes suggested except the following ones and the Connection screen.
w.r.t the Information page, I wanted it to be the first page for user support, but maybe it would be better to go to the binding page and rename the "Information" page to a "support" page?

The socials section on the bottom of the page is huge and it really dominates the display on mobile. I think it should be smaller than the title, as this is the least important thing on the page

Can you show me? On all my devices and in the browser they are all good.

• Update screen: Don't we generate firmware.bin only now for everyone, even though it is compressed? The 8285 page requires me to upload a bin.gz extension. I feel like we gotta take the opportunity to change this clunky text here too, but I have no suggestion unless we decide to change it :-D

Nope, it's been .bin.gz on the 8285 for a very long time. It actually accepts both, but the .bin always fails because it's too large. The JS code has not materially changed in this.
I'm open to suggestions for text as well 😄

I use WebUI extremely much, and think it looks good (Chromium/Linux) Nice work! But a thought, we "nerds" usually have dual connections, both Wifi and LAN in our computers, so the dream would also be to connect/add "Web flasher" to WebUI, that would really be an optimal solution!?

Nope, it's been .bin.gz on the 8285 for a very long time. It actually accepts both, but the .bin always fails because it's too large. The JS code has not materially changed in this.

Yeah that's been my impression as well, but the build process builds a .bin file.

def compressFirmware(source, target, env):
    """ Compress ESP8266 firmware using gzip for 'compressed OTA upload' """
    if FIRMWARE_PACKING_ENABLED:
        build_dir = env.subst("$BUILD_DIR")
        image_name = env.subst("$PROGNAME")
        source_file = os.path.join(build_dir, image_name + ".bin")
        target_file = source_file + ".gz"
        binary_compress(target_file, source_file)
        os.remove(source_file)
        os.rename(target_file, source_file) # renames .bin.gz to .bin

Thus my confusion about the lack of a .bin.gz and wondering if we had changed this to always use a renamed .bin file to avoid confusion. Where does the .gz come from?

I say "dominates" regarding the socials, but that's hyperbole on my part. I mean they are far my prominent than I think they should be, being the thing here that is trying hardest to get your attention. Why so big? It should be tucked away like an unobtrusive footnote, not appearing like it's trying to be a GDPR consent banner. The text can squish up to the icon and then the whole bar be half that size.

Looks great! I just see one problem which is on Firefox mobile the socials size is too small. It is fine on Chrome and desktop Firefox (even in devtools as mobile).