I’m most interested by his take on iPhone apps running on the iPad.

I’m worried, however, of displaying them at this magnified size. They’re blown up to twice their regular size, which wouldn’t be a problem if the iPhone encouraged resolution-independent interface design, but almost all iPhone apps use custom controls that are designed at one size. Blowing them up will create a blurry mess of pixels. I’m curious to see how this problem will be solved – if it will be solved at all, of course.

I’ve had similar thoughts, and wondering how a certain iPhone app I’ve been working on will look blown up.

Read the rest of the iPad UI Roundup on The Cocoia Blog.

Used to be that to drive a car, you, the driver, needed to operate a clutch pedal and gear shifter and manually change gears for the transmission as you accelerated and decelerated. Then came the automatic transmission. With an automatic, the transmission is entirely abstracted away. The clutch is gone. To go faster, you just press harder on the gas pedal.

That’s where Apple is taking computing. A car with an automatic transmission still shifts gears; the driver just doesn’t need to know about it. A computer running iPhone OS still has a hierarchical file system; the user just never sees it.

Gruber shares some other thoughts on the iPad on Daring Fireball.

Read the full post on MobileCrunch for more details.