Earlier quoted context omitted.
>>It was a bit of both. The original iPhone wasn't a hardware revolution, but it was an OS revolution. I disagree. Only a very small minority cares about operating systems and revolutionizing them. What the iPhone revolutionized was user experience. For the first time, someone invented a device that was easy to understand, fun to use, and seemingly limitless in capability. When Steve went on stage and showed it off,…
I don't think we're actually disagreeing. I'm not saying that the average iPhone user has remarked "Core Graphics is great! It makes my phone so responsive and fast!". I'd be very surprised if any lay iOS user has ever said that ;) But the idea is the level of interactivity and the UX around iPhone would have been impossible without the platform Apple first built for OSX. Many other manufacturers at the time had UX a…
iOS 7: Catch me if you can
111–120 of 131 posts
Re: iOS 7: Catch me if you can
#112Earlier quoted context omitted.
It was a bit of both. The original iPhone wasn't a hardware revolution, but it was an OS revolution. It was the first time anyone put an OS on a phone that had a blazing fast graphics layer. Touchscreen phones existed before then, but because of platform performance, was always of the "poke, wait, stuff magically appears, poke, wait, stuff magically appears..." model. Apple didn't just invent new usage models, they i…
>>It was a bit of both. The original iPhone wasn't a hardware revolution, but it was an OS revolution. I disagree. Only a very small minority cares about operating systems and revolutionizing them. What the iPhone revolutionized was user experience. For the first time, someone invented a device that was easy to understand, fun to use, and seemingly limitless in capability. When Steve went on stage and showed it off,…
Interesting that it wasn't the first time an Apple CEO went on stage and showed off a pocket tablet, and the minds of everyone in the audience went into overdrive to start imagining all the possible things they could do with it.
What the Newton, in 1993, revolutionized was user experience. For the first time, someone invented a device that was easy to understand, fun to use, and seemingly limitless in capability. Except it wasn't limitless. The public mind was thrilled with the concept, embraced the wonderous new platform, and got...egg freckles? http://fortunebrainstormtech.files.wordpress.com/2011/10/db9... The OS, hardware, UI, UX, all were revolutionary - and some revolutions fail. Steve killed it promptly upon his return, and I imagine nonetheless studied it a great deal, taking some 13 years between unveilings to get it right, making sure the engaged public didn't overwhelm the second attempt.
Re: iOS 7: Catch me if you can
#113Earlier quoted context omitted.
60fps scrolling? A semi-decent animation framework for developers? Low audio latency and good power management? Pretty much all the advantages Apple has from their decade of experience of developing OS X frameworks?
> 60fps scrolling? It's pretty easy to make UITableView's chug if you do something stupid when populating cells as well. > A semi-decent animation framework for developers? The property animation system introduced in Honeycomb and backported to what, 2.2? works very nicely. > Low audio latency Audio has been an issue on Android. I've not delved into it myself but this is certainly something that only seems recently f…
Only the chuginess comes standard with Android.
The property animation system introduced in Honeycomb and backported to what, 2.2? works very nicely.
It's not really close to CA.
>Not sure this warrants calling the platform far behind though.
If you casually dismiss everything else too, of course not.
>I'm not sure what you're getting at here.
Like Android apps allowed to run rampant in the bg, draining the batteries pronto -- a complaint you hear all the time, and of which you can also find some measurements.
Re: iOS 7: Catch me if you can
#114If this article is accurate - and that iOS 7 has so much eyecandy that it will only work on the latest high end hardware - does this mean that a low end budget iPhone is off the table? Or is this Apple's way of segmenting a high end version of the OS and then a version with all the eyecandy disabled for the cheap iPhone? It's interesting that Apple and Google seem to be going in polar opposite directions right now -…
Don't believe everything you read in articles before its released. Best not to form opinions on things that aren't in general availability. Apple isn't going for "high end effects" at all with ios7, more fluid effects that overall provide a consistent experience. Can't get too into details due to nda but it isn't nearly as crazy as this article makes it out to be.
It is impressive what they've changed since Ive took over though, very impressive how much of a change they've made actually. It definitely feels designed all the way through.
Re: iOS 7: Catch me if you can
#115Apple doesn't need to introduce delicious eye-candy to its interfaces that nobody needs to hamper web developers...they can just keep neutering the shit out of WebView by keeping it several generations behind the Safari javascript engine.
Re: iOS 7: Catch me if you can
#116Earlier quoted context omitted.
> 60fps scrolling? It's pretty easy to make UITableView's chug if you do something stupid when populating cells as well. > A semi-decent animation framework for developers? The property animation system introduced in Honeycomb and backported to what, 2.2? works very nicely. > Low audio latency Audio has been an issue on Android. I've not delved into it myself but this is certainly something that only seems recently f…
There is a property animation system on Android, but it's woefully lacking when compared to iOS. IIRC it doesn't even support 2.5D transform with a Z axis and variable camera distance (which is useful for perspective transform). On iOS 7 they now have a full rigid-body physics engine built in and comes with a nice high level API for developers to take advantage of.
That's great, but the original comment I was discussing was the claim that "Android is just now getting what iOS had three years ago". iOS 7 is three to six months away, still.
Re: iOS 7: Catch me if you can
#117Why is blur supposed to be computationally intensive? It's very simple mathematically...
Re: iOS 7: Catch me if you can
#118I think this is a good thing, personally. I don't see any reason to write code specifically for iOS any more, when I can, just as easily, declare a similar GUI function in a language that will work on all platforms.
Re: iOS 7: Catch me if you can
#119Re: iOS 7: Catch me if you can
#120Earlier quoted context omitted.
Motion, dynamics, and depth are a hallmark of the Windows Phone Metro experience.
Windows phone metro doesn't include a physics engine. The motions are all tweened. Windows phone metro includes no depth at all, it truly is flat and 2D spatial. Dynamics?