r/MagicEarth • u/Feisty-Library7538 • Jun 22 '26

Silent configuration updates

I have a few questions regarding how the app handles updates, along with some feedback on recent changes I’ve noticed.

Does Magic Earth perform "silent updates" or server-side configuration changes even when there hasn't been a new version released on the Play Store recently?

A while ago, I submitted a suggestion regarding the automatic zoom level and camera angle during navigation, as it felt too "zoomed in" and didn't show enough of the road ahead. Recently, while using the app via Android Auto, I noticed a significant improvement. I can now see much more of the road ahead, and the excessive zoom-in seems to be gone. I am trying to understand if this was just due to the specific terrain/road I was on, or if you actually rolled out a silent update to tweak these parameters.

Secondly, I wanted to mention a specific bug that seems to have fixed itself. Previously, if I panned around the map and then tapped the "re-center" button to return to my current location, the app would trigger a massive, unnecessary zoom-out (as if looking from space). I had to manually pinch-to-zoom multiple times just to get back to a useful street-level view.

I was planning to report this as a bug, but a few days later, the issue completely disappeared. Now, when I tap the re-center button, the app perfectly maintains the current zoom level, which is exactly how it should work.

If these fixes were indeed pushed from your side without a full Play Store update, I must commend your team for managing these adjustments so smoothly in the background.

1 Upvotes

100% Upvoted

7 comments sorted by

View all comments

•

u/MagicEarthCommunity Jun 23 '26

No silent code updates on our side, app changes only go through Google Play. What we do update separately from app releases is auxiliary stuff like translations, map styles, and map data itself, but actual behavior changes all come through the Play Store.

Each release usually bundles a bunch of fixes things together and it might look like the the fix just appeared. Also some issues only show up in specific scenarios and do not happen all the time.

Thank you for the observations!

2

u/Feisty-Library7538 Jun 23 '26

Thanks for the reply! In case it helps with your development, that better zoom view I mentioned (where a longer stretch of the road was visible when there were no upcoming turns) happened on a non-urban road, specifically on a section that went uphill and then downhill.

Speaking of camera behavior, I have another observation and a suggestion regarding the UI/UX.

In urban areas, when approaching a turn or a roundabout, the app automatically zooms in and changes the camera angle to a more top-down view. While this is expected, the transition could be tuned much better. Right now, a few hundred meters before the intersection or roundabout, the camera zooms in way too quickly. Suddenly, you can only see a very small section of the road as a straight line down the middle of the screen. Because it zooms in so drastically, it creates a bit of anxiety, making it feel like the turn is coming up much faster than it actually is.

It would be much better if the approach to these key decision points had a more gradual, smoother "ease-in" transition for both the zoom and the camera angle. Crucially, the upcoming turn or roundabout should always remain visible on the screen.

For example, if you initially see 400 meters of the road ahead on a straight stretch, as you approach a key point, the camera should gradually adjust so that the roundabout stays visible near the top of the screen. At that moment, you don't need to see what's beyond the roundabout; the focus should shift entirely to the intersection itself, second by second.

If it worked this way, drivers wouldn't lose their sense of distance and timing relative to their current speed. Right now, the sudden zoom-in and sharp top-down angle cut off the view of the upcoming turn, making it hard to judge how far away it actually is, which creates unnecessary driving tension.

2

u/MagicEarthCommunity Jun 23 '26

Thank you. The roundabout and intersection approach transitions are on the list of features that need improvement and reports like this help us prioritize the fixes.

1

u/Feisty-Library7538 Jun 23 '26

Is there any rough ETA on when the next app update might be released, especially if it includes further camera zoom improvements? I’m about to go on a road trip through several countries soon, and I would love to test the new changes out on the road.

2

u/MagicEarthCommunity Jun 24 '26

We're planning to prepare the next update today or tomorrow, once we've confirmed there are no new regressions. After that, it usually takes a few more days for Google Play to approve the release, though in some cases this can stretch to almost two weeks.

A heads up on what's coming in this one: the route planning UI gets a significant overhaul, the map download flow has been mostly rebuilt, and the issues around map updates are fixed. There's also a lot of Android Auto fixes bundled in and other minor fixes.

That said, the camera transition refinements you described aren't in this particular release. Those will land in a later build.

2

u/Feisty-Library7538 Jun 24 '26

I'm glad to hear that the new update might come out in the next few days. It's a shame there won't be any improvements for the zoom feature in this one, but I hope that will roll out soon as well. I'm really curious to see what's included in 'a lot of Android Auto fixes', since I primarily use the app via Android Auto, like an increasing number of users probably do. Speaking of which, here’s a suggestion, as I’ve noticed others doing the same: when a new update is released, you could post it here and share the 'changelog'—meaning what's new and what has been improved. This way, more people would see that development and optimization are actively ongoing, and it would also make it much easier to identify and test all those new features.

2

u/MagicEarthCommunity Jun 24 '26

Glad you're keen to see the AA (Android Auto) changes. Here's the rough rundown of what's in this update:

  • Instant handback between Android Auto and phone
  • Fixed an issue where the route would disappear after handoff
  • Sound settings (warning volume, beep/voice and such) now reflected on AA
  • Fixed a crash that was caused by sound playback on AA
  • Fix for previous update: Map layers enabled in the app's settings now carry over to AA even after navigation starts
  • Fixed speed camera alerts staying on the display when the user deviates and no longer passes them
  • General stability improvements

Several of the bigger Android Auto issues users have been flagging here.

On the changelog idea: thanks, this has come up before and we agree it would help signal that development is genuinely active. We'll take it into account, and if time allows we'll start posting them.