Adobe insights about creating, delivering and monetizing digital content across platforms and devices

Tag Archives: nexus one

Post navigation

We are pleased to announce that Flash Player 10.1 is now generally available for download on the Android Market for Google™ Nexus One™ phones. Flash Player 10.1 for Android (2.2) is now generally available as of August 16; we had previously released Flash Player 10.1 to partners in June 2010. We expect additional Android devices like the HTC Incredible, Samsung Galaxy S, Motorola Milestone, Droid X, Droid by Motorola, Dell Streak and other mobile platforms to get Flash Player 10.1 over the next few weeks and months. Upgrade paths for devices in market today depend on the specific device, manufacturer, operator and the region. In addition to Android, mobile platforms including webOS, BlackBerry, MeeGo, LiMo, a future version of Windows Phone 7 and others will deliver support for Flash Player 10.1 over the coming months. Many of the new devices are expected to come pre-installed with full Flash.

Adobe Czech Republic in cooperation with youngsters conference JuniorInternet (by Together CZ) opens innovative contest for Czech and Slovak developers to celebrate mobile versions of Flash Player 10.1 and AIR for Android. Enter and win Google Nexus One or Creative Suite 5!

What can you win
1st Place – Google Nexus One (Froyo) + goodies
2nd Place – […]

This is just a short video I made this AM while watching the Adobe Open Source Media Framework (OSMF) launch on Acrobat Connect via my Google Nexus One. I haven’t tested all the features but as for watching, it seemed to perform perfectly. Note there is no plug in to present from the N1 device. For the record, I am on Android 2.2 (FroYo) build with Adobe Flash Player 10.1 (10.1.61.68).

People have asked me which apps I use on my Nexus One quite a few times already so I thought I’d do a blog post on it.
Adobe AIR & Flash Player 10.1
I don’t think this needs too much explanation 😉 Having Flash Player 10.1 in the browser really is a blessing. When breaking news happens I […]

So today is my birthday… ehr… I mean… Today is the start of Google I/O! To celebrate both occasions, I am giving away a Google Nexus One to one of my readers.
I’m sure you all know that Flash Player 10.1 and AIR 2 are coming to mobile devices. In order to win the Google Nexus One […]

February 9th 2010: The last day I used my iPhone. Or: The day I discovered Android. Or: The day I switched to the Google Nexus One. Well… You get the idea.
I was an iPhone user from the moment it came out. Before I continue this post, I want to repeat what I’ve been saying all […]

On Friday I gave the Keynote at Flash Camp Seattle and as part of that keynote I tried to show off Flash Player 10.1 running on Nexus One. Unfortunately the demo didn’t go well and it got some attention around the web. I’ve had a great experience with Flash on my Nexus One but in this case I was running an interim Flash Player build, one I probably should not have installed, and one that I definitely should not have used for any public demos

After I saw Jeff’s blog post, I sat down, upgraded my Flash Player, and went through and tested some of the sites I use on a regular basis. The experience was fantastic. Everything from the Eco Zoo to the NHL video site runs almost flawlessly. While it won’t make up for my mistake at Flash Camp, I recorded a video so people could see an experience that will be much closer to the final experience with Flash Player on Android.

It’s been cool to see so many Flash sites work on mobile devices. However because there is such a variety of Flash content out on the web, it’s important to understand that not all of it is going to run on devices like the Nexus One, both because of lower hardware capabilities of devices and because of user interface design.

A lot of people are clearly interested in Flash Player on mobile devices. It’s a big issue, and I feel terrible that my unpreparedness ended up being a strike against Flash on mobile devices. We’ll be releasing a public version of Flash Player 10.1 at Google I/O and would love to hear how your Flash sites perform. You can always submit issues by using the open Flash Player bug base.

In case you missed it, Adobe was at Web 2.0 Expo in San Francisco this past week discussing and demoing some of the latest Flash Platform technologies running across devices. We showed Flash Player 10.1 and AIR 2 (available in the first half of this year) running on the Google Nexus One, Motorola Droid and Palm Pre, as well as the Dell tablet. Seeing the latest builds of Flash Player and AIR in action you could see firsthand how developers can deliver the same great experiences users expect on their desktops, right on their devices.

I wanted to do something slightly different and build more of a functional application.

I come from a Flex background and so I haven’t spent a lot of time creating ActionScript only projects. And while Flex performs pretty well on Flash Player 10.1, doing an AS3 only project gives it a better shot at running, especially as the application gets more complex. So I went with ActionScript only and created an application that uses the Foursquare API as well as the Geonames database to find and let me check into physical features like mountains, streams, lakes, etc when I’m out hiking and want to still be able to check into Foursquare.

Thoughts on Building for Mobile Flash

As you’ve seen, a lot of Flash content will just work. And because of the AIR for Android packager, a lot of people will just end up building applications and not worry about creating in-browser Flash apps for mobile devices. But I wanted to try it. A few thoughts:

One, the Flex mobile framework can’t come soon enough. I have so much more respect for the old-school Flashers because rolling everything by hand is a pain. And I had it easy because I was dealing with a fixed resolution since I was specifically targeting the Nexus One.

Two, while I didn’t do much in the way of performance tuning, that’s going to be important. These are pretty beefy devices and we’ve done some great optimizations, but for complex Flash content, tuning your code will be central to a good experience.

Three, as Mike Chambers showed, hover content works, but I found it kind of annoying. The way it’s currently set up, the hover event fires after the down event fires. So using SimpleButton the way I normally use it didn’t quite work because the effect was off. I ended up just making the hover state the same as the down state.

Lastly, I was surprised how much just worked. I pulled a LOT of third party content into this application. Keith Peter’s Minimalcomps, the Foursquare AS3 API by Tim Walling, my own AS3 library for Geonames, the Google Maps API, TweenLite, Shannon Hicks OAuthAS3 library – and it all worked just fine. Part of what I wanted to test was how much I could throw at the device and I was pleasantly surprised by how well it all worked even on the beta bits of Flash Player 10.1. So when you target these devices, you’ll be able to use a very similar workflow which I think is important.

To see the application in action, you can check out the video above or test the application in your browser here. You’ll need to have a browser like Firefox 3.6 that supports geolocation and if you check in you’ll be checking in this poor guy. All of the code is available on GitHub and you’re free to do with it what you will. Unfortunately my OAuth implementation was half-assed, so the Foursquare checkin didn’t work, but it works in the browser.

As most of you know, I switched to a Google Nexus One about 7 weeks ago. (Hmm… That reminds me… I really should finish that blog post I’m writing so you can get an idea how I get on with the N1 coming from 3 years of using Apple’s phone). I absolutely love that the […]