Return-Path: X-Original-To: apmail-flex-dev-archive@www.apache.org Delivered-To: apmail-flex-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C9C5E1036E for ; Sun, 14 Jul 2013 21:18:43 +0000 (UTC) Received: (qmail 25380 invoked by uid 500); 14 Jul 2013 21:18:43 -0000 Delivered-To: apmail-flex-dev-archive@flex.apache.org Received: (qmail 25355 invoked by uid 500); 14 Jul 2013 21:18:43 -0000 Mailing-List: contact dev-help@flex.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@flex.apache.org Delivered-To: mailing list dev@flex.apache.org Received: (qmail 25347 invoked by uid 99); 14 Jul 2013 21:18:43 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 14 Jul 2013 21:18:43 +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 omuppi1@gmail.com designates 209.85.212.44 as permitted sender) Received: from [209.85.212.44] (HELO mail-vb0-f44.google.com) (209.85.212.44) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 14 Jul 2013 21:18:37 +0000 Received: by mail-vb0-f44.google.com with SMTP id e15so2707823vbg.31 for ; Sun, 14 Jul 2013 14:18:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=jUvDdwFWXp78df/nGpG1dO/IFfjPrepGV0Wfpeq5M3g=; b=A56x9Q2S8sJu7F6HM81GHa4uMwowXZbi8bVBVtRSBYVIdrGJAislNulyrnvMQEDlNG ZzjdGxG+rymLBBxf6mCASr9jGBrZiXN45kINuCWq7YTFgpXx2jfG0rc1SfNWPIxDrWl6 ZBjbPTamH66wnG5cxQ9WgNP+kzPb7bmWxilk4v9WK0BHJS9W/eQgWXcdhtYErv7fhPAL BlVRPtDgbOy+9xy3s/5/2mngkuw5CZpxm6OHRLvqxVpszb/ngGbFJKEOgBwU0sUPKqTp ce+UvBSxeBi166iC3x39WKO4746DQpxztpD36975eBiBni0XeYVplesfDAtYX8LEXp2f Em9g== MIME-Version: 1.0 X-Received: by 10.58.97.167 with SMTP id eb7mr27443675veb.45.1373836696538; Sun, 14 Jul 2013 14:18:16 -0700 (PDT) Sender: omuppi1@gmail.com Received: by 10.58.251.7 with HTTP; Sun, 14 Jul 2013 14:18:16 -0700 (PDT) Received: by 10.58.251.7 with HTTP; Sun, 14 Jul 2013 14:18:16 -0700 (PDT) In-Reply-To: References: Date: Sun, 14 Jul 2013 14:18:16 -0700 X-Google-Sender-Auth: TpEiHDHcZ1NGkeVWMPSTClgmOFg Message-ID: Subject: Re: Flex as a Mobile Framework From: OmPrakash Muppirala To: dev@flex.apache.org Content-Type: multipart/alternative; boundary=089e013c5b0a46d5bf04e17f487a X-Virus-Checked: Checked by ClamAV on apache.org --089e013c5b0a46d5bf04e17f487a Content-Type: text/plain; charset=ISO-8859-1 On Jul 14, 2013 11:56 AM, "Ejaz Asghar" wrote: > > Hi, I'm a flex designer & developer and I'm now a days developing mobile > apps with Flex. Before i start my story, I'd like to share my experience > with other components > 1- Feathers UI, Feather is good for games, but when it comes to apps, > Feathers is not what we need, especially when it is not available on > playbook and BB10 will always stay behind Stage3D based improvements > 2- MadComponents (One man army rich component set with no updated > documentation/examples like Feathers UI have and most importantly there are > very missing features, a proper skinning support for multidensity apps !) > 3- Flex, a matured framework with a great community, already available > important sets of mobile components, great documentation and examples and > Flex is great for business /data driven apps (free from STag3D) > > Even though our recent app which uses completely skinned UI (bitmaps) works > great on iOS (almost feel native) but it lags on various places (including > animation/list scrolling) on Android. It works great on BB playbook too. > > I'm following the apache community since its start, and still im unable to > see any commitment/improvements on the mobile side, Even i was the one who > listed 2-3 major bugs which proves that (perhaps) we are the only one both > working and relaying heavily on Flex for Mobile for entertainment/business > apps. I am working on multiple Flex mobile projects both at work and for personal projects. I am sure I will run into some of the bugs you have seen. > > I would like to know if you guys have any plans to improve Flex on Android > (fragmented market) and overall provide mobile features (components, > transitions, features etc) to Apache Flex? I can't say that there are any formal plans, but if you have any concrete ideas please start a discussion and build momentum around them. I am sure that I and others here will be able to help out. Around here, anyone with a good idea who is able to get stuff done and generate interest in what they are doing will succeed. > > We tried to move to Starling, but we aint building games neither our > business app requires FeathersUI because unlike Flex it is again driven by > 1 person. On the other hand, flex fulfill our requirements and we want to > know if we can sit back and expect progress on mobile sides. > > Thank you for listening :) Thank you for writing your thoughts out. Please don't get me wrong, but I doubt if anyone can sit back and expect progress to be made by someone else. Everyone scratches their own itches and if you want something strong enough, you have to put some effort into it. Again, building momentum by raising specific issues and getting people to listen to you is key. Thanks, Om --089e013c5b0a46d5bf04e17f487a--