Return-Path: X-Original-To: apmail-incubator-flex-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-flex-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DDA789D61 for ; Sun, 19 Feb 2012 07:28:36 +0000 (UTC) Received: (qmail 48219 invoked by uid 500); 19 Feb 2012 07:28:36 -0000 Delivered-To: apmail-incubator-flex-dev-archive@incubator.apache.org Received: (qmail 48181 invoked by uid 500); 19 Feb 2012 07:28:36 -0000 Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: flex-dev@incubator.apache.org Delivered-To: mailing list flex-dev@incubator.apache.org Received: (qmail 48173 invoked by uid 99); 19 Feb 2012 07:28:36 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 19 Feb 2012 07:28:36 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of yanlilei64@gmail.com designates 209.85.214.47 as permitted sender) Received: from [209.85.214.47] (HELO mail-bk0-f47.google.com) (209.85.214.47) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 19 Feb 2012 07:28:29 +0000 Received: by bkwq11 with SMTP id q11so4127932bkw.6 for ; Sat, 18 Feb 2012 23:28:08 -0800 (PST) Received-SPF: pass (google.com: domain of yanlilei64@gmail.com designates 10.204.128.202 as permitted sender) client-ip=10.204.128.202; Authentication-Results: mr.google.com; spf=pass (google.com: domain of yanlilei64@gmail.com designates 10.204.128.202 as permitted sender) smtp.mail=yanlilei64@gmail.com; dkim=pass header.i=yanlilei64@gmail.com Received: from mr.google.com ([10.204.128.202]) by 10.204.128.202 with SMTP id l10mr8489687bks.116.1329636488671 (num_hops = 1); Sat, 18 Feb 2012 23:28:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=MbZjKXyztfzwD9NmEibiCKc/eagyn/F/wHc/BZyv0rM=; b=kb2OCUD7cNiyn+2emMtFaxNzvhXHMC19aQjCXltnzndbSvsNMh1MA7tzIOS5FRCVYU Vf+x+rG+pFckDSLTxcrQAmk8VR8firTDxi+WbjR0DIuOGvJZKTSNXfO7oPfGaPD5PC0k fy9z4h0TmyTRVmd5vgMjBvJL6x0z7q6OAomf8= MIME-Version: 1.0 Received: by 10.204.128.202 with SMTP id l10mr6832367bks.116.1329636488584; Sat, 18 Feb 2012 23:28:08 -0800 (PST) Received: by 10.204.130.24 with HTTP; Sat, 18 Feb 2012 23:28:08 -0800 (PST) Date: Sun, 19 Feb 2012 15:28:08 +0800 Message-ID: Subject: AIR Mobile app stability From: James Ong To: flex-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=00151747b49a951d3f04b94c1ed6 --00151747b49a951d3f04b94c1ed6 Content-Type: text/plain; charset=ISO-8859-1 Hi, I wish to find out how reliability and stability using AIR for mobile app as compare to Android and iPhone SDK? On the marketplace and iTune store, almost all of the apps need bugfix or resolve the vulnerabilities, have any of the AIR you created need bugfix updates? --00151747b49a951d3f04b94c1ed6--