I am tasked with building an app that does not have a fixed screen order. When started the app will contact a server an get a list of actions to perform. So one launch could be screen 1 - screen 5 - screen 7 next time screen 3 - screen 5 - screen 9
I tested a simple app that does that; my Main activity starts the needed activity and that activity returns to the main activity, which starts the next needed activity. In other words, all activities return to the Main activity which then determines which activity to start next. It seems to work fine, but I have read that Activities should only be used for UI, my Main activity had no UI, it just controlled which activity happened next. So should I be using a different approach? I am brand new to Android, but have decades of Java experience. In case it makes a difference, I am using AS 3.0.1 Thanks -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. To post to this group, send email to android-developers@googlegroups.com. Visit this group at https://groups.google.com/group/android-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/android-developers/488583e8-68d6-42a2-890d-8d98568f75d7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
