Systems and methods for integrating mobile application plug-ins
The present disclosure is directed to integrating mobile application plug-ins. For example, a method may include: at run-time of a host application, initializing, by the host application, a plurality of plug-ins; in response to initializing the plurality of plug-ins, establishing a set of supported services provided between a plurality of components comprising a native component of the host application and the plurality of plug-ins; detecting a request for a service from a first component of the plurality of components; and in response to determining that the requested service is one of the supported services, routing the requested service to a second component of the plurality of components, the second component being different than the first component.
1. A computer-implemented method, comprising:
at run-time of a host application, initializing, by the host application, a plurality of plug-ins, wherein:
the host application comprises a native component and communicates services of the host application to the plurality of plug-ins with a plug-in service provider interface (SPI);
the host application injects at run-time a plug-in application programming interface (API) that is specific to a type of the host application into one or more of the plurality of plug-ins; and
the one or more of the plurality of plug-ins communicates services of the one or more of the plurality of plug-ins to the host application with the plug-in API;
in response to initializing the plurality of plug-ins, establishing, during run-time of the host application, a bi-directional contract between the host application and the plurality of plug-ins with the plug-in SPI and the plug-in API, wherein the bi-directional contract defines a set of supported services requested and cross-accessed by a plurality of components comprising the native component of the host application and the plurality of plug-ins;
detecting a request for a service from a first component of the native component and the plurality of plug-ins; and
in response to determining that the requested service is one of the supported services, routing the requested service to a second component of the native component and the plurality of plug-ins, the second component being different than the first component.
2. The method of claim 1 , further comprising:
transmitting a query to each of the plurality of components to determine which of the plurality of components can provide the requested service; and
selecting the second component based on responses from the plurality of components in response to the query.
3. The method of claim 1 , wherein the one or more of the plurality of plug-ins comprise an SPI implementation and the host application communicates services of the host application to the SPI implementation of the one or more of the plurality of plug-ins.
4. The method of claim 1 , further comprising integrating a new plug-in into the plurality of plug-ins in response to the new plug-in being installed.
5. The method of claim 1 , further comprising receiving an update to a first plug-in of the plurality of plug-ins and modifying a pointer of the first plug-in.
6. The method of claim 1 , wherein the first component of the plurality of components is the native component, and wherein routing the requested service to the second component of the plurality of components comprises routing the requested service to the plurality of plug-ins.
7. The method of claim 1 , wherein the first component of the plurality of components is one of the plurality of plug-ins, and wherein routing the requested service to the second component of the plurality of components comprises routing the requested service to the native component.
8. A device, comprising:
a memory; and
a processor coupled to the memory and configured to:
at run-time of a host application, initialize, using the host application, a plurality of plug-ins, wherein:
the host application comprises a native component and communicates services of the host application to the plurality of plug-ins with a plug-in service provider interface (SPI);
the host application injects at run-time a plug-in application programming interface (API) that is specific to a type of the host application into one or more of the plurality of plug-ins; and
the one or more of the plurality of plug-ins communicates services of the one or more of the plurality of plug-ins to the host application with the plug-in API;
in response to initializing the plurality of plug-ins, establish, during run-time of the host application, a bi-directional contract between the host application and the plurality of plug-ins with the plug-in SPI and the plug-in API, wherein the bi-directional contract defines a set of supported services requested and cross-accessed by a plurality of components comprising the native component of the host application and the plurality of plug-ins;
detect a request for a service from a first component of the native component and the plurality of plug-ins; and
in response to determining that the requested service is one of the supported services, route the requested service to a second component of the native component and the plurality of plug-ins, the second component being different than the first component.
9. The device of claim 8 , wherein the processor is further configured to:
transmit a query to each of the plurality of components to determine which of the plurality of components can provide the requested service; and
select the second component based on responses from the plurality of components in response to the query.
10. The device of claim 8 , wherein the one or more of the plurality of plug-ins comprise an SPI implementation and the host application communicates services of the host application to the SPI implementation of the one or more of the plurality of plug-ins.
11. The device of claim 8 , wherein the processor is further configured to integrate a new plug-in into the plurality of plug-ins in response to the new plug-in being installed.
12. The device of claim 8 , wherein the processor is further configured to receive an update to a first plug-in of the plurality of plug-ins and modify a pointer of the first plug-in.
13. The device of claim 8 , wherein the first component of the plurality of components is the native component, and wherein, to route the requested service to the second component of the plurality of components comprises, the processor is further configured to route the requested service to the plurality of plug-ins.
14. The device of claim 8 , wherein the first component of the plurality of components is one of the plurality of plug-ins, and wherein, to route the requested service to the second component of the plurality of components, the processor is further configured to route the requested service to the native component.
15. A non-transitory computer-readable device having instructions stored thereon that, when executed by at least one computing device, cause the at least one computing device to perform operations comprising:
at run-time of a host application, initializing, by the host application, a plurality of plug-ins, wherein:
the host application comprises a native component and communicates services of the host application to the plurality of plug-ins with a plug-in service provider interface (SPI);
the host application injects at run-time a plug-in application programming interface (API) that is specific to a type of the host application into one or more of the plurality of plug-ins; and
the one or more of the plurality of plug-ins communicates services of the one or more of the plurality of plug-ins to the host application with the plug-in API;
in response to initializing the plurality of plug-ins, establishing, during run-time of the host application, a bi-directional contract between the host application and the plurality of plug-ins with the plug-in SPI and the plug-in API, wherein the bi-directional contract defines a set of supported services requested and cross-accessed by a plurality of components comprising the native component of the host application and the plurality of plug-ins;
detecting a request for a service from a first component of the native component and the plurality of plug-ins; and
in response to determining that the requested service is one of the supported services, routing the requested service to a second component of the native component and the plurality of plug-ins, the second component being different than the first component.
16. The non-transitory computer-readable device of claim 15 , wherein the operations further comprise:
transmitting a query to each of the plurality of components to determine which of the plurality of components can provide the requested service; and
selecting the second component based on responses from the plurality of components in response to the query.
17. The non-transitory computer-readable device of claim 15 , wherein the one or more of the plurality of plug-ins comprise an SPI implementation and the host application communicates services of the host application to the SPI implementation of the one or more of the plurality of plug-ins.
18. The non-transitory computer-readable device of claim 15 , wherein the operations further comprise receiving an update to a first plug-in of the plurality of plug-ins and modifying a pointer of the first plug-in.
19. The non-transitory computer-readable device of claim 15 , wherein the first component of the plurality of components is the native component, and wherein routing the requested service to the second component of the plurality of components comprises routing the requested service to the plurality of plug-ins.
20. The non-transitory computer-readable device of claim 15 , wherein the first component of the plurality of components is one of the plurality of plug-ins, and wherein routing the requested service to the second component of the plurality of components comprises routing the requested service to the native component.