Archive for category Flash Player

An amazing seven years

After what has been an incredible, nearly seven years at Adobe, my number has come up, and so it’s time to move on. This will undoubtedly be the last post on flashmobileblog.com, something that I know hundreds of thousands of you have enjoyed reading for the various insights into Adobe’s Mobile and Devices efforts.

There have been many highlights during my time at the mobile helm, most notably working with my close friend Bill Perry and the growing mobile developer community back in 2007, and of course the incredible Evangelist team led by Ben Forta for the past four years.

Throughout these years together we’ve managed to deliver incredible advances in the Mobile and Devices industry, shipping over a Billion devices with Flash Lite and ultimately bringing Flash Player and AIR to mobile and the Digital Home.  Those achievements, despite having their respective flaws, have enabled some of the most incredible successes ever seen in the mobile content industry.  So while we have seen various people scoff at the cancellation of Flash Player on mobile, at least we tried.

The great news is that Adobe AIR and Flex continue to be wonderful solutions for mobile developers.  It has been incredible to see their transformation into key technologies for the ecosystem and I look forward to seeing them grow in the future.

I’d like to thank you all for being such a great community and supporting my efforts around the world over the years.  I’m really excited to see what the future holds, maybe I’ll have even bigger hair!

Mark

 

 

33 Comments

Steve Jobs

We discovered today that Steve Jobs, one of the most iconic characters in our industry died today.  This is a really sad event that has resonated across the world, on my own Facebook feed I notice that even those of my friends who aren’t “techies” still recognise him and what he stood for.

At Adobe we’re all very saddened to hear this terrible news.  Only yesterday we saw Tim Cook, Apple’s new CEO, deliver the next iPhone and continue the legacy that Steve started and under what we know now to be horrendous difficulty.  This evening Serge, Michael, Piotr and myself were talking about how difficult it would be to present that keynote knowing that their friend was that ill.  Our hats are off to them all.  Their launch of the iPhone 4s was as ever appropriate, “4Steve”.

Here is my favourite Steve Jobs performance.

12 Comments

AIR 3 MapView Native Extension on iOS

For quite some time I’ve had my Radar application out on the Android Market, but one of the major annoyances was that the Google Maps component didn’t work on iOS.  So I could never release the application for that platform, despite many “attempts” to get it working.

With AIR 3 we have new feature called Native Extensions, so I asked one of our great Engineering team called Meet Shah to look at this problem and see if we could expose native UI components within an AIR application.  It turns out that Native Extensions don’t just give us the capability to access APIs like Notifications and Bluetooth, but to actually present native UI within our apps.

The goal is to finish the Native Extension for Android, iOS, Playbook and Desktop platforms and then release the code.  Meet decided to follow the current (deprecated) AS3 API for Flash so that your existing applications will continue to work ongoing, great idea!

 

, , ,

47 Comments

AIR 3 Native Extensions

 

Yesterday we pushed out the first Release Candidate of AIR3 and Flash Player 11, and with that, we’ve outed another new feature of AIR – Native Extensions.  This represents a further opening up of the Flash Platform in that you will finally be able to add new features to the runtime.

History of Native Extensions

The origin of Native Extensions actually goes back all the way to Flash Lite in 2005 and were in fact part of my first engineering project at Adobe.  Back then we had the idea to enable a man machine interface (MMI) to the Flash Lite runtime to enable complete device interfaces to be built in Flash, the Samsung D600/D900, LG Prada, LG Cookie etc were the result of that effort .

The feature later evolved to become part of an OEM runtime called Adobe Mobile Client which was integrated into the BREW MP Platform to enable low-end devices to be produced with advanced interfaces and at much lower cost.

More recently we started working on “StageCraft”, the code name for a project to bring AIR/Flash support to the TV ecosystem.  With the first iteration it was apparent that remote controls were all different, it would be impossible to create a completely consistent API for all of the various pieces of consumer electronics out there.  With that, Native Extensions were reborn and redesigned to enable OEMs to build these custom APIs with ease.

Which brings us to today’s announcement, the opening of the Native Extension feature for all to use.

What are Native Extensions for?

From a high level this feature enables you to:

  • Achieve deeper integration with target devices
  • Incorporate legacy native code in your applications
  • Achieve maximum performance for critical code

As I see it, we built the Native Extension feature originally to enable access to platform or device specific features that don’t form part of the platform today.  Just to give you some context here, we always have debates about adding new features in the runtimes, many are community sourced, some OEM focused and some are internal like Flex etc.  Imagine what happens when the Acrobat, Photoshop and Runtime engineers are free to finish their pet projects :-)

Here are some thoughts on deeper API possibilities for devices today:

  • Notifications
  • Gyroscope
  • Bluetooth
  • Advertising
  • NFC / Payments
  • USB Accessories
  • Media FX/Encoding
  • Text to Speech
  • Contacts
  • Calendar
  • Alarms

Of course let’s not ignore the various possibilities that are now open for desktop developers that want to access provide new interfaces for legacy products.

The benefit is that now customers conversations shouldn’t end with “Can you support XX with AIR on XX platform?”, from this point on the answer will always be yes, assuming you have the technically capability to implement it, or can acquire the extension from someone who can.

Using a Native Extension

From Actionscript, the use of an already built Native Extension couldn’t be simpler.  In the example below you can see the first iteration of the Native Extension that I’ve been creating for Android Tablets with multiple displays.

            import flash.external.ExtensionContext;
            if(!extensionContext)
            {
                extensionContext = ExtensionContext.createExtensionContext("com.android.MultiDisplayInfo", "");
                return extensionContext.call("getInfo","getCount") as int; 
            }

 

Get Started

 

 

 

 

, , , ,

20 Comments

$200k – Adobe AIR App Challenge for Sony Tablets


This summer seems like one for Flash and Mobile, so it’s great to be able to tell you that Sony, one of our long term partners in mobile, are joining the Open Screen Project and will be a platinum sponsor of Adobe MAX in LA.

Today we’re announcing an exciting new Adobe AIR App Challenge for two upcoming Sony Tablet devices.  It’s available to those of you in Germany, Italy, Japan, Spain, UK and USA.

There are lots of prizes ($200,000 USD) available for various categories of applications, as well as early access to the devices and Adobe AIR 3, and a paid-up trip to Adobe MAX for finalists.  All that and more for optimizing your applications for Sony’s new devices.

Let’s take a look at the devices..

Sony Tablet

Both tablets come with Sony quality design and hardware, most importantly, with incredible quality screens.  Each of the devices has a Tegra 2 chipset from NVIDIA and will be “PlayStation Certified”, so expect some of the best quality games seen on the 1st-gen PlayStation and Xperia PLAY smartphone.

The tablets will ship with Flash Player pre-installed, but interestingly the Sony Tablet devices will ship with a new Sony Web browser.  With that, we can expect better performance for Flash and browsing the web, compared to the stock browser.

The Sony Tablet S1 (codename) which has a stunning curved body designed to feel lighter in the hand, like when you fold a magazine.  It comes with a 9.4 inch display, so will be great for Entertainment and reading.  As many of you have heard me say, 10″ screens feel too big for my little Irish hands, so it’ll be interesting to see what it’s like.

Sony Tablet S2 (codename also) is quite different as it comes with two screens.  The underlying technical specs are identical between the devices, but this device is going to be great for building applications that long for unique interfaces that make use of the dual-screens.  I’ve got my sights set on a mixing deck idea, but it’s also going to be a nice way to play games; Battleship anyone?

The Challenge

Adobe and Sony are challenging developers and content publishers to build breakthrough mobile apps optimized for the Sony Tablet S1 and Sony Tablet S2.  We have a panel of some amazing judges, both Sony, Adobe and industry experts picking finalists and winners across four key categories.

Each category has a cash prize of $20,000 USD and promotion on the Sony Tablet devices, with a $100,000 USD Grand Prize awarded for the best overall application.

  • Entertainment
  • Lifestyle and Community
  • Gaming
  • Business and Productivity

Our team of judges will be reviewing applications throughout the process, and will look favourably at applications that span across different platforms.  Maybe your application works on Sony Vaio PCs, or Sony Televisions with GoogleTV?

If you get in early enough, before September 16th, you’ll have the chance to be one of the 10 MAX Award Finalists.  So get in early and you can get a free trip to Adobe MAX in LA!

In addition, $10,000 USD will be awarded for the following applications:

  • Most Innovative Application
  • MAX Public Favorite – awarded by community vote

The top 80 finalists in the contest will get pre-release access to the devices for a 4 week period, the Adobe AIR 3 runtime, and access to the very latest tooling to complete your application.  You’ll be on the leading edge of Flash development and innovation.

Adobe AIR 3 Beta

You will use Adobe AIR 3 Desktop Beta, released soon for the desktop to optimize your applications for both devices.  So you can start to consider how your existing or new applications would make use of the dual screen, be as novel as you like!  (cough, mixing desk, cough)

For the Sony Tablet S2 you will use the upcoming Native Extension feature in AIR 3, one of the most exciting features in the upcoming release of the platform.  Native Extensions give us an easy way to optimize applications for dual screens, that’s because we can now access any API on a host Operating System!

All applications should support both the Sony Tablet S1 and S2.

Key Diary Dates

  • Sept 16: Deadline for MAX Showcase App prizes
  • Oct 1-5: MAX Public Favorite Vote & MAX Showcase App winners attend Adobe MAX
  • Oct 10: Deadline for Entries
  • Nov 11: Final App Submission for Finalists to the Android Market
  • Nov 17: Winners Announced

Submit your app or app project now at airappchallenge.com

 

 

 

 

 

, , , , , ,

12 Comments