Dynamic View Object Lifecycle for Mobile App Memory Optimization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Applications running on electronic devices consume excessive memory resources due to multiple views being held simultaneously, leading to inefficient memory usage and slow view switching speeds.
Innovation Solution
A method and apparatus for page view switching that detects user operations to switch between views, destroys the current view, creates a new view object by calling a view controller class, and assigns values to display the target view, utilizing a view information tree to store and restore view status information.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple views are held simultaneously by running applications, then users can switch between different views, but memory resources are consumed excessively
Solution Approach 1:
The patent extracts only the necessary view data from memory when switching between views. Instead of holding all view objects in memory simultaneously, the system retrieves only the required view information from storage when needed, thereby reducing overall memory consumption while maintaining view switching capability
Solution Approach 2:
The patent implements dynamic memory allocation where view objects are created and destroyed based on actual switching needs. Views are dynamically loaded into memory when switched to and destroyed when switched away from, allowing the system to adapt memory usage to current operational requirements rather than statically allocating memory for all possible views
2Speed
If multiple view objects are stored in memory simultaneously, then view switching can be performed quickly, but memory resources are wasted
Solution Approach 1:
The patent performs preliminary preparation by storing view data in a persistent storage format with optimized structures. When switching views, the system retrieves pre-formatted data quickly without needing to maintain all views in memory, achieving fast switching through efficient data retrieval rather than through pre-loading all views into memory
Solution Approach 2:
The patent employs disposable view objects that are created temporarily during view switching and then destroyed. Instead of maintaining expensive long-lived view objects in memory, the system creates lightweight view objects only when needed and immediately destroys them after use, reducing overall memory footprint while maintaining switching functionality
Data Source
AI summary
A method for page view switching is provided. The method includes detecting a view switching operation in an application interface by a user to switch from a current view to a target view. The method also includes destroying the current view corresponding to the view switching operation and creating a view object corresponding to the target view in the view switching operation by calling a view controller class. Further, the method includes assigning values to the view object through a view controller and displaying the view object with the assigned values on the application interface to display the target view to the user.


