Managing iOS-based mobile communication devices by creative use of callkit API protocols
Systems, methods, and devices for managing predetermined functions on a mobile device, the operating system (OS) installed on the device including an event application programming interface (API) configured to enable voice over internet protocol (VoIP) applications to assume priority over other applications and functions of the mobile device when VoIP calls are detected. A mobile device management software application installed and running on the mobile device emulates a VoIP software application and uses event API calls to trick the OS into believing that a VoIP call has been detected and, in response, causes the OS to block or interfere with one or more predetermined functions on the mobile device based on the status and location of the mobile device.
1. A method for preventing user interaction in a mobile device, comprising:
detecting activity in the mobile device that is prohibited based on a policy; and
in response to the detected activity, invoking one or more Voice over Internet Protocol (VoIP) application programming interface (API) functions by an application to prevent user interaction with the activity, wherein invoking the one or more VoIP API functions causes the mobile device to display the application in a foreground of the mobile device, wherein to display the application in the foreground of the mobile device prevents user interaction with the activity.
2. The method of claim 1 , wherein invoking the one or more API functions causes the mobile device to:
generate a VoIP call notification by the application; and
display the VoIP call notification in the foreground of the mobile device, wherein to display the VoIP call notification prevents user interaction with the activity.
3. The method of claim 2 , wherein the VoIP call notification includes a caller name, and further comprising:
changing the caller name in the VoIP call notification to an indication that the activity is being prevented.
4. The method of claim 1 , further comprising:
generating a notification indicating that the activity is prohibited; and
displaying the notification in the foreground of the mobile device.
5. The method of claim 1 , wherein the detected activity is of a second application, and wherein the detected activity is further prohibited based on the second application corresponding to a blacklisted application.
6. A computer-readable storage medium storing computer-executable instructions, which, when executed on a processor of a mobile device, cause a mobile device to perform an operation for preventing user interaction in a mobile device, the operation causing the mobile device to:
detect activity in the mobile device that is prohibited based on a policy; and
in response to the detected activity, invoking one or more Voice over Internet Protocol (VoIP) application programming interface (API) functions by an application to prevent user interaction with the activity, wherein invoking the one or more VoIP API functions causes the mobile device to display the application in a foreground of the mobile device, wherein to display the application in the foreground of the mobile device prevents user interaction with the activity.
7. The computer-readable storage medium of claim 6 , wherein to invoke the one or more API functions causes the mobile device to:
generate a VoIP call notification by the application; and
display the VoIP call notification in the foreground of the mobile device, wherein to display the VoIP call notification prevents user interaction with the activity.
8. The computer-readable storage medium of claim 7 , wherein the VoIP call notification includes a caller name, and wherein the computer-executable instructions further cause the mobile device to:
change the caller name in the VoIP call notification to an indication that the activity is being prevented.
9. The computer-readable storage medium of claim 6 , wherein the operation further causes the mobile device to:
generate a notification indicating that the activity is being prevented; and
display the notification in the foreground of the mobile device.
10. The computer-readable storage medium of claim 6 , wherein the detected activity is of a second application, and wherein the detected activity is further prohibited based on the second application corresponding to a blacklisted application.
11. A mobile device comprising:
a processor; and
a memory storing computer-executable instructions, which, when executed on the processor, causes a mobile device to perform an operation for preventing user interaction in the mobile device, the operation causing the mobile device to:
detect activity in the mobile device that is prohibited based on a policy; and
in response to the detected activity, invoking one or more Voice over Internet Protocol (VoIP) application programming interface (API) functions by an application to prevent user interaction with the activity, wherein invoking the one or more VoIP API functions causes the mobile device to display the application in a foreground of the mobile device, wherein to display the application in the foreground of the mobile device prevents user interaction with the activity.
12. The mobile device of claim 11 , wherein to invoke the one or more API functions further causes the mobile device to:
generate a VoIP call notification by the application; and
display the VoIP call notification in the foreground of the mobile device, wherein to display the VoIP call notification prevents user interaction with the activity.
13. The mobile device of claim 12 , wherein the VoIP call notification includes a caller name, and wherein the computer-executable instructions further cause the mobile device to:
change the caller name in the VoIP call notification to an indication that the activity is being prevented.
14. The mobile device of claim 11 , wherein the operation further causes the mobile device to:
generate a notification indicating that the activity is being prevented; and
display the notification in the foreground of the mobile device.
15. The mobile device of claim 11 , wherein the detected activity is of a second application, and wherein the detected activity is further prohibited based on the second application corresponding to a blacklisted application.