Hi all, I am going to start working on application whose target is to collect user input (textual and media) and send it to a web service. It would be nice to use a wizard-like approach for user interface since the chunks of user input data can be nicely grouped together and logically split over a couple of screens.
Here's the question, how would you design activities for such kind of app? I think of the following two approaches, could you please see which of them is better in your opinion? 1. A single Activity for the whole bunch of wizard screens. Using this approach I would create an instance variable in the activity to hold data model used by wizard screens, which will be consecutively populated with user input data from step to step and eventually sent to the web service. While this approach seems to be well it does not allow to use 2. Activity per wizard screen. This one seems to be superior because it follows the guidelines of working with activities and tasks, but I do not know how to share the model between wizard steps there. What is best practice of designing things like this? Would it be nice to store the model in a persistent storage, use Intents to pass the data back and forth, use of IPC? I am looking forward for your advices, Thanks! Pavlo --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
