views:

110

answers:

4

I am web developer from a year.I have Used PHP,python with client side Js libraries like Jquery,motools, etc.

So if switching to Adobe air will be a good thing ?

  1. If It is strong enough to make decent desktop apps (Eg: music/videos player)?
  2. If apps can be made for Android or iphone OS ?
  3. Can i use Jquery like libraries (i am very used to that syntax) ?
  4. And at last if there will be sufficient work in future for Air developers ?

Sorry if asked already .

+2  A: 

You can't make apps for the iPhone with Adobe Air.

You have to use Objective-C and the Apple API.

ChrisF
+2  A: 

Adobe AIR does allow you to leverage web development skills such as Javascript, HTML and CSS to develop desktop applications. So your skills are transferable in that sense. You can also use Flash (and Actionscript) to develop AIR apps.

Adobe used to offer a way to create iPhone apps from Actionscript using a packager but Apple disallowed that.

There are impressive AIR apps out there, but arguably it hasn't gotten the traction Adobe might have hoped by now, a few years after release.

If I were you I would look at the task or job you need to do and learn the best technology to tackle that, rather than just adopting a platform. But if it's iPhone development, the the Apple way is the only way, and you'll need to learn Objective-C.

Ciaran Archer
A: 

Adobe has posted info on AIR for Android here: http://labs.adobe.com/technologies/air2/android/

adamp
+2  A: 

It's true you can't make an iPhone app directly from the Air SDK, but Air, Mobile Safari and Android are all built on the WebKit browser. That means that there are only a small handful of very major differences between the platforms, so if you write your code to minimize the differences and isolate the differences in separate classes, it's actually pretty easy to keep your code base almost identical across systems.

For example, in Air and Android, you have the option of accessing the local SQLite database through either synchronous or asynchronous methods, with or without transactions. If you aren't used to asynchronous programming, you'll probably want to go with the simpler, more linear synchronous route; and maybe transactions will seem overkill to you. But because Webkit on the iPhone does not support synchronous database calls and everything is done through transactions, you'll be really stuck when it comes to porting your app to the iPhone. But if you write your own Database class so it is asynchronous and transaction based, all you'll have to do is write an interface or bridge to make your class work on all three platforms.

Air has a small mountain of features that you should probably stay away from if you want to port your apps quickly across all platforms. For example, you are allowed to write files to the user's local file system. Stuff like that is simply not allowed on iPhone, so don't expect it to port.

To get your code working on the iPhone and into the App store, there are several webkit wrapper frameworks. The two I know best are PhoneGap and Titanium. Titanium has the added benefit of publishing directly to both Android and iPhone, though I've never actually tried it myself. I do have lots of experience with PhoneGap, and while it is still pretty buggy, it does make it pretty simple to get your apps into the store.

Andrew
very cool PhoneGap looks real money.THX buddy
Arsheep