Thanks Tomislav for valuable input Best Regards Sumudu
On Sat, Jan 11, 2014 at 12:10 AM, Tomislav Pokrajcic <[email protected]>wrote: > Hi Sumudu, > initially we were concerned about the performance because of requirements > for complex UI, but at the end it was better than we hoped for. > I believe that native app would perform better, but our customer (another > software company) didn't have any performance remarks. > We implemented many details regarding performance tuning but the most > important thing was to avoid MXML as much as you can in your components. > All item renderers should be pure AS3. > > Smooth view transitions impact user perception of app quality a lot and > here are some tricks we did to get there. > First we decided to cache some components. > For example, most of our views had 2 or 3 main components and we would > store references to these components in a singleton to avoid destroying > them after exiting the view. > So, when user enters the view for the second time we didn't have to wait > for these components to raise from nothing but instead injected them > 'prepared' into the view. > We didn't cache everything, just several complex components that take long > to initialize. It's also possible to cache entire views but we didn't take > that route. > > It can make a big difference if you organize the code execution workflow > in a way that data loading/preparing operations don't interfere with view > switching transitions. > For example, on button click we would usually show a preloader, then load > data for the next view (our controllers are cached) and when everything is > ready then activate transition that now runs uninterrupted. > Have in mind that user doesn't actually expect to get new screen > immediately because he/she knows that some data has to be loaded and that > it takes time. Preloader keeps them calm while waiting that second. > This way transition doesn't start right away, but it's executed without > glitches and it leaves good impression. > > I don't have any special link/guideline to share, we got all ideas from > 5-6 years of experience with Flex. > Making complex mobile apps that behave well is possible, but it takes some > extra effort to get there. > > Cheers, > > Tomislav > > > > On 10.1.2014. 5:32, Sumudu Chinthaka wrote: > >> Hi Tomislav >> >> unfortunately we couldn't try your application and it seems UI is pretty >> complex too. how about the app performance do you feel any slowness >> comparing to native IOS application, if there is a delay is it a >> acceptable >> delay. >> >> also i would like to know what are the memory optimization/performance >> tuning guild lines did you follow, any document or link you could share >> would be great >> >> Thanks >> Sumudu >> >> >> >> >> On Fri, Jan 10, 2014 at 3:07 AM, Tomislav Pokrajcic <[email protected] >> >wrote: >> >> My company recently completed a business tablet app for a customer. Here >>> you can find some screenshots: >>> http://www.boardpoint.eu/en/tablet.aspx >>> >>> It has pretty complex UI, many custom components, real time data sync... >>> There were some tweaks and cheats in the process, but in the end we >>> produced a pretty smooth interface. >>> Works for iPads and Androids. >>> Unfortunately it's not available for public download because it's >>> distributed over protected enterprise app store. >>> >>> Regards, >>> >>> Tomislav >>> >>> -- >>> www.binaria.hr >>> >>> >>> >>> On 9.1.2014. 15:29, Scott Matheson wrote: >>> >>> Hi >>>> Has anyone got a good example of a Flex written iPad app, on the is >>>> iStore that I can pull down and show my manager as an example of the >>>> art of >>>> the possible ? >>>> >>>> I still get the old, well it may be possible but it will not be as good >>>> as a Objective C app >>>> >>>> Scott >>>> >>>> >>>> ________________________________ >>>> >>>> Disclaimer: This electronic mail and any attachments are confidential >>>> and >>>> may be privileged. If you are not the intended recipient, please notify >>>> the >>>> sender immediately by replying to this email, and destroy all copies of >>>> this email and any attachments. Thank you. >>>> >>>> >>>> >>> > >
