Recent content by anon(5780458)

Android lags and stutters. It may seem smooth out of the box, but one you install apps to make it actually useful, the stuttering begins for no obvious reason. I recently used a relative's new Nexus 5 and was surprised at how smooth it was. It was noticeably smoother than even my iPhone 5S on...

WPF draws its own ugly, substandard, unresponsive controls from scratch like Java. It's only good for pumping out data entry business applications (or making fully skinned non-native, unresponsive applications like iTunes on Windows). Internet Explorer 11 is the gold standard for responsive...

.NET WinForms uses native Win32 API to render buttons, textboxes and some controls. The application code is .NET but the UI is (mostly) native with callbacks to your .NET event handlers.

Java needs to die. Anything Java lags. Java on desktop lags (Eclipse), Java on phones lags worse. No amount of on-paper comparisons will ever make Java applications as a whole run as smooth as native code. Java apps on a top of the line desktop with a native OS like Windows lag. Half of the...

Just take some iOS 5 device and compare the pre-Apple Maps Maps app to the current Google Maps. Take even the current Apple Maps and compare the pinch to zoom and scrolling fluidity to Google Maps.

I'm purely interested in the performance aspect of it. I still use Chrome and Google Maps. The ancient Maps app from iOS 1.0 is smoother than the current Google garbage.

I'm an Android developer. I have many, many test devices at work including the Nexus 5. Core features are unusuably laggy. The default browser is laggy and unresponsive. The default Maps app is EXTREMELY laggy and unresponsive. The Google Maps app is such a substandard pile of garbage that it...

Because the Nexus 5 has the latest OS, fully supported hardware & drivers and unviolated stock Android. Not to mention the raw hardware performance itself is superior. Moreover Android 4.4 is specifically designed to improve performance by lowering the hardware requirements.

The first thing mentioned in The Verge's review of the Nexus 5 is that it lags while scrolling in apps. Non-debatable. All other phones are inferior to the Nexus 5. This is input latency in action.

This line is hilarious. Going from Android is as fast as iOS to Android phones are more responsive than iPhone 5S. LOL. Their methodology was explained in the original source. It's just a blank no-load app used during the tests. 300ms is the under-load latency. Scrolling in Chrome and other...

These tests are all on a blank screen with ZERO CPU usage. When you're running an app or scrolling in the browser the latency on Android spikes to 300ms. iOS remains well below 100ms. The Windows phone while having a higher idle latency, also doesn't become laggier under load. Yes it makes a...

Nope. All devices have 150ms+ input latency. Scientifically verified with a high speed camera and sensors. The lowest latency Android device to date is the Shield which is ~80ms but isn't really a phone. The rest all spike to 150-300ms under load i.e. scrolling. This is what gives it the...

Lies. It's been scientifically verified by several sites and YouTube videos. This includes 150ms of lag on the keyboard. This is present on every existing Android device without exceptions.

Even if the device is hypothetically smooth, all Android devices have 150ms of input latency or worse. Sliding anything drags behind your finger by a visible distance and games are unplayable compared to iOS. You can tap a button and remove your finger from the screen before the button gets...

Because I'm an Android user? It doesn't mean I can't recognise an unresponsive substandard OS compared to other devices I use.