You don't need to marvel at anything. Faster frame rates give more fluid operation. More fluid operation typically helps bring a better user experience. If Google didn't believe this, they never would have worked on project butter. Sure it helped, but there is still plenty of room for improvement.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Moving from iOS to Android: Sluggish Apps Normal?
- Thread starter jfrancis04
- Start date
- Sort by reaction score
You don't need to marvel at anything. Faster frame rates give more fluid operation. More fluid operation typically helps bring a better user experience. If Google didn't believe this, they never would have worked on project butter. Sure it helped, but there is still plenty of room for improvement.
You are sounding like Android is very much behind in fluidity compared to iOS but in actual fact newer phones like S3/4/nex/one are very close or equal to the fluidity of iphone5. But like I said many times the advantage of these Android phones is that the UI speed (like scrolling, window/page transition, animation duration) is much faster than iphone5.
I think the slower speed of iphone UI is purposely by design. Look at the terribly slow scrolling speed (and the long window animation duration) has been there since long ago.
You must not have read that last post where I said Project Butter helped.
And don't be so naive to think that Android is just as smooth as iOS.
I have a Nexus 4. It is the only one out of those mentioned that does not run a custom skin. And custom skins really just bog down the system. And I can tell you from personal experience that the Nexus 4 is not as smooth. That is just a fact. There are specific times when it gets close. There are specific times when it gets ridiculously far from being close. Overall it is somewhere in the middle.
Scroll speed and animation speed is personal preference and has nothing to do with how sluggish a phone is.
Funny how some people always find a way to bring up scrolling speed without properly understand Apple's take on the matter. And seriously, people need to stop bringing this up. It has been beaten to death in these forums.
Androids take is simple, just scroll fast. Does Android take into account how many times you have to flick your finger to determine is scrolling speed to increase? No, because Android isn't that smart. When finished reading an article and you want to go to the top to navigate the site menu to find another article, is there a one-tap way to do so on Android? No, because it isn't that smart.
Let's say for example there is a huge article you are reading. Just to show how big, on Android let's say it takes 50 hard flicks to get to the bottom. Now on iOS, by the 5th flick, scroll speed dramatically starts to increase. At about flick 8, it actually scrolls a certain percentage of the webpage as opposed to a static scroll amount. For example, a hard flick on iOS might first cover the length of the screen and ignore how long the page is. But after a few more flicks, it ignores how big the screen is and pays attention to how long the webpage is because it understands you are trying to get further down. So back to the example, the first flick or two might only move down ~.5% of the page. Meaning you would need 200 static iOS flicks to scroll to the bottom of what would normally take Android 50. But at about flick 8, it ignores everything but page length. And then scrolls go at about 15-25% of the entire page per flick. Meaning it would take significantly less amount of flicks to get to the bottom.
Here is a video to demonstrate how after a few flicks, iOS recognizes what you are trying to do and makes adjustments accordingly:
Android won't make adjustments accordingly. And then what happens when you want to go back to the top? Another 50 flicks on Android. iOS? 1 tap.
Not to mention the first few flicks on iOS make more sense for, you know, actually reading an article. An average flick on Android can take you way too far, causing you to scroll back up and decreasing overall user experience.
But again, this is personal preference. And if you prefer to use more flicks, then go right ahead. I won't debate you on your preference.
No, Google is not admitting that the apps is better, Google said that the new design ion iOS is "better" than the old Android one
I don't know where you see frames dropping ion Evernote.
Maybe you should read what I said again. I said that Google admitted to it offering a better experience. I went back and read that article again and stick to my original wording.
On the screen.
Maybe you should read what they said because they didn't said that the iOS experience is better and, by the way, even if the experience was better, what they said has nothing to do with sluginesh or
Where? I don't see any frame dropping
Google clearly said maps for iOS is better than for Android. If it is better, they are clearly saying it offers a better user experience. How can an app be better on one platform while at the same time offer an inferior user experience? Answer: it can't.
Clearly my point in using that link was to support a better user experience. Please read closer next time.
Some peoples are more sensitive to slower frame rates. But even so, this can depend on how much content is in a note or what you are viewing when you slide over to the menu. For example, viewing a simple text only note and then swiping to view the menu is much smoother than showing a card view of multiple notes and then swiping to the menu. But again, some people's eyes may not be able to see it.
Google clearly says that the new design is better, nothing more, they don't say that the user experience is better. Because it isn't, there is no integration with the OS like on Android.
And they don't say that the app is better on iOS, by the way.
Please, read closer next time because Google didn't said that there was a better experience
Ah, the problem is people that can't see those frames dropping. I see
There's a difference between frame RATE and frame DELAY. iOS never runs a frame delay less than 33ms. Android OS pushes 50ms or higher, even on the current flagship models. This is the primary reason for faster processors in Android devices.....they are required to drive the OS.
Frame delay is noticeable to the naked eye.
Frame delay is noticeable to the naked eye.
The first time you scroll down your notes list its very noticiable, afterwards its better but still dropping frames. This is on my HTC One and Lg OG Pro. On my iPhone 5, it is smooth from the get go.
82 notes right now, almost all of them with pictures. i can't see any frame dropping
You have lost all credibility. Here is a direct quote:
"Google admits that its even better than Google Maps for Android phones"
Oh ya I forgot, saying an app is better on one platform means that at the same time the entire user experience is actually worse
Come on man, thinking isn't hard.
Ah, the problem is people that can't see those frames dropping. I see
----------
Don't waste your time. Many people have come on this thread to tell their experiences of how android apps are sluggish compared to iOS apps. He just refuses to take off his blinders. Even if 100 more people were to come on this thread saying the same thing, he would still stick to his blind android bias.
They are talking about the design, not the whole app. The one losing credibility is you when you're cutting the quote.
Oh ya I forgot, saying an app is better on one platform means that at the same time the entire user experience is actually worse
Come on man, thinking isn't hard.
Yes, it is not hard, you just have to read the quote and understand it and they are not saying that the WHOLE app is better.
Android bias my ass. Do you want that I record a video to show that there is no frame dropping?
So no, I don't want to waste your time and mine, do you believe that? Perfect, have a nice day and suffer you sluggish applications
You're right, it isn't hard to read. Too bad not everyone sees that
They clearly are talking about the app as a whole. Let's not forget that at the time of the article, doing turn by turn navigation inside Google Maps for Android forced you to use Navigation Beta, which is a total piece of crap. On iOS, it was all built into the Maps app, making it a seamless process. Google wasn't just talking about colors when they said Maps for iOS was better, they were talking about the whole app.
Yes. If you say there is no frame dropping when multiple other people say there is, you are clearly in the minority. So you are going to have to show some evidence to backup your claim.
At least now you finally admit apps are sluggish on Android
----------
And here you are never posting a single link or video or source yourself. Hmmmm.....
You're right, it isn't hard to read. Too bad not everyone sees that
They clearly are talking about the app as a whole.
If you want to believe it, as I said, I don't want to waste the time. Pogue's quote is clear, I was no the one cutting it.
You and other poster makes "multiple other people"? And the ones making the claim are the ones that have to proof it.
Still expecting just one video of those frame droppings in Evernote.
But as I said, I don't want to waste my time or your time, this is the last answer. Have a nice day
Nor were you the one to understand the full quote in relation to the state of both apps at the time. Funny how you didn't respond to my argument explaining the shortcomings of the Android version of the app. Convenient
http://dictionary.reference.com/browse/multiple?s=t
You're making the claim there is no lag. Just by witnesses the side that says there is lag has more evidence. If you are going to claim there is no lag, prove it. Otherwise your words are just fluff.
Shot it in 60fps. Then I slowed it down to 24 for those watching that might not be able to tell the difference right away. Plus I am not sure of the max fps YouTube supports, so slowing it down to 24 made sense. And of course viewing this in real life makes it more apparent than on a computer monitor. But still, it is quite obvious.
Bear in mind, this is just evernote. And this is only one part of the UI. Things like this happen around various parts of the UI in various apps. And as someone already said, this doesn't happen on their iPhone 5.
So where is your proof?
I hope you have a nice day too. But if you decide to come back and continue this discussion, make sure to come back with something that actually supports your claim.
Yeah. Nice going. You call that scrolling when all I see is a white screen during scrolling and the scroll just do a discrete jump down the page (and not actual scrolling). This discrete jump is useless if you want to locate where you are. Add to that uselessness is that you just see a white screen while scrolling.
To make it scroll like that you need to do a 5-8 fast flips. On Android I can do a fast scroll with just one-long flip. I can vary the scroll speed based on how I flip the screen. There is no need to do the fast 5-8 flips before the scroll do this discrete jump down the page. btw: I try to do this with my thumb on the Iphone5 and it is so darn difficult to do. Try it.
In other words, iOS scrolling is still slow and not up to the level provided by Android.
You clearly didn't understand one bit of what was going on.
It was the MR home page at the time. I zoomed in and went off to the side to simulate a longer page. There is no content on the side of the page, that is why it is white. If it couldn't keep it, it would give a checkerboard pattern. Try doing some research first. And it is not jumping. It is still scrolling, just much much faster. But I see how some people can get it confused with a jump, even though it is quite clear to me it is just a super-fast scroll.
One long flip like you are talking about makes no sense for, you know, actually reading what is on the page. And if it takes 50 flips to get to the bottom, the way iOS does it is much faster. Plus you can get to the top with 1 tap. Android would require another 50 flicks.
HAHAHAHAHAHAHAHAHA!!!!!!!!!!!
What do you think this video was?????????
In other words, Android scrolling doesn't understand what the user is trying to accomplish. Scrolling will take you past what you want to read, doesn't speed up in an extremely large article, and provides no easy way to get to the top. iOS, however, does all of the above much better.
Nope. Your super-fast scroll is a discrete jump. I tried this on my ipad. while it is doing the discrete jump the page is blank/white. Only when you finger stops the text came back.
I give it to you that iOS one tap to go to the top is something good to have. But then most of the time we are reading from top to bottom. In Android, depending on the apps/browsers you can have scrollbar / go scroll to top/bottom. A scroll bar is much more useful.
HAHAHAHAHAHAHAHAHA!!!!!!!!!!!
What do you think this video was?????????
Why don't you read properly.
Do it one-handed holding the phone with your thumb. How many times do you encounter such extremely large article where you need to do that kind of useless discrete jump? Very seldom. I am talking normal use like coming to this thread in the forum. It is so slow scrolling to the post you want on iOS.
I would do a fresh install and see.
----------
The point is that apple seems to be the slowest to refresh.
Yup.
Its not doing that for me.
Exactly why it makes more sense to not scroll at a super fast speed... Because if we are reading from top to bottom and we scroll down, we miss content.
Not seeing that in the default AOSP browser that comes with a Nexus 4, Chrome, Chrome beta, or Dolphin.
And on iOS the tap to top is a system wide thing. It isn't dependent on the various different ways each individual app wants to do it. Bringing more consistency.
Just did it with my thumb only and it worked just fine.Why don't you read properly.
Normal use is reading through an article without missing content when scrolling and then having an easy way to get back to the menu at the top. Android fails at both of those.
Normal use is not having a scrolling race to see who can get to the bottom fastest. And if you did want to race who could get to the bottom or the top fastest, iOS would win half the time with a single tap
Anyways, we have gotten extremely off topic from sluggish apps. But hey, if you want to debate something as subjective and pointless as scroll speed, I'm down. Besides, you really only have one thing going for you, which is that on Android it is faster. iOS? Tap to top, scroll speed makes more sense for reading, and dynamic scroll speeds based on what the user is trying to accomplish. 1 - 3 mate.
Just went to store on saturday and tested both the HTC One and the GS4. Both phones, but especially the GS4, showed lags and stutters sometimes, e.g. pulling down the notification bar, opening random apps or scrolling through the app drawer. No biggie, but it IS there! It just isn't as smooth as an iPhone, period.
Some people just don't see it (be happy if you don't!), but me and many other people experience that lag, stutter, dropped frames or whatever you call it.
It's not that the phone is bad, you just have to live with it (android).
Some people just don't see it (be happy if you don't!), but me and many other people experience that lag, stutter, dropped frames or whatever you call it.
It's not that the phone is bad, you just have to live with it (android).