flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tianzhen Lin" <tang...@usa.net>
Subject RE: Flex mobile performance
Date Tue, 02 Jul 2013 17:55:28 GMT

No matter what code, JavaScript or ActionScript, they will run slower on a
slower processor, and mobile is slower because the processors are slow.  I
cannot tell you how much I dislike PhoneGap because the UI is much less

As for graphs, I am not sure if you are referring to Flex charts or any
other graph library.  As far as I have done, I helped create an app
streaming 100k's of samples to be plotted on a chart in real time, I had a
smooth user experience.  It requires some optimization on data bound the
chart (not the chart component itself).  This is the same kind of discipline
no matter what technology the app is going to do.  In my case, the
optimization is done through avoiding to plot more dots than needed, and
also implement a collection using vector as the underlying value holder
instead of ArrayCollection.  It requires a few days of tuning, but the end
result is rewarding.

As for your case of loading graph, I used to have tricks to preload other
graphs once the first one is rendered, that would make subsequent switches
go more smoothly.


-----Original Message-----
From: manish sharma [mailto:minisharma17@gmail.com] 
Sent: Tuesday, July 02, 2013 10:28 AM
To: dev@flex.apache.org; jeffry@dot-com-it.com
Cc: OmPrakash Muppirala
Subject: Re: Flex mobile performance

I have created one app for the mobile banking they want to see the graphs
and in the app I have used 6-7 types of graphs. It will take time to load
the graphs and also taking time in switching one graph to another if I want
to go back to previous graph it will load again.

I think the main problem with the same in holding the instance of the
previous screen.

The performance is also the another issue.

Thanks & Regards* **?*
PHONE:   +91 783 899 6886
e-mail:   sharma.manish,gwl@gmail.com /
Join my Network:*http://in.linkedin.com/pub/manish-sharma/23/513/b74*
*P *Please consider the environment and do not print this email unless
absolutely necessary. Please encourage environmental awareness. SAVE

On Tue, Jul 2, 2013 at 1:35 AM, Jeffry Houser <jeffry@dot-com-it.com> wrote:

> On 7/1/2013 1:15 PM, OmPrakash Muppirala wrote:
>> On Mon, Jul 1, 2013 at 10:02 AM, Jonathan Campos 
>> <jonbcampos@gmail.com
>> >wrote:
>>  On Thu, Jun 27, 2013 at 4:43 PM, OmPrakash Muppirala
>>> <bigosmallm@gmail.com>wrote:
>>>  So, when folks are saying that Flex does not perform well on 
>>> mobile, can
>>>> you please post some examples, etc so we can try to figure out what 
>>>> the real problems?  As opposed to sweeping statements like Flex 
>>>> mobile sucks, etc.
>>>>  Just as a quick note. I've spent quite a bit of time over the last 
>>>> 2
>>> years
>>> talking to teams that have had issues with their Flex Mobile apps 
>>> and they all blame Flex for some really bad framerates and they 
>>> "know their code is correct".
>>> The biggest issue I've found is item renderers. Wouldn't you know 
>>> when I switch out their item renderers things seem to move very 
>>> smoothly and almost all their complaints go away. Yes there is still 
>>> that half-second lag for the new View to come in but other than that 
>>> all the performance issues are gone.
>>> J
>>>  I have similar experiences as well.  In fact, badly designed
>> itemrenderers
>> cause lags even in non-Flex iOS and Android apps.  I have seen this 
>> in numerous apps.
>  Even before mobile; the bulk of customer support complaints about the 
> Flextras AutoCompleteComboBox were fixed when I showed customers how 
> to re-write their itemRenderers not to use binding.  All of a sudden 
> the memory leaks--which everyone insisted came from my code--went away.
> --
> Jeffry Houser
> Technical Entrepreneur
> http://www.jeffryhouser.com
> 203-379-0773

View raw message