一般来说,如果你使用“一劳永逸,为许多平台建设”工具,你就有可能放弃利用某些(或所有)装置或平台特征的能力。 实际上,你选择了一种最低的共同标准。 也就是说,你只能向你们提供你所选择的所有平台上的现有平台。

Building a native app -- that is, using Xcode to build an iOS app and using the Android SDK to build an Android app -- gives you complete access to all of a given platform s specific features and capabilities, thereby ensuring the best user experience on each platform.

我现在认为: 土著口供较好,只是因为他们向使用者介绍本土经验——这种经验将使他们熟悉平台的用户。 当你选择使用一个跨平台工具时,你正积极选择让用户在其装置上获得比理想少的经验,但YOU节省了一定时间(可能的话)让你投向市场。 谁是赢家?

In my job, my boss and I had a specific conversation about this. We have native iOS and Android apps, on purpose, because we didn t want to give up platform-specific features. We wanted each app to give the best experience it could on its platform. We specifically agreed that a cross-platform solution was not the way we wanted to go.

Depending on what you are building, Air is a great platform for developing cross-platform mobile applications. Despite recent news that the Flash player is no longer being developed for mobile browsers, the native story remains strong. Plus, having seen native IOS, native Android and Flex development, the Flex platform is much better when it comes to the ease of development. With high-level features like data binding, visual state management, a solid component/skinning model, transitioning model, etc, it is a generation or two ahead of iOS and Android (IMO).

If you are using Flex for mobile (iOS/Android/Playbook), you get a common look/feel across all mobile devices. @MarkGranoff suggested that the user experience is downgraded when using an approach, but I d challenge that.

Although I agree that an out-of-the-box styling of the UI components in Air feels a tad off, I don t recommend that anyone build apps that way anyways. Instead, create an app that looks like your app. There have been many applications that don t conform to the native look/feel of iOS or Android but are still quality from an aesthetic and UX perspective.

对于一个在所有平台上看望/照相的镜子,需要说几句。 我可以告诉大家,......用户确实不关心。 如果看好,感觉好,做他们想要的东西,他们会高兴。

The Flex Mobile SDK uses a lot of the same UI paradigms (especially in the soon-to-be-released version of the SDK) and it is getting better. I wouldn t discredit it. You can save a lot of money and time using something like Flex Mobile.

You can use Flex to compile to AIR for iOS or android. The performance of AIR vs Objective C or Java is significantly slower. The advantage of using AIR is to have one cod base delivered to two platforms. But if you have the know-how, Objective C and Java are better suited to development on their respective platforms. However many successful apps have been launched on iOS and Android using AIR. If you want to know if it would work for you I would seek out those apps in iTunes and Android Market and see how they perform for you. If you app is not a game it will likely work fine. And if you app is a simple game it could also work fine. Also remember there are other multi=platform development tools to choose from, like phone gap, or appcellerator: http://www.appcelerator.com/ http://phonegap.com/

or even Unity 3D: http://unity3d.com/

UPDATE: Since this original answer in Novemer 2011, Adobe has made significant improvements to AIR for iOS and Android. Petformance problems are negligible unless you are doign somethign very instinsive such as large image processing. Likewise, Unity3D has improved a lot too. It s an excellent choice for games that are 2D or 3D.

如果你利用空气开发跨平台信号,你应当注意到以下事实:

(1) 你们没有接触本土特征(但你可以利用土长的延伸来解决这个问题)。

2) performance is slower than native apps (but you can use Starling framework to use GPU power in devices which will increases the performance a lot!)

底线是,使用AS3和Alex/Air SDK建造移动器是你能够想到的最佳解决办法,如果使用饥饿的话,其性能要大大高于本地人。