Does Section 3.3.1 Kill Time Magazine?

A Commenter brought up something very interesting.

First, let’s review Section 3.3.1., which got everyone in an uproar:

3.3.1 — Applications may only use Documented APIs in the manner prescribed by Apple and must not use or call any private APIs. Applications must be originally written in Objective-C, C, C++, or JavaScript as executed by the iPhone OS WebKit engine, and only code written in C, C++, and Objective-C may compile and directly link against the Documented APIs (e.g., Applications that link to Documented APIs through an intermediary translation or compatibility layer or tool are prohibited).

The Commenter stated:

I understand this position, but the shockwave it can start with iPad development can be tooooooo big. imagine Time and other magazines having to code their Apps form the scratch instead of using something like WoodWing plugin for InDesign.

I believe it can be a good position for closed applications, but for magazines? It can be a dangerous road…

And from the WoodWing press release:

“Using newly-developed InDesign plugins, the layouts for any digital magazine can be enriched with interactive multimedia elements like video, slideshows, and dynamic content,” said Erik Schut, President of WoodWing Software.

Does any of that encroach on Apple’s new edict?

One response to “Does Section 3.3.1 Kill Time Magazine?

  1. Hi Mike.
    Thanks for the highlight.

    I’ve been following your blog with close attention because it raises interesting questions about publishing —books and magazines— for the ipad as this is the main reason I can use to defend this new platform.

    Being a publisher, I’m interested in porting or creating content specifically for the iPad and other tablets. One of the main “goals” of the iPad is to save the publishing industry —specially periodical— and this section 3.3.1 may kill all opportunities.

    Big publishers can build up a special team to cope with this eventuality,but smaller publishers —myself included— rely on software such as this plugin or others to easily convert and adapt from our print plates into digital apps…

    Are we cut off even before we could start? I don’t really care about Flash and I agree with Adobes position, but maybe they are too focused in that “war” that end up having collateral damage…

    Keep up your fantastic blog…
    CP