These are Activity, Service, Content provider, and Broadcast receiver. The Activity component is defined by the user interface. This part controls what the user uses on the application which is usually separated into one Activity per screen. One example may be the different application buttons the user can press on the home screen. The Service component controls the procedures that run in the background. These may call other programs that oversee background downloads of music, files, etc. If the designer wants, the service can also be application specific daemons run service. Useful examples of services in the background is a firewall that records and matches internet traffic to its list of dangerous websites or an antivirus app that will automatically check the system periodically and after the app updates it’s virus database. The Content provider uses a relational database interface to control the sharing of data. Using Structured Query language or SQL as a base language, the Content provider relays date between apps, and from apps to internet and vice versa. This is regulated with the SQL Delete, Select, and Insert are several commands that the Content provider uses to set permissions between one object to another like an Access Control List or ACL. Common examples of this are when you send a text to someone, or when you get a high score on a mobile game, and you send the score to display it on leaderboards. The last component is a Broadcast receiver. This is space specifically designed to receive data or signals. This can be used in tandem with Services and Content providers to receive updates such as an email app telling you when you get email. When all of the components put together, this explains how your phone’s system works. For example, if you turn on your device which is connected to the internet, and your mailbox on a web site gets a new email, then the device will alert you. When you are at
These are Activity, Service, Content provider, and Broadcast receiver. The Activity component is defined by the user interface. This part controls what the user uses on the application which is usually separated into one Activity per screen. One example may be the different application buttons the user can press on the home screen. The Service component controls the procedures that run in the background. These may call other programs that oversee background downloads of music, files, etc. If the designer wants, the service can also be application specific daemons run service. Useful examples of services in the background is a firewall that records and matches internet traffic to its list of dangerous websites or an antivirus app that will automatically check the system periodically and after the app updates it’s virus database. The Content provider uses a relational database interface to control the sharing of data. Using Structured Query language or SQL as a base language, the Content provider relays date between apps, and from apps to internet and vice versa. This is regulated with the SQL Delete, Select, and Insert are several commands that the Content provider uses to set permissions between one object to another like an Access Control List or ACL. Common examples of this are when you send a text to someone, or when you get a high score on a mobile game, and you send the score to display it on leaderboards. The last component is a Broadcast receiver. This is space specifically designed to receive data or signals. This can be used in tandem with Services and Content providers to receive updates such as an email app telling you when you get email. When all of the components put together, this explains how your phone’s system works. For example, if you turn on your device which is connected to the internet, and your mailbox on a web site gets a new email, then the device will alert you. When you are at