what is the best practices to keep data between activities deathes/restarts for the whole application session?

by Arhimed » Sat, 09 Jan 2010 03:27:44 GMT


Sponsored Links
 We're designing an app that has several activities which are working
in a wizard like way - user should pass from the activity #1 to
activity #5 to get to the final activity (#6).

Since we know an activity can be suddenly terminated by OS on low
memory we used Application class as a static storage for keeping the
data the user inputs on "wizard" activities and other data our app
needs for the whole session.

Unfortunately we've discovered this approach fails - looks like the
Application class instance is also can be killed by OS (this was
specifically discovered on Android 1.6 versus 1.5). Are our
expectations wrong on this approach (we think Application class
instance always lives for the whole app session)?

So the question is - what is the best practices to keep data between
activities deathes/restarts for the whole application session?



Other Threads

1. Default Sound Resources

Hello!

I have a timer application and I was hoping to add the default sound
resources that are available on the device, a la android.R.drawable.*

Are these resources available in any default location? Or shall I just
compile my own set of royalty-free sounds?

Cheers,
Ralph

--~--~---------~--~----~------------~-------~--~----~

2. Typeface affecting TextView marquee?

The default marquee scroll (i.e., three scrolls of text when list item
is selected) in my application's ListView works when the typeface is
set to Typeface.NORMAL but not when set to Typeface.ITALIC.  Is the
marquee scroll implemented for TextViews with the ITALIC typeface?
--~--~---------~--~----~------------~-------~--~----~

3. Sensor issues

4. onDraw issue? -- what's going on?!

5. fill_parent for each child widget?

6. Application install hooks?

7. How can i listen to "Home" key