How I: Solve low memory issues with onSaveInstance; fragments; and Bundles Video Lecture | "How I" by Google Developers - IT & Software

hi my name is Edith
I work as software specialist at current
technology mobile applications team I
gurantee JP obviously which are most
popular banking applications are our
team's products there are lots of
different devices in the market with
lots of different capabilities because
of Pinkie Bank which provides service to
all of our customers and some of the
devices have some low memory issues do
not keep activities options which is
lying on the developer options gives us
the opportunity of simulating these long
memory issues today I'm gonna tell you
the most important and common low memory
issue which is your activities being
recreated the system may destroy your
activity if had stopped or hasn't been
used for a long time or the foreground
activity need more resources so the
system will destroy your activity to
recall the memory let's think about
money transfer transaction there are
lots of selections in the page
Sandra count brass selection if there is
a lot women issue happens on the user
selection page let's say that a cow
selection user selects the account and
turn back to the main page and because
of long memory all the selections all
the fields will be cleared if your
activity stops because of a low memory
issue then on same instant state method
will be caught by the system and you can
save all your data what you want in this
method and after being recreated your
activity the only store instance state
method will be called so you can restore
back all your data in here and the
system uses
value objects in this solution
the official solution wasn't enough in
our case because being recreated
offer activity minsters the users start
transaction from a start and select all
the selections
again and again of course we could use
on say vistas state method and official
solution
but it about means high-cost service
simulated problem and develop another
solution if you use one activity for
whole transaction and a fragment for
each related page then your activity
won't be recreated and you will complete
your transaction in one activity if you
want to solve the foreground/background
cases none you can use your confidence
custom components on say visa methods
activities on sales method and you can
save all the data but if you think about
your users uses another application or
at another transaction it won't be a
real problem to lose the data which is
not using fun one last issue I want to
talk about is our bundle object which
you use for saving data and passing data
between activities bundle object has a
maximum storage limit and if you have to
keep board on this maximum limit then
you have to develop some other solutions
in that case you want to use your
device's local storage maybe but it
won't be a safe solution our solution is
in that case is use a hash map that will
allow with your application I talked
about the common law memory issue and
how we solve it my advice to all Android
developers select this option before
submission and control their
applications they don't have to solve
every low memory issue but at least they
could know which user which problems the
users have five feet
you