The article says that rich content isn't the source of the bloat:
Each full page is a giant image – there are actually two images for each page: one for landscape and one for portrait mode.
If the app stored text as, you know, text then presumably it would require significantly less space. Eliminating the portrait/landscape duplication would also save space.
That or the descriptions of the app are somewhat overcritical.
Even so, if Adobe did want to throw a laughing cog at Apple via their clients, they're doing Wired a disservice, and frankly, that's terribly insane. They just couldn't throw a high profile partner/client under the bridge just to amuse some tantric executive war between Adobe and Apple.
Lastly, although hard to believe a company fairly technology agnostic as Wired would use their financial line (their money making product) as a way to experiment with dissing a technology giant, let's pretend Wired and Adobe both wanted to stick it to Apple for the 3.1.3 clause. They would be simply shooting themselves in the foot, as their customer is who really loses out here, not Apple.
It just make any sense at all, although I will give you that it's a romantic idea. More likely, they rushed a replacement implementation, since they couldn't use Adobe's compiler. Conde Naste clearly upholds Wired to the same deadlines as their other high end properties, and want to see a ROI for all the R&D they've had, perhaps. Becausethis certainly looks like a rushed implementation, or at a minimum, one done by amateurs.
You can build an iPhone OS app that contains all of the data to be rendered by a Webkit UIWebView. Apps built on Phonegap use this technique, for example. It's possible to build a pre-packaged app that's basically a glorified Web browser with all of the content embedded inside as resources. The interactive elements could then have been made with JavaScript, rather than pre-rendered.
While I think Flash (the authoring tool) is a bloated mess, it's light years ahead of anything that exists for creating interactive content with HTML5/CSS/Javascript. There are no good tools for generating something like the Wired app in HTML5.
I don't agree the tools are non-existent, but to the "wwhat do you gain from that" part: distributing a packaged "Web site in an app" has significant App Store and UI benefits over a paywalled Web site.
Ain't nobody talking about downloading the thing as you read it.
All of the content for an HTML 5 version could be stored offline, you'd be gaining massive size savings - which on limited mobile devices (not just the iPad) would be huge gains.
I'm actually considering writing an open source objective-c framework for specifically this purpose, I would hate for Adobe to get a foothold in this and kill the promise.
An easy jumping off point for cross compatibility with Android, Windows, and OS X?
However, the real reason it is 500MB is the same reason the paper copy is so many pages...
It is about 50% advertising.
- less control over interaction
- less snappy animation
- approval of some bloggers
- easier ports to fictive multi-touch tablets on other platforms
(Yeah, I understand your question was retorical, but I couldn't resist)
I make cocoa apps, and I'm pretty sure that the 'native' part of the app — the part of it that could be ditched by linking to WebKit instead – weighs in way under 10 megs
Why didn't Wired use HTML5?
1) a) it was built by Adobe who build it on Flash to begin with, b) the tools just aren't there yet. c) because of #2.
2) Why is the app 500MB? Because all the rich content (images, movies, audio) are bundled into the app so you do not need an internet connection to view it. I think we can all agree that downloading a "magazine" before you leave the house, then finding you can't view most of it, would be an uber fail.
If the app had been based on HTML5 it would have been a 'mare to cache all of the content locally for offline viewing. HTML5 does offer local storage, but not in a way that would allow sites to cache 500MB of content. And even if they could, do you really want to wait 20 minutes for that Pixar feature to download over 3G?
I suppose you could have created a native app with everything bundled locally and a UIWebView for rendering the HTML5 content, but really what do you gain from that?