Also the phrase "know your audience". No sense in casting pearls before the swine.
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").
That's a management thumbprint on the deliverable.
But when it's embedded software on physical devices where the business will have to incur cost in order to ship and hit those users, I can absolutely see why management would do the same thing as what all of the competitors are doing.
...it's the software frameworks. A new screen size. A different color depth. A bug when the graphics library is upgraded for antialiasing. Etc.
Also, devices already sold often get updates, so it's not even just about future devices.
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.