And fragments are a pain, you should use screens and views

mkodekar: what do you mean by screen?

so far i know, fragment should be acceptable for complex view

Tell me about fragment lifecycle

i see, much override functions

See there are lesser in views and screens

how you avoid configuration changes?

There is onSave and on restore for that

it will changes, all you view or screen just implemented in activty

It won't try it

i see

Yeah sure .

@mkodekar why do you say fragments are a pain. I've been using them successfully in fairly large projects without any "pain". IMHO, once you understand them, they are a real pleasure to use. Fragments have a lot of lifecycle events, yes. But you should only care about the ones that you need. Just like activities. I agree there might be some rather good cons. But I fail to see any from your comments

Actually I use fragment for all my project, and that really good.

I don't have any major issues with fragments as well but sometimes building complex ui with fragments becomes a pain, secondly the screen and view architecture certainly is a good alternative for me to do such type of stuffs.