performance - Android cache heavy object for fragment -
where best place cache heavy object (long initiation time) not build each time when enter fragment. i'm thinking keep in activity , pass each time when fragment initialized. sound sensible? there pattern that?
does sound sensible?
yes sensible if same object shares properties different fragments and/or locations.
is there pattern that?
i can't recall specific pattern given scenario there practice coomunicate between activity , fragment. have @ communicating other fragments
Comments
Post a Comment