Android lifecycle - are my ideas correct? -


i have read android life cycle in couple of books , official documentation, still unable thoughts in 1 place , understand completely. developing simple app, in use fragments, makes harder, fragments have separate life cycle applications. ask couple of questions:

my application simple logger of various data, user needs enter data , @ it. understand, cycles onpause, onresume, onstop shouldn't worry about? guess real question android life cycle methods essential every application?

is considered bad practice if (fragment vise) calling methods , managing views in oncreateview?

do know simple , yet guides me understand how manage android life cycle correctly?

onresume , onpause important part of lifecycle, , should worry it. whenever user change app another, o goes notifications, or whatever, calling onpause() when goes app, , onresume() when came back. have understand activity may killed, (if system don't have enough resources), in case oncreate called first, if not, jump oncreate , goes onresume(). onstop no necessary, should free resources in onpause() because after onpause call, don't know if activity killed system.

fragments includes same activity lifecycle callbacks plus own callbacks.


Comments

Popular posts from this blog

php - Magento - Deleted Base url key -

javascript - Tooltipster plugin not firing jquery function when button or any click even occur -

java - WrongTypeOfReturnValue exception thrown when unit testing using mockito -