Mobile Layout

[bilbosax <wa...@comcast.net>]

In my AIR desktop version of my application, I have the main app and two
components.  The first component shows a google map and the second is a
photo viewer.  It is possible that my employer is going to pick up my
application and if that is the case, it is possible that 125,000 people will
use my application daily.  The trouble for mobile is with the map.  If each
employee only looked up 5 map locations a day, which will likely be much
more than that, that would be over a half a million google map loads per
day.  This will cost almost a million dollars/year.  So for the desktop, I
created the map in a component that slides on and off the screen, but it is
never closed or recycled.  This way, I can open a google map once, and keep
it open the entire time a user is using the app.  This can get the cost down
to only $100,000 a year - much better.

But on mobile, I don't know how this will work.  I guess I could do it the
same as on the desktop and just keep a component open that slides on and off
the screen.  But I wanted to ask about the views layout on a mobile
application.  Each time you move in and out of a view, is the content
removed and garbage collected, or will it stay open and active until you
close the app? If the data and components are kept active as you move in and
out of view, I could just use the View layout of a mobile application,
otherwise, I will have to create custom components and keep them active
myself.  Thanks for any information.



--
View this message in context: http://apache-flex-users.2333346.n4.nabble.com/Mobile-Layout-tp13718.html
Sent from the Apache Flex Users mailing list archive at Nabble.com.