Technical method for solving problem of no white screen in page jump based on iOS high-performance loading

Abstract

The invention discloses a technical method for solving the problem of no white screen in page jump based on iOS high-performance loading, and the technical method comprises the following steps: an on-demand loading mechanism: during page jump, loading data according to actual demands, and avoiding excessive preloading and resource waste; the user experience is optimized: page skipping is performed on the premise of ensuring that the first screen data of the page is acquired, so that the white screen or loading phenomenon of the page is avoided, and the user experience is improved; weak network optimization: through an overtime control module, better user experience can be kept under the condition that the network is poor; the method is high in adaptability, and all pages using the jump mode can take effect only by accessing the landing page once; the development cost is low: only page jump API needs to be replaced, and the first screen data of the landing page is ensured to be prepared, and the page does not need to be transformed on a large scale; unnecessary preloading requests are avoided, and consumption of CPU, memory and network flow is reduced.

Description

Technical Field

[0001] The invention relates to a technical method for solving page jump without white screen based on iOS high-performance loading, and belongs to the technical field of application of solving page jump without white screen. Background Art

[0002] In mobile application development, users often encounter white screen or loading when jumping to a page. This is mainly because the page data is obtained from the server, and the client needs to wait for a while before the page content can be displayed. This phenomenon significantly affects the user experience, especially in a slow or weak network environment, where users have to wait longer. Currently, commonly used solutions include optimizing request speed, obtaining data in advance, etc., but these solutions are either too costly or consume too much device resources. The existing optimization methods cannot fully solve the white screen problem when jumping to a page, especially in complex scenarios.

[0003] The existing technologies include the following:

[0004] 1. Reduce request time by optimizing server logic, links, or using cache, HTTP2, etc. However, even so, the average network time is still more than 300ms, and users can clearly feel the delay in page loading time;

[0005] 2. Before the page jumps, the previous page obtains the landing page data in advance. This method requires the modification of a large amount of jump logic, which has high development costs and is prone to waste of memory and traffic because users may not necessarily visit the preloaded page;

[0006] 3. Request data in advance on the previous page and store it in the cache. However, this method is costly for pages with many entrances and complex businesses, and the previous page cannot accurately determine whether it needs to jump to the specified landing page.

[0007] It can be seen that the existing technical methods have the following problems: they increase the burden on the client and fail to fundamentally solve the white screen and loading problems of the page, especially in the case of jump methods such as openURL. Summary of the invention

[0008] In this embodiment, a technical method for solving page jump without white screen based on iOS high-performance loading is provided to solve the problem that the existing technology increases the burden on the client, fails to fundamentally solve the page white screen and loading problems, especially the problem that it cannot be applied under jump methods such as openURL.

[0009] The present invention achieves the above-mentioned purpose through the following technical scheme, which is a technical method for solving the problem of page jump without white screen based on iOS high performance loading. The technical method for solving the problem of page jump without white screen includes the following steps:

[0010] S1. On-demand loading mechanism: when the page jumps, data is loaded according to actual needs to avoid excessive preloading and resource waste;

[0011] S2. Optimize user experience: Redirect pages on the premise that the data on the first screen of the page has been obtained, thereby avoiding page blanks or loading phenomena and improving user experience;

[0012] S3. Weak network optimization: Through the timeout control module, a good user experience can be maintained even in poor network conditions.

[0013] Preferably, in the step (S1), for the data that needs to be loaded from the network, an asynchronous loading method is adopted to avoid blocking the main thread, and a suitable network request library is used to manage network requests and responses. The network request library includes Alamofire and NSURLSession.

[0014] Preferably, the page loading performance is optimized in the step (S1) by using WKWebView, which is a recommended web view component in iOS 8 and later versions. Compared with UIWebView, WKWebView has higher performance and better stability, supports JavaScript interaction and new features of HTML5, and has a refresh rate of up to 60fps, which can provide a smooth user experience.

[0015] Preferably, the correctness of the page jump logic is ensured in the step (S2), including necessary preparation work, which includes loading data, initializing pages, and avoiding null pointer exceptions or memory leaks during the jump process.

[0016] Preferably, in the step (S2), when the page jumps, repeated creation and destruction of view controllers are avoided to reduce memory overhead and improve performance. A cache mechanism may be considered to store commonly used view controller instances.

[0017] Preferably, in the step (S1), when the page jumps, the life cycle of the landing page is first triggered, but the page does not jump immediately. The system first checks whether the first screen data of the landing page has been cached:

[0018] If there is cached data, the page jumps immediately;

[0019] If the business carries landing page data, the page will jump immediately;

[0020] If the above conditions are not met, the system initiates a first-screen data request and executes a page jump after the request is successful.

[0021] Preferably, in the step (S1), under weak network conditions, the timeout module will control the jump process to prevent the user experience from being reduced due to long waiting time. Through the configuration module, the system can dynamically choose whether to enable this solution according to the needs of the specific landing page. This solution is applicable to all jump methods, including complex scenarios such as openURL.

[0022] Preferably, the step (S2) supports multiple redirection methods, not only for conventional redirection, but also for methods such as openURL, to ensure coverage of all scenarios.

[0023] Preferably, in the step (S3), log records are added after the weak network optimization, and log record statements are added in key code segments to record the running status and error information of the program, and the problem is located and a corresponding solution is formulated by analyzing the log records.

[0024] Preferably, after the weak network optimization in step (S3), Xcode is used for debugging, and the running status of the application is monitored by the debugging tool of Xcode, including memory usage, CPU occupancy, etc., and the problem is located by setting breakpoints, checking variable values, etc.

[0025] The beneficial effects of the present invention are as follows: the technical method for solving the problem of page jump without white screen based on iOS high-performance loading in the present invention has strong adaptability: it only needs to be accessed once on the landing page, and all pages using the jump method can take effect;

[0026] Low development cost: You only need to replace the page jump API and ensure that the landing page home screen data is ready, without the need for large-scale transformation of the page;

[0027] On-demand loading: avoid unnecessary preloading requests and reduce the consumption of CPU, memory and network traffic;

[0028] Support multiple redirect methods: not only for regular redirects, but also for openURL and other methods to ensure coverage of all scenarios;

[0029] No white screen, no loading: Under normal network conditions, users will not feel the page loading process, and the experience is smoother. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] Figure 1 The figure is a flow chart of the method of the present invention. DETAILED DESCRIPTION

[0031] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0032] Embodiment 1:

[0033] A technical method for solving the problem of page jump without white screen based on iOS high performance loading, the technical method for solving the problem of page jump without white screen includes the following steps:

[0034] S1. On-demand loading mechanism: when the page jumps, data is loaded according to actual needs to avoid excessive preloading and resource waste;

[0035] S2. Optimize user experience: Redirect pages on the premise that the data on the first screen of the page has been obtained, thereby avoiding page blanks or loading phenomena and improving user experience;

[0036] S3. Weak network optimization: Through the timeout control module, a good user experience can be maintained even in poor network conditions.

[0037] Preferably, in the step (S1), for the data that needs to be loaded from the network, an asynchronous loading method is adopted to avoid blocking the main thread, and a suitable network request library is used to manage network requests and responses. The network request library includes Alamofire and NSURLSession.

[0038] Preferably, the page loading performance is optimized in the step (S1) by using WKWebView, which is a recommended web view component in iOS 8 and later versions. Compared with UIWebView, WKWebView has higher performance and better stability, supports JavaScript interaction and new features of HTML5, and has a refresh rate of up to 60fps, which can provide a smooth user experience.

[0039] Preferably, the correctness of the page jump logic is ensured in the step (S2), including necessary preparation work, which includes loading data, initializing pages, and avoiding null pointer exceptions or memory leaks during the jump process.

[0040] Preferably, in the step (S2), when the page jumps, repeated creation and destruction of view controllers are avoided to reduce memory overhead and improve performance. A cache mechanism may be considered to store commonly used view controller instances.

[0041] Preferably, in the step (S1), when the page jumps, the life cycle of the landing page is first triggered, but the page does not jump immediately. The system first checks whether the first screen data of the landing page has been cached:

[0042] If there is cached data, the page jumps immediately;

[0043] If the business carries landing page data, the page will jump immediately;

[0044] If the above conditions are not met, the system initiates a first-screen data request and executes a page jump after the request is successful.

[0045] Preferably, in the step (S1), under weak network conditions, the timeout module will control the jump process to prevent the user experience from being reduced due to long waiting time. Through the configuration module, the system can dynamically choose whether to enable this solution according to the needs of the specific landing page. This solution is applicable to all jump methods, including complex scenarios such as openURL.

[0046] Preferably, the step (S2) supports multiple redirection methods, not only for conventional redirection, but also for methods such as openURL, to ensure coverage of all scenarios.

[0047] Preferably, in the step (S3), log records are added after the weak network optimization, and log record statements are added in key code segments to record the running status and error information of the program, and the problem is located and a corresponding solution is formulated by analyzing the log records.

[0048] Preferably, after the weak network optimization in step (S3), Xcode is used for debugging, and the running status of the application is monitored by the debugging tool of Xcode, including memory usage, CPU occupancy, etc., and the problem is located by setting breakpoints, checking variable values, etc.

[0049] The above technical method based on iOS high-performance loading to solve the problem of page jump without white screen has strong adaptability: it only needs to be connected once on the landing page, and all pages using this jump method can take effect; low development cost: only need to replace the page jump API, and ensure that the landing page first screen data is prepared, without the need for large-scale transformation of the page; on-demand loading: avoid unnecessary preloading requests, reduce the consumption of CPU, memory and network traffic; support multiple jump methods: not only suitable for regular jumps, but also supports openURL and other methods to ensure coverage of all scenarios; no white screen, no loading: under normal network conditions, users will not feel the page loading process, and the experience will be smoother.

[0050] Embodiment 2:

[0051] A technical method for solving the problem of page jump without white screen based on iOS high performance loading, the technical method for solving the problem of page jump without white screen includes the following steps:

[0052] S1. On-demand loading mechanism: when the page jumps, data is loaded according to actual needs to avoid excessive preloading and resource waste;

[0053] S2. Optimize user experience: Redirect pages on the premise that the data on the first screen of the page has been obtained, thereby avoiding page blanks or loading phenomena and improving user experience;

[0054] S3. Weak network optimization: Through the timeout control module, a good user experience can be maintained even in poor network conditions.

[0055] Preferably, in the step (S1), for the data that needs to be loaded from the network, an asynchronous loading method is adopted to avoid blocking the main thread, and a suitable network request library is used to manage network requests and responses. The network request library includes Alamofire and NSURLSession.

[0056] Preferably, the page loading performance is optimized in the step (S1) by using WKWebView, which is a recommended web view component in iOS 8 and later versions. Compared with UIWebView, WKWebView has higher performance and better stability, supports JavaScript interaction and new features of HTML5, and has a refresh rate of up to 60fps, which can provide a smooth user experience.

[0057] Preferably, the correctness of the page jump logic is ensured in the step (S2), including necessary preparation work, which includes loading data, initializing pages, and avoiding null pointer exceptions or memory leaks during the jump process.

[0058] Preferably, in the step (S2), when the page jumps, repeated creation and destruction of view controllers are avoided to reduce memory overhead and improve performance. A cache mechanism may be considered to store commonly used view controller instances.

[0059] Preferably, in the step (S1), when the page jumps, the life cycle of the landing page is first triggered, but the page does not jump immediately. The system first checks whether the first screen data of the landing page has been cached:

[0060] If there is cached data, the page jumps immediately;

[0061] If the business carries landing page data, the page will jump immediately;

[0062] If the above conditions are not met, the system initiates a first-screen data request and executes a page jump after the request is successful.

[0063] Preferably, in the step (S1), under weak network conditions, the timeout module will control the jump process to prevent the user experience from being reduced due to long waiting time. Through the configuration module, the system can dynamically choose whether to enable this solution according to the needs of the specific landing page. This solution is applicable to all jump methods, including complex scenarios such as openURL.

[0064] Preferably, the step (S2) supports multiple redirection methods, not only for conventional redirection, but also for methods such as openURL, to ensure coverage of all scenarios.

[0065] Preferably, in the step (S3), log records are added after the weak network optimization, and log record statements are added in key code segments to record the running status and error information of the program, and the problem is located and a corresponding solution is formulated by analyzing the log records.

[0066] Preferably, after the weak network optimization in step (S3), Xcode is used for debugging, and the running status of the application is monitored by the debugging tool of Xcode, including memory usage, CPU occupancy, etc., and the problem is located by setting breakpoints, checking variable values, etc.

[0067] The above technical method based on iOS high-performance loading to solve the problem of page jump without white screen has strong adaptability: it only needs to be connected once on the landing page, and all pages using this jump method can take effect; low development cost: only need to replace the page jump API, and ensure that the landing page first screen data is prepared, without the need for large-scale transformation of the page; on-demand loading: avoid unnecessary preloading requests, reduce the consumption of CPU, memory and network traffic; support multiple jump methods: not only suitable for regular jumps, but also supports openURL and other methods to ensure coverage of all scenarios.

[0068] It will be apparent to those skilled in the art that the invention is not limited to the details of the exemplary embodiments described above and that the invention can be implemented in other specific forms without departing from the spirit or essential features of the invention. Therefore, the embodiments should be considered exemplary and non-limiting in all respects, and the scope of the invention is defined by the appended claims rather than the foregoing description, and it is intended that all variations falling within the meaning and scope of the equivalent elements of the claims be included in the invention. Any reference numeral in a claim should not be considered as limiting the claim to which it relates.

[0069] In addition, it should be understood that although the present specification is described according to implementation modes, not every implementation mode contains only one independent technical solution. This description of the specification is only for the sake of clarity. Those skilled in the art should regard the specification as a whole. The technical solutions in each embodiment may also be appropriately combined to form other implementation modes that can be understood by those skilled in the art.

Claims

1. A technical method for solving page jump without white screen based on iOS high performance loading, characterized by: The technical method for solving the problem of page jump without white screen includes the following steps: S1. On-demand loading mechanism: when the page jumps, data is loaded according to actual needs to avoid excessive preloading and resource waste; S2. Optimize user experience: Redirect pages on the premise that the data on the first screen of the page has been obtained, thereby avoiding page blanks or loading phenomena and improving user experience; S3. Weak network optimization: Through the timeout control module, a good user experience can be maintained even in poor network conditions.

2. The technical method for solving page jump without white screen based on iOS high performance loading according to claim 1 is characterized in that: In the step (S1), for the data that needs to be loaded from the network, an asynchronous loading method is adopted to avoid blocking the main thread, and a suitable network request library is used to manage network requests and responses. The network request library includes Alamofire and NSURLSession.

3. The technical method for solving page jump without white screen based on iOS high performance loading according to claim 1 is characterized in that: In the step (S1), the page loading performance is optimized by using WKWebView, which is a recommended web view component in iOS 8 and later versions. Compared with UIWebView, WKWebView has higher performance and better stability, supports JavaScript interaction and new features of HTML5, and has a refresh rate of up to 60fps, which can provide a smooth user experience.

4. The technical method for solving page jump without white screen based on iOS high performance loading according to claim 1 is characterized in that: The correctness of the page jump logic is ensured in the step (S2), including necessary preparation work, including loading data, initializing pages, and avoiding null pointer exceptions or memory leaks during the jump process.

5. The technical method for solving page jump without white screen based on iOS high performance loading according to claim 1 is characterized in that: In the step (S2), when the page jumps, repeated creation and destruction of view controllers are avoided to reduce memory overhead and improve performance. A cache mechanism may be considered to store commonly used view controller instances.

6. The technical method for solving page jump without white screen based on iOS high performance loading according to claim 1 is characterized in that: In the step (S1), when the page jumps, the life cycle of the landing page is triggered first, but the page does not jump immediately. The system first checks whether the first screen data of the landing page has been cached: If there is cached data, the page jumps immediately; If the business carries landing page data, the page will jump immediately; If the above conditions are not met, the system initiates a first-screen data request and executes a page jump after the request is successful.

7. The technical method for solving page jump without white screen based on iOS high performance loading according to claim 1 is characterized in that: In the step (S1), under weak network conditions, the timeout module will control the jump process to prevent the user experience from being reduced due to long waiting time. Through the configuration module, the system can dynamically choose whether to enable this solution according to the needs of the specific landing page. This solution is applicable to all jump methods, including complex scenarios such as openURL.

8. The technical method for solving page jump without white screen based on iOS high performance loading according to claim 1 is characterized in that: The step (S2) supports multiple redirection methods, not only for conventional redirection, but also for methods such as openURL, to ensure that all scenarios are covered.

9. The technical method for solving page jump without white screen based on iOS high performance loading according to claim 1 is characterized in that: In the step (S3), log records are added after the weak network optimization, and log record statements are added in the key code segments to record the running status and error information of the program, and the problem is located and a corresponding solution is formulated by analyzing the log records.

10. The technical method for solving page jump without white screen based on iOS high performance loading according to claim 1 is characterized in that: After the weak network optimization in step (S3), Xcode is used for debugging, and the running status of the application, including memory usage, CPU occupancy, etc., is monitored using Xcode's debugging tools, and problems are located by setting breakpoints, checking variable values, etc.

Images