a change in the lifecycle status of another component, such as activities and fragments. These components help you produce better- organized, and often lighter-weight code, that is easier to maintain. ϥΠϑαΠΫϧରԠίϯϙʔωϯτɺΞΫςΟϏςΟϑϥάϝϯτͳͲɺଞͷίϯϙʔωϯτͷϥΠϑ αΠΫϧεςʔλεͷมԽʹԠͯ͡ΞΫγϣϯΛ࣮ߦ͠·͢ɻ͜ΕΒͷίϯϙʔωϯτΛ༻͢Δͱɺཧ ͕༰қͰɺΑΓܰྔͳίʔυΛ؆୯ʹ࡞Ͱ͖·͢ɻ
between an AdapterView and the underlying data for that view. The Adapter provides access to the data items. The Adapter is also responsible for making a View for each item in the data set. AdapterΦϒδΣΫτɺAdapterViewͱͦͷϏϡʔͷجʹͳΔσʔλͱͷؒͷϒϦοδͱͯ͠ػೳ͠· ͢ɻΞμϓλσʔλ߲ͷΞΫηεΛఏڙ͠·͢ɻΞμϓλɺσʔληοτͷ֤߲ʹରͯ͠Ϗϡʔ Λ࡞͢Δ͋Γ·͢ɻ JPT։ൃͰ͍͏ UBCMFWJFXͱ͔ʹ͢ EBUBTPVSDFͩ
UI-related data in a lifecycle conscious way. The ViewModel class allows data to survive configuration changes such as screen rotations. The Android framework manages the lifecycles of UI controllers, such as activities and fragments. The framework may decide to destroy or re-create a UI controller in response to certain user actions or device events that are completely out of your control. ViewModelΫϥεɺϥΠϑαΠΫϧΛҙࣝͨ͠ํ๏ͰUIؔ࿈ͷσʔλΛ֨ೲ͓Αͼཧ͢ΔΑ͏ʹઃܭ ͞Ε͍ͯ·͢ɻ ViewModelΫϥεΛ༻͢ΔͱɺσʔλΛը໘ͷճసͳͲͷߏมߋʹ͑Δ͜ͱ͕Ͱ͖ ·͢ɻ 3Y4XJGUͰͬͨͭͩ ͳʂ