Mark Doherty :

Darren :
It would be nice to see a general improvement to the Adobe Mobile Packager interface, like the ability to save projects, etc. It feels like a bare-bones application right now, and while it works great at what it does, there’s room for improvement. Perhaps some sort of integration with the Flash IDE (e.g. publishing a Flash Lite movie instead of just testing it builds the packages specified).
But to a certain extent, that’s just window dressing. I think Dale hit the nail on the head and reiterate how great it would be to see the Distributable Player be an acceptable packaging solution on Ovi. If the Distributable Player can’t be used on (what I hope will be) a major avenue of Flash Lite content distribution, then that’s a big strike against it.
(And fixing the input text field behaviour would be fantastic, too! Props to Alessandro for pointing that one out!)
Darren

Bare bones?? Where’s the love?!

Hey, AMP is great at what it does (and mea culpa: you can save projects – it’d been a while since I used it), it’s just that it could do it better! For example, I can publish a sis, or I can publish a cab, but I can’t do both at once? Why not? I realize that in theory packaging is the final step that only should need to happen once, so it doesn’t seem like this would be a big workflow issue. But I’ve found that I’ll end up going through the package/install/test/uninstall/package loop a few times (to check the icon appearance or for other issues), so the easier this process is, the better it would be (for me personally, at least).

1. In order to ensure that the Flash platform becomes all pervasive on the mobile phone rather than a ragbag of old different incompatible versions – Improve/Repair your relationship with Nokia, Sony Ericcson, Samsung, Blackberry and Motorola + others so that they all support FlashLite 3.1 distributable player cleanly across as many phones as possible. You have different issues with each company and you can see “cracks” appearing between Adobe and Nokia by looking at the latest Nokia presentations on their developer forum. Get your CEO to listen.

2. Release Date for FlashLite 3.1 distributable player on as many mobiles as possible and make this the baseline for all suppliers shipping Flash Lite embedded on phones.

3. A proper roadmap to convince developers that Adobe actually have a platform plan which makes sense, otherwise Qt, J2ME and Nokia’s WRT look more attactive options as phone support is better standardised.

Darren :

It would be nice to see a general improvement to the Adobe Mobile Packager interface, like the ability to save projects, etc. It feels like a bare-bones application right now, and while it works great at what it does, there’s room for improvement. Perhaps some sort of integration with the Flash IDE (e.g. publishing a Flash Lite movie instead of just testing it builds the packages specified).

But to a certain extent, that’s just window dressing. I think Dale hit the nail on the head and reiterate how great it would be to see the Distributable Player be an acceptable packaging solution on Ovi. If the Distributable Player can’t be used on (what I hope will be) a major avenue of Flash Lite content distribution, then that’s a big strike against it.

(And fixing the input text field behaviour would be fantastic, too! Props to Alessandro for pointing that one out!)

Darren

Bare bones?? Where’s the love?!

Benefit Mobile Solutions :

The ability to open the main swf file from a custom path. For example, If i have my app files at e:/others/ the launcher app can tell fl3.1 to open e:/others/myapp.swf not the swf inside the launcher app path.

Unfortunately that would constitute a security breach

Lots of very correct interesting points made here.

I think the wishlist I have is difficult in that it requires cooperation between Adobe and hardware manufacturers. But the issues below are currently the biggest issues we have with our projects. Usability and player penetration are no longer problematic.

From my perspective the top 3 would be:

1. Work on fixing discoverability issues across all target platforms. Joe the Plumber can’t necessarily be taught that he has to find his newly downloaded app in the Gallery/Memory Card/Images folder.
2. Don’t lose focus on the platforms that make up the largest market segments, ie. Series 40 and the small Walkman phones. Don’t lose sight of the fact that a very large percentage of the installed base may never be able run AIR for Mobile.
3. Create a common platform service API independent of platform. Right now – being totally inept at Java – I can’t even create a Quit button using Capuchin and some of the published code samples for Nokia Platform Services don’t work.

Mads

For example: Nokia, SE, Opera, to name just a few that are known in US and EMEA regions (APAC and esp Japan use Flash Lite heavily in the browser, for instance).

So, it depends on your device, region, and sometimes even operator (it’s not uncommon for some to disable functionality) …

It seems more and more OEMs are adopting Flash inside their respective mobile and device browsers, however …except lame duck, Apple for instance … for perfectly logical business reasons, of course).