Android Client Design Solution

Solutions are being talked about with demand. An abstract requirement requires a more abstract solution to deal with it, which is the relationship between disease and medicine. However, a solution may contain multiple features, each of which is a node on the solution. An excellent solution must be supported by one or more core functions.

 in the Android client to implement the solution, the first thing to do is to do two things: 1 will be implemented in the list of features, and one by one refinement, sorting. 2 core function Operation guarantee. 3 Analyze the hardware environment, familiar with the functions and interfaces that the client can provide, and the data quality.  1 Listing Features: Implementing a solution is certainly not just a function, but there must be one or two core functions. But the core function, does not mean that the user can be very convenient to operate. Therefore, some support functions need to be supplemented according to the user's usage habits. For example, playing a video file, the core function is the playback function, but the user's habit is: first open the file selector, click on the file to play. Clearly meet the user's this whole set, can say is a solution. Second, some features can continue to be subdivided, and the subdivision function helps to be more clear and the system environment evaluated. Listing these features, and sequencing, will facilitate the implementation of the business and the estimation of invoking the system interface.  2 Safeguard core functions: two aspects, whether the core function itself is robust, running smoothly in a demanding system environment. Many buger like to transplant code, but rarely consider the operating conditions and whether they can be run healthily. An assessment is needed in this regard. On the other side, whether the core functions need to be called properly, and how the exceptions to the runtime ensure stability.   3 Analyzing the hardware environment: the hardware environment refers to some of the interfaces that a device can invoke and the data it provides. Some machines may not have certain devices, such as gyroscopes, data Services, NFC, etc., which need to be considered beforehand, otherwise NFC is required in the solution, or the functionality in some small corners requires this kind of hardware support, but no, it is not a bad thing. On the other hand, data quality, if you want to take a low-pixel camera to shoot some scenery, the resulting video data, certainly no high-pixel good. It is necessary to consider, otherwise, you know.  To summarize the pull of the egg, summarized as the need for data to achieve their own business or program, and to be able to assess the existing hardware environment can be satisfied, not meet the change, fits casually you.

Android Client Design Solution