...

Blog

Shows this week at Rash Pixel

Three new releases over on Rash Pixel this week.

the naked marketers—Ep 46: Megan Who?
Dane and I try to make sense of life without Megan, who quit us this week. She stuck it out with our inanity for 46 episodes over two years and finally could take it no more. Apparently, her shiny new role with the Cause Marketing Forum is just too compelling a mistress for us to compete anymore. She has such a great presence on these shows and while we both congratulate her on the change in her role and exciting opportunities ahead, she will be sorely missed for her good spirit, great humor, and unending patience. That, and she’s dead to us, of course.

Movies We Like—“When Harry Met Sally…”
Predictably, we love this movie. And so far, I think I can fairly say that this is a movie about which no one I have ever actually met has not loved as well. It’s the quiet funny kid… the kid that’s just too charming to pick on, even though every now and again he might eat a booger. It’s also our very special New Year episode, because of all the New Year redux scenes in it. It’s a theme thing. Seriously, go listen to this show and make sure to comment on Facebook to share your thoughts with me and Andy.

Taking Control—Ep 49: How to make an organizing goal
Finally Nikki gets to something that has bugged me for years: resolutions suck. They don’t actually deal with the positive change you want to achieve in your life, they deal with the things you invariably hate about yourself for some reason or another. Better to create goals, structure them as projects with milestones, and give yourself a plan to achieve them. Fine to use the New Year season to set some new goals and reset priorities, but once you get good at setting organizing goals, you’ll want to do this all year round.

Dumb as a marketing differentiator

Ina Fried - Adobe’s Mobile Flash Pullback Puts Android Tablet Makers in Tough Spot

RIM rep on their strategy going forward with regard to Flash:

“As an Adobe source code licensee, we will continue to work on and release our own implementations. RIM remains committed to delivering an uncompromised Web browsing experience to our customers, including native support for Adobe Flash Player on our BlackBerry PlayBook tablet (similar to a desktop PC browser), as well as HTML5 support on both our BlackBerry smartphone and PlayBook browsers,” RIM said in a statement to AllThingsD. “In fact, we are pleased that Adobe will focus more efforts on the opportunities that HTML5 presents for our developers, and shares our commitment to HTML5 as we discussed together at DevCon Americas.”

Seriously.

Gruber on conflating Flash benefits

‘Opponents’:

It’s not that iOS’s popularity for web browsing led to the death of mobile Flash; it’s that the lack of Flash — and the resulting overall improvement to speed, responsiveness, and battery life — led to the popularity of iOS for web browsing.

(Via Daring Fireball)

Yeah, that’s about how it shakes out. And that, I’d wager, is what’s going to do in Flash on the desktop too. I know I’m not shy about discussing the improvements in stability and battery life on my own laptop since I disabled Flash on my system. I say the same to my non-technical parents, who also have now moved to a Flash-free lifestyle. If my parents can do it, anyone can.

Marco Arment celebrating the end of Mobile Flash

→ Adobe ends mobile Flash development:

This isn’t just the death of mobile Flash: it’s a confirmation from Adobe that all Flash is on its way out.

Adobe’s management is also being pragmatic about its priorities. Rather than fight a losing battle for a particular runtime, Adobe can focus on what it does best: makingtools for creative professionals.

Whether those tools build Flash or HTML apps shouldn’t matter: they should build what creative professionals need to build, and these days, that’s native mobile apps and HTML5 web apps.

(Via Marco.org)

Adobe finally kills Flash player development for mobile

From Danny Winokur, VP & GM, Interactive Development at Adobe:

However, HTML5 is now universally supported on major mobile devices, in some cases exclusively. This makes HTML5 the best solution for creating and deploying content in the browser across mobile platforms. We are excited about this, and will continue our work with key players in the HTML community, including Google, Apple, Microsoft and RIM, to drive HTML5 innovation they can use to advance their mobile browsers.

I love Adobe. After Apple, Adobe is the company I count on for having allowed me to quit my job to freelance. I have a very large, soft spot in my professional heart for Adobe. What I know of Adobe is that when they focus, they turn out amazing and powerful tools that we could never have imagined before. With each substantive iteration of Creative Suite and each product announcement, I’m filled with this sort of breathless anticipation at discovering what new wonders will enable me to deliver a vision for my clients they never would have expected.

That’s where Adobe excels. They create the most powerful tools in the world for allowing creatives to do incredible work. Sometimes I get the feeling that Adobe doesn’t know that.

Of course, the real news:

Our future work with Flash on mobile devices will be focused on enabling Flash developers to package native apps with Adobe AIR for all the major app stores. We will no longer continue to develop Flash Player in the browser to work with new mobile device configurations (chipset, browser, OS version, etc.) following the upcoming release of Flash Player 11.1 for Android and BlackBerry PlayBook.

It’s about time.

This is the march of technology talking on one hand, timing on the other. The problem with Flash has always been that it’s devilishly tricky to optimize in low-power environments. Had mobile chips come out with the horsepower required for Flash and a cold fusion reactor in the first place, we wouldn’t have been having discussions about Flash on mobile. It would likely have been the dominant mobile media delivery mechanism. Unfortunately for Adobe, that reality only exists in some other timeline, which is about to be frozen in amber.

The upside is huge here. Getting Flash on mobile out of the picture means that Adobe will get to the yeoman’s work of creating the tools for creatives to build incredible things on all mobile platforms and focus on telling stories rather than graceful degradation for the mobile experience.

One last interesting point:

We are already working on Flash Player 12 and a new round of exciting features which we expect to again advance what is possible for delivering high definition entertainment experiences. We will continue to leverage our experience with Flash to accelerate our work with the W3C and WebKit to bring similar capabilities to HTML5 as quickly as possible, just as we have done with CSS Shaders. And, we will design new features in Flash for a smooth transition to HTML5 as the standards evolve so developers can confidently invest knowing their skills will continue to be leveraged.

That Flash will continue as a dominant media distribution package for big media is sort of a no brainer to me. But this last bit seems to me as a realistic assessment of progress in HTML5 for general rich media user experience. That Adobe is continuing to contribute and migrate underlying Flash tools says to me that they’re both aware that their future is in building tools for a standard which they do not control, and that we’re not there yet. I think they’re right on both counts, but this is the first time I’ve heard nuance from Adobe that there is a future out there on the horizon for deprecating the Flash desktop experience in favor of HTML5. It’s right there, in the subtext: if we bring all these rich media capabilities to HTML5, who’s going to be left developing in Flash?

On the upside, seems like the religious arguments about the future of Flash on mobile have dialed back their fervor. And Adobe’s doing a pretty good job of planting the seeds of transformation here as optimistically as they can.