Today the online magazine e-week published an interview with Adobe CTO Kevin Lynch. In that he provided details about Creative Suite 4, Adobe’s work in the Open Source community, the Open Screen Project and our goals for multi-screen content.
“And that’s what we’ve done with AIR on PCs. AIR is a way to deploy an application across OSes. And that’s going great. We’ve had 35 million installs of AIR and we’re hoping for 100 million by the end of the year. Looks like we’re going to make it. And we’re working to bring that same technology to mobile devices. And I think that might be a trend toward a “mobile first” experience, which is really a reversal of how people create applications.
Right now they create largely using large screens and PCs and think about creating stuff that will be displayed on large screens and PCs. And I think that need to change. In the conception of creating that content we need to think about how that will work in the constraints of a mobile device and then maybe how it will work on the big screen. That’s a reversal of how people are thinking and I think it will take a few years for it to happen.
But at Max that’s one of the things we will encourage people to think about — to shift more to this mobile way of thinking and then consider PCs. And that will be a change to our tooling over time. Already we’re starting to do that with things like Device Central in Creative Suite 4 where you can visualize your work across devices. But there’s going to be a lot more to do there.”
As you can see this is a clear signal of our intent for multiple screens including mobile phones, consumer electronics, set-top boxes and of course desktop computers. Innovation for web has, and always will be, the primary driver behind all that we do for the community.
If you haven’t already signed up for MAX and the mobile sessions then now is the time to get on board.
See the badge on the right hand side —>
Our Device Intelligence team have been hard at work! Device profile update number 7 is by far the largest profile update we’ve ever had with some fantastic new additions.
In total there are 261 profiles included, 57 new devices and updates to 204 existing profiles. In total that makes 525 device profiles for you to create content with.
Spread the word, and get it here.
Today we launched the new Adobe Creative Suite 4, which represents a massive step forward for the mobile developer. As part of the Suite, and included with the point products the new Adobe Device Central CS4 includes many new features.
We listened to your feedback and our engineering and product team are rightly very proud of this release. Here are some of the highlights:
- Online device library
- Fully automatic publish/update of device profiles
- Local Library for storing and sharing the profiles that interest you
- Project enabled - ready for working in teams
- Task SDK for automation and for Mobile Packaging
- Send your content by Bluetooth to your device or by FTP
- Record and create test scripts to run across many devices automatically.
- Produce test reports with screen shots automatically
- Video demo recording
- Improved FLV support
- Network traffic sniffing
- Not to forget the nifty Vibrate test
Clearly there are many other improvements and fixes, the integration to After Effects is a huge benefit for mobile video production. I expect that many developers focussing on mobile and devices will consider the new suite a must have upgrade.
Check it out..
Mark
Following immediately after the popular Project Capuchin Webinar Sony Ericsson have now published a set of Capuchin APIs, some really great reference applications and a tutorial to get you started. Get them here.
Project Capuchin:
Is a Java ME API which makes it possible for Java to launch a Flash Lite application on enabled mobile devices using a Java host application. Flash can communicate with the rich APIs provided to Java using standard DataRequest and ExtendedEvent objects. You can being to use the API set from Sony Ericsson and build on them as a community.
As an example the following Java function accepts DataRequest, determines the request type and then returns latitude and longitude strings. The call to complete() calls the waiting onLoad function in the DataRequest object.
The most basic usage the Flash API in Flash looks like this where handleGetGPS is called when onLoad fires.
When using classes there are much better ways to handle DataRequests safely particularly where classes are bound to MovieClip instances such as lists or components. For example I tend to wrap DataRequests in a DataProvider object which handles the scoping and event broadcasts as well as DataRequests.
You can find an example of this DeviceDataProvider wrapper class in my example section, note that coment “CPU and memory efficiency” which is a compiler hack 
Also in the example section is a re-written version of the same class to handle networking and RSS Feeds.
Adobe MAX 2008 is only a few months away and I hope that all of you find the time to attend in San Francisco, Milan or Tokyo.
As part of the event we host the MAX Awards ceremony and I’d like to extend the opportunity for you to nominate individuals or companies. There is a specific category for “Mobility and Devices” and you can also select a region.
Nominations can be for applications, services and experiences that you have seen over the past year.
If you haven’t been to the MAX 2008 site, be sure to have a look at the fantastic sessions.
Latest Comments
RSS