Android borderless Program Design Philosophy

 

From: http://blog.csdn.net/lfhfut/archive/2010/07/21/5751348.aspx borderless Program Design Concept this formulation comes from here. "Android applications are just virtual and there is no actual entry point. Unlike the application concepts on the Windows platform, Android provides more Components. Highlight requests and services, highlight individual components, and weaken boundaries. various components of the system can communicate freely without boundaries. Service requestors directly send requests, no matter where the object is or who it belongs to, the component is a free and independent individual. An application can directly request the components of other applications. This is the core concept of the Android Application Framework Design, everything else serves this core idea." "Let programmers ignore the concept of application, or even abandon the concept of process completely. What programmers see is a component. application programmers use these components to construct a so-called application, so what do designers need to consider first? I think it should be an abstract application model under which concepts and interfaces are generated ." "In Android, you can start an Activity, but you have no right to destroy an Activity. This is an embodiment of individual rights. The elimination of an individual is determined by the system, this is the humanistic meaning of Activity in Android." This summary is very good. From my recent basic understanding of Android development, it is true. Developed on the Android platform, you do not need to build an application from the beginning. You can use some of the functions provided by the system, or some of the functions already implemented in other applications, to assemble your own applications. Of course, you can expose some of your functions to others. Specifically, it is the use of Activity and Intent. Based on this model, Android development is more like accumulation of wood. Of course, this is ideal. Recently, Google launched a tool for generating a custom application by dragging components on the web. Of course, I only read the following introduction, there is no chance to experience it in person. However, this will be the trend of the future. Of course, this is a good thing for developers. You can turn your ideas into reality more quickly. You don't have to do anything small. This is also a good thing for mobile phone users. Applications built using a unified Activity are completely unified in terms of appearance and usage. When users get a new application, there will be no significant cost for use. This is certainly a good thing for Google. Google can make all its cloud computing services into components, and application developers can freely combine them into their own applications, this will be very helpful for Google to promote its own services. Of course, currently, the provision of components is not perfect. To develop an application, you still need to do a lot of work on your own. Only a few services can directly call the Intent provided by Google, however, it is difficult to ensure that the Activity of others is called, such as the dependency on others' applications, such as the interface guarantee, and so on. In addition, mobile phone manufacturers now provide their own UI sence when customizing Android, and different mobile phone manufacturers are also different. In addition to Android native, this makes it increasingly difficult to unify the UI, I don't know what to do in the future. This article from the CSDN blog, reproduced please indicate the source: http://blog.csdn.net/chrisplus_jiang/archive/2010/07/29/5773299.aspx