As long as those users aren't disabled.
In-Flight Entertainment Challenge
81–84 of 84 posts
Re: In-Flight Entertainment Challenge
#82Earlier quoted context omitted.
FAANGs have UX Engineers whos main goal is to typically prototype ideas. The code they write is not always submitted to source. So a UXD works with a UXE to make ideas happen quickly to vet them out.
Interesting, do those roles pay well? I’ve never heard of a role that would fit me at a FAANG and didn’t think it existed but that’s exactly what I do.
Re: In-Flight Entertainment Challenge
#83Earlier quoted context omitted.
Idk, those two terms are as different to me as URL vs URI. Searching it will yield a long explanation about the differences, but IRL people will use them interchangeably.
People do this a lot, but those of us who actually do the work instead of sit and talk in meetings about the work know that there is a huge difference between writing React components (UI) and designing flows in Figma (UX). It's just outsiders who say UI/UX as if they are the same thing.
Writing React components -- frontend engineers (no "UI").
Designing flows -- UX (no separation on UXD/UXE, and they actually have to sit in meetings a lot, to figure out what users want and how others do it).
And we use "UI" for folks in design industry: images, colors, fonts, look-and-feel, modern fashion, transition animations, etc. Maybe some nice interactivity that UX didn't care enough for.
Re: In-Flight Entertainment Challenge
#84Earlier quoted context omitted.
I mostly agree, but I still use the in-seat screen for the flight map.
You could have that available on the inflight wifi would work fine, local image/tile server to a certain level globally, cache the area under the projected flightpath before departure, then update the cache as time goes on. Some planes have external cameras too which can be interesting - you could have those on the inflight wifi too.