There's 3 weeks of "2011 Q2" left, which has been the closest we've had to a release date for Flash Player 11.
On 2nd of june Shantanu Narayen, was grilled regarding the performance of the Flash Player and choose not to talk about Molehill.
While the incubator Flash player is running sweet on PC, the lack of an AIR alpha version makes me wonder just how far away a release is.
Customers are asking on a daily basis. It's been great getting our hands on the technology so early, but if it backfires on us developers who
have taken the time to test out the player, I worry that early adopters will shift to "alternative technolgies".
Put another way, if I can't deliver the Molehill experience in Flash soon I'll be forced to adopt Unity for actual projects in the pipeline.
(reading that back sounds like a lame threat, but actually it's just an economic reality. Fending off iPad questions has been difficult enough...)
Is there anyone at Adobe that can share some encouraging words? I WANT TO BELIEVE !
I don't work for Adobe so I can't answer that question.
But I personally would prefer that the beta community had an opportunity to test a release candidate before one was actually released. And that some time be allocated to that.
The worst thing that could happen is that the player is released before it really should have been. I'm sure Steve Jobs would like that.
thank you for bringing up that topic. First let me say: +1.
You spoke my heart.
My company is desperatly looking forward for a release
of AIR 3 since otherwise our developments can't continue.
Is there any way we can get access to a prerelease version?
Please feel free to contact me regarding possibilties.
Anselm Benedikt Hötte
I don't in any way advocate releasing the F11 player before it's tested and I don't believe I've ever suggested that. The Incubator program is a great initiative that Adobe should be given credit for. I do however think Adobe has a duty to inform the community testing it's software as to the release date (weeks, months, a year?). It is important to manage expectations, both from developers and end customers.
Paradoxically interest in Molehill prevents some customers investing in Flash based solutions here and now. I've done my part to promote the new technology ( http://videometry.blogspot.com/ ). Now I must deliver. The only thing I can honestly say to my cutomers is that I don't think there will be a Q2 release, though I would be tickled pink if Adobe proved me wrong in the next 10 days. With a revised release date I wouldn't have to rely on blind speculation.
I realised that you weren't suggesting Adobe release FP11 before it's ready. That was really just a concern of mine - added on top of yours.Didn't mean to conflate the two.
I agree with you. We need a revised release date.
At the risk of reconflating my concerns - unrelated to yours - I'll add the following somewhat tangential commentary:
From a developer's point of view (rather than a manager's point of view) release dates are always estimates so they must be in most cases, off the mark. They are estimates! Guesses. And especially in this case.
Now from a manager's point of view (who must deal with irrational clients with irrational expectations) estimates would be, ideally, not estimates at all but actual guarentees. Indeed some companies hold their developers to their estimates and penalise them if their estimates are off (whether over or under)! Or worse - to satisfy short term client expectations (rather than "push back" on the client) they release something that isn't ready. The manager doesn't get blamed when the thing eventually fails. The developer does. That's the crappy thing about working as a developer.
However a manager's job should not be to manage developers (unless they really are that bad) - but to manage clients - to manage their expectations - to ease clients (when required) into understanding the various hiccups and hurdles on the way to completion.
And especially in this case (being an alpha/beta process with complex issues - multiple graphics cards etc).
A lot is riding on MoleHill, as fas as I can tell, especially with competition from HTML5 - and the whole mobile platform politics going on.
Unity had to navigate through some embarrasing stuff ups with their earlier incarnation of their web browser player (although all is fine now) - but I personally lost client support for Unity (a year or so ago) when it crashed some browsers in it's early incarnations. If that happens with FP11 the situation would be a zillion times worse because it wouldn't be just new sites leveraging the new hardware 3D API that would suffer - but all existing flash sites. A lot of angry developers, customers and the probable death of Flash.
Anyway my tangential point is that even if Adobe release a revised release date (with which I agree they should) one would still need to go back to the client and manage their expectations that even the revised release date is an estimate (at best) and not a guarentee.
Or better - not to engage clients at all - until a working release candidate has been tested as ready to go.
Adobe has engaged us. I wouldn't want to read that as their mistake (or risk) as I prefer to think otherwise: especially since getting access to the alpha/beta process has lot going for it from a developers point of view. But if we (as developers) engage clients (or engage our managers - who engage clients) that is really our "mistake" (or our risk) - that we need to manage. Or at least that is how I would argue it - since I don't want to lose acess to the alpha/beta process.