Loading Profile...
iPhone UI awfully slow
Nearby on iPhone is pretty cool, but the performance of the map operations (moving, zooming, etc.) is awfully slow, not only network-wise, but also slow in terms of UI responsiveness. The built-in Google Maps application is *much* faster.
It would be great if the performance could be optimized in future releases. Right now, it's extremely slow even over fast WiFi connections.
It would be great if the performance could be optimized in future releases. Right now, it's extremely slow even over fast WiFi connections.
I’m frustrated
7
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Hi gkaindl, yes we agree, it is something we need to handle better for sure. In fact, it's our #1 priority right now. Thanks very much for the response.
Also, I personally find the list view mode most useful, don't have to open things one at a time, can really get a feeling for what's around. -
Inappropriate?I agree with OP the Map UI is "dragging I believe this app has potential it is kinda a like a cross between Loopt and Grafito. -
Inappropriate?An update should be coming out over the airwaves in the next couple days, including some performance improvements. Thanks for being patient everyone!
-
Inappropriate?Nearby seems to use the same map as Loopt so should I expect the same performance in moving around the map as in the Loopt application.
-
Inappropriate?I have found it to be much faster in street view. Hybrid is so slow at the moment.
I’m frustrated
-
Inappropriate?I have the 1.2 update and I've set the map view to 'mobile'. The tiles certainly do load more quickly, but the overall responsive of the map interfaces seems to be unchanged, or at least it hasn't improved enough.
If you launch the Maps app bundled with the phone and you start flicking the map around immediately, even before the map loads, you'll notice that the app responds to movement instantaneously. There is almost no lag between the dragging my finger across the screen and the corresponding movement of the grid. Furthermore the movement is always fluid.
This is extremely important in terms of usability, much more so than the time it takes to actually load the map. In comparison, Nearby seems clunky.
It's the nature of these touchscreen based/direct manipulation style interfaces. In the same way that it's tough to tolerate audio/video sync issues or choppy/stuttering audio but we can watch a poor quality image for long periods, or reduced frame rates as long as it is consistent.
I'm sure this is what gkaindl was describing when he said,
> the map operations (moving, zooming, etc.) is awfully slow, not only network-wise, but also slow in terms of UI responsiveness.
I'd also recommend changing the label 'mobile' to something else. The implication of 'mobile' is unclear. Is it just me?
Thanks for your efforts,
Rob1 Comment
Add a comment
This solves the problem
-
Yes agreed, this was just a quick fix that was very simple to get in, the actual interactivity performance is my sole focus this week, starting today at iPhone Dev Camp down in SF. -
Inappropriate?I've now got the update and it does seem to be working much faster. However, I'm confused by this "mobile" label - what's that all about?2 Comments Add a comment
This solves the problem
-
yeah, in the rush of getting that release ready, I just opted for the technical name of the tile set, they are the tiles designed for mobile devices. I'd be glad to consider alternate naming suggestions :)
-
Describing that mode in a word might be tricky. I can't immediately think of a way to say 'this is a street view with smaller tiles' in a word. But it does occur to me that there's a lot of space available on that screen, so you could use some of it to describe either all of the modes or just this one. That would probably solve the problem.
-
Inappropriate?How about something like "light"?
-
Inappropriate?I think "light" is better than "mobile". Mobile is a pretty loaded term in this context, so definitely confusing, and light isn't.
What about "small"? which to me seems a little less good than "light", but light is often used to indicate the removal of features so it might have the wrong connotation.
I still say that if you can use some of the space on that screen for a short explanation of what the different modes are, then that may be a good thing to do, unless you're planning on doing something else with it.
What we're talking about with "mobile" is the street mode with smaller map tiles that load faster and is particularly well-suited for slower connections. So it makes sense that it's hard to reduce that to one word.
EMPLOYEE
EMPLOYEE
