That’s right! We’re moving again, this time, we’re sharing a space with Agnieszka Gasparska of Kiss Me I’m Polish, where we’ll be collaborating and doing more great things together! Stay tuned!
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
<iframe width="425" height="350" frameborder="0" scrolling="no" marginheight="0" marginwidth="0" src="http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=151+W+19th+St,+New+York,+NY+10011&sll=40.68425,-73.964016&sspn=0.011097,0.024226&ie=UTF8&hq=&hnear=151+W+19th+St,+New+York,+10011&z=14&iwloc=A&ll=40.741453,-73.996456&output=embed">></iframe>
View Larger Map
Tweet This Post
I believe Facebook is the only appropriate place for this story:
After not being able to recall some obscure person I had supposedly met in passing some time ago, Aya asked me, "What DO guys remember?" I told her boy brains have extensive areas devoted to electronics and machinery spec details, as well as arcane sports trivia. She then proceeded to ask me "Okay, who won the Super Bowl in ... 1986?" After a moment of mental rummaging through the last vestiges of the guy files of my brain, I somehow summoned up the answer: "Da Bears." She then proceeded to Google verify on Wikipedia (on her iPod Touch) and, lo, and behold! BOOYAKASHA!!!
Scenario
What would a “free market correction” feel like? What if the U.S. Government had allowed AIG, JPMorgan, Bank of America, and Citigroup to collapse? What would have happened if Treasury had chosen not to prop up the nine largest American banks on October 14, 2008? What news reports would have trickled out over Twitter, CNN, CNBC, Fox News? What emails and text messages would we have received from our banks? What would the impact have felt like over a 48 hour period? Subscribers would experience this alternate reality as filtered through Twitter streams, emails, text messages, photographs, video, and podcasts.
Suggestions and ideas are welcome.
Tweet This Post
Disclaimers: I don’t have an iPad yet (I ordered the 3G version), and I’m not officially an iPhone developer in that I haven’t made or sold any apps yet. This does not, however, keep me from posting my opinions on both from the perspective of someone who is looking to create and design apps for the iPhone and iPad.
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:
Tweet This Post
<object width="425" height="256">><param name="movie" value="http://tv.adobe.com/assets//swf/player.swf">/></param><param name="allowFullScreen" value="true">/></param><param name="allowscriptaccess" value="always">/></param><param name="FlashVars" value="fileID=5117&context=145&embeded=true&environment=production">/></param><embed src="http://tv.adobe.com/assets//swf/player.swf" flashvars="fileID=5117&context=145&embeded=true&environment=production" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="425" height="256">></embed></object>
The demos are getting more and more realistic (first Mag+, now this). My initial reax:
- It took a whole team from Adobe partnering with the staff of Wired Magazine to do this demo. The tools aren’t there yet, but publishers, your newsrooms and staff need to look and work like this. Right now, I don’t think they’re geared for this type of production. Yet.
- The question is what hardware is it running on? Can it run on any old tablet that supports multi-touch (not an iPad)? Who makes such a device?
- Does the video have to play full-screen or can it play inline?
- Can you resize the text? I don’t think you can. To me, it looks like they’re taking the assets from the InDesign layout and converting to Flash/Flex/AIR.
- HTML5 and CSS3+ Javascript can’t necessarily pull this off yet. Another big “YET”. jQTouch, I’m waiting…
- I foresee an app per publication, not per issue, which means for books, you’ll buy the Penguin app, and the Knopf app, and pay a subscription fee to get particular chapters of books. In terms of magazines, you’ll buy the Wired app and the GOOD app, e.g., and pay a subscription fee to get particular issues. The question is sharing…
UPDATE: from Wired itself:
The content was created in Adobe InDesign, as is the case for the print magazine, with the same designers adding interactive elements, from photo galleries and video to animations, along with adapting the designs so it looks great in both portrait and landscape orientation. This is a departure from the usual web model, where a different team repurposes magazine content into HTML, unavoidably losing much of the visual context in the process. Wired.com is not a re-purposed version of the magazine, but rather an separately-produced news service.
Read More http://www.wired.com/epicenter/2010/02/the-wired-ipad-app-a-video-demonstration/#ixzz0fjhurJU8
(Putting nose back to grindstone…)
