• Coding

  • Android application design

Hey guys quick question. Recently I started tinkering around with the android sdk ( i'm new to this even to java in general).

When you design an app is it a collection of different activities ? or do you try to limit yourself to a couple of activities. I'm asking this because transferring data from one activity to the other is quite the hassle (intents and whatnot). What the best way to approach the general design structure ?
As you stated, an android app is simply a collection of multiple activities. You should ask yourself if what you're doing is worth to set an activity and if it requires an intent or not.

The level of user interaction with the app can be helpful, if for example you want to launch a popup with some buttons, then using a dialog will be more than enough.

It all depends though.
m0ei wroteIt all depends though.
Do you have a good guide that explains the most appropriate approach to each case (something about several scenarios and best course of action) ?

Also, is there a good class generator that creates classes with their proper imports? some generator where you choose the class name and identifiers, the gets and sets etc.. as well as methods to implement (such as parcelable) and it generates one for you automatically ?