Comment by crazygringo
3 days ago
This is why specifications are important, and why design is important.
The reality is that we have certain conventions that are immediately understandable, and that too much visual complexity results in confusion rather than clarity.
If the sky is hazy white when I expect it to be blue, I'm confused as to whether it's the sky or if the map is still loading. It's adding cognitive complexity for no reason. Stars similarly serve no functional purpose at night.
What you built sounds great for an actual planetary view like Google Earth. And it sounds fun to build. But it's an anti-feature for a navigation view. When you're navigating, simplicity and clarity are paramount. Not realism.
> This is why specifications are important, and why design is important.
Also the phrase "know your audience". No sense in casting pearls before the swine.
Though sometimes the higher ups might not be the same as (or understand) the actual audience.
In this case the higher ups may have been confused due to, say, looking at the app while indoors (and from the perspective of "let's judge this developer's work"), while the actual users would see it in a vehicle alongside the real sky (and from the perspective of "let's see how easy this is to match up with reality").
Ah, I see the confusion. You think the users are the dev's audience! /s
2 replies →
Also, any fanciness you add in your product is something you need to then maintain. Even after the developer that built it leaves the company.
It takes thousands of years for the stars to have changed positions in a noticeable way, and my best guess is that the customers will not use their car GPS for so long that this will bother them.
Very funny, but in case you're serious, it's not the stars changing...
...it's the software frameworks. A new screen size. A different color depth. A bug when the graphics library is upgraded for antialiasing. Etc.
2 replies →
Oh come now. You are being no fun.