In the meantime, update your address books:

Redub LLC
151 W.19th St, 5th Fl
New York, NY 10011
O: 212.255.6290
F: 888.531.8858


View Larger Map

Tweet This Post

If you’re a web or Flash developer (or a concerned publisher), you’re probably wondering “Why is Apple shutting out Adobe? Why isn’t it allowing Flash on the iPad?” Some publishers have already gambled and hitched their horses to Adobe AIR in the hopes that it will allow them to transition to app-building without making a dramatic shift to hiring Objective C and Cocoa developers. With their recent release of the iPhone OS 4.0 SDK beta, in section 3.3.1 of the iPhone Developer Program License Agreement, they explicitly state “that applications must be written in Objective-C, C, C++, or JavaScript as executed by the iPhone OS WebKit engine” (see @gruber’s excellent redux). This strikes directly at the heart of Adobe’s CS5 release which promised the ability to author in an environment many designer/developers were familiar and comfortable with (Flash/Flex) and export to iPhone or iPad applications, something many people (myself included) were very excited about.

What happened? Why did Apple shut this route to app-ification down?

My take on it is that now that Apple’s gotten deep into the mobile computing business, it’s started to care a lot more about how applications are written, because how they’re written seriously affects how well and efficiently they run. And mobile computing is all about ruthless efficiency, like engineering for space travel. If your application (and then your phone) grinds to a halt because of some unidentifiable memory leak (I’m using “memory leak” here as a euphemism for “poorly written code that makes a program run sub-optimally”), and you need to make an emergency phone call, you’re ditching your iPhone right then and there.

The same “memory leak” might be happening right now on an application you’re running on your desktop (either a Flash SWF in your browser or some other desktop application) but because of the huge RAM and memory sizes of most desktop computers, these leaks take a lot longer to become noticeable. (I’m talking out of my ass here but correct me if I’m wrong.)

Another way to look at it is that when you use a “meta-framework” to author in Flash/Flex and export to iPhone, you’re depending on Adobe to create the proper hooks to tie into Apple’s Touch APIs, and the assumption with these meta-frameworks is that you don’t really care what’s going on under the Apple hood; you just want to “drive the car” so to speak. What Apple is saying, to put it bluntly, is “You need to care about what’s going on under the hood if you want to make apps for the iPhone/iPad.”

As @gruber points out, “We’re still in the early days of the transition from the PC era to the mobile era,” and it looks like Apple is taking this opportunity to enforce standards and best practices on their mobile devices by a) making app developers use their tools and APIs and b) strict gatekeeping during the app submission process before releasing them to the App store. It’s tough love, and some people are going to get hurt. Some people will have their feelings hurt (Flash developers), and others are going to have their businesses hurt (MonoTouch, Adobe, and it’s also looking like Flurry/PinchMedia and other analytics companies are going to get shut out).

Big Questions: What about Google/Android? Will Apple’s benevolent dictatorship win out over a messy but open democracy?

For more reading on this subject, check these excellent articles:

• Apple’s prohibition of Flash-built apps in iPhone 4.0 related to multitasking from AppleInsider
• Daring Fireball on Why Apple changed Section 331
• Steven Johnson’s column on How Apple has rethought a gospel of the web

Tweet This Post

My presentation on the future of reading, long-form journalism and publishing (plus some screenshots of the Redub Reader) in 20 slides (20 seconds each slide) at Pecha Kucha NY, 9/14/09 at Solar1.

Thanks to Ayagwa for filming and editing!

Tweet This Post

There are still features we are hinting at but that we’re still working on adding, like annotation (which is the biggie). We’re laying in the sharing stuff now.

Oh, and as far as search engine optimization is concerned, we’re working on a solution for that. Right now all of the content is stored as XML in a database (modeled on WordPress). We just have to build a front-end for it that spiders can crawl all over.

And feedback is welcome!

Tweet This Post

I used to doubt the hype about Twitter, until last week. When Alex and Adam posted a tweet (at 5am no less) looking for a presentation whiz to visualize balance sheets and the economic situation, I almost fell out of my chair, because as it happened, when they made their amazing episode on This American Life back in February called “Bad Bank”, I had started doodling (first on paper, then moved to the computer) as they were talking in an effort to try to understand what was going on visually. OK, I admit, I listened to it about 5 times, and eventually I ended up with a series of slides that I posted to them last week (I think it was 7am) via Twitter.

Turns out they were making a live presentation in LA a week later, and with Ryan Lauer, who was also a huge fan of the show (we listen to it in the office), we expanded it into a longer slideshow in Keynote ‘09, which, by the way, kicks serious ass once you get to know how to use it. Anyways, I cannot tell you how amazing this experience was working with them and how much fun we had working on this. They are my heroes.

Plus, I’ve gotten an invaluable crash course in economics and I can’t wait to do more with them. They actually make this incredibly complex and crucial stuff understandable in human terms, which is exactly what Redub does with creative visualizations of data.

UPDATE: Entire webcast embedded above! Link from Planet Money’s blog.

PS — if you’re wondering what “WTFJHTOE” stands for, check the webcast

Tweet This Post