State-specific external functionality for software developers

1. A computing, device comprising:

a data store configured to store information identifying a plurality of functions, wherein each of the plurality of functions corresponds to external functionality available from third party applications; and

at least one processor configured to:

receive a selection, from a first electronic device corresponding to a first application developer, of a first function of the plurality of functions to supplement functionality of a first application under development by the first application developer, and

provide a software development kit (SDK) library associated with the first function to the first electronic device,

wherein the SDK library includes instructions for:

when a first screen of the first application including a first user interface element is displayed at a user device which executes the first application developed at least based on the SDK library, in response to user selection of the first user interface element, preparing a query wrapper including a combination of a predefined text string corresponding to the first function and a name of a first entity inputted at the user device,

transmitting the query wrapper to a search system,

receiving a result set from the search system, wherein the result set includes a plurality of items, and wherein a first item of the plurality of items includes an identifier of a target application and an access mechanism for a specified screen of the target application associated with the query wrapper,

displaying the plurality of items, and

in response to user selection of the first item, actuating the access mechanism to execute the target application and display the specified screen.

2. The computing device of claim 1 , wherein the access mechanism specifies downloading and installing the target application from a digital distribution platform prior to executing the target application.

3. The computing device of claim 1 ,

wherein the first item includes a second access mechanism, and

wherein the second access mechanism specifies executing a web edition of the target application to the specified screen.

4. The computing device of claim 1 , wherein the access mechanism includes a script to navigate from a default screen of the target application to the specified screen of the target application.

5. The computing device of claim 1 , wherein the at least one processor is further configured to:

provide a specification of the first user interface element to the first electronic device, and

provide, to the first electronic device, a function call for including the name of the first entity in the query wrapper.

6. The computing device of claim 1 , wherein visual properties of the first user interface element are adjusted in response to choices made by the first application developer.

7. The computing device of claim 1 ,

wherein the at least one processor is further configured to store a blacklist in the data store, and

wherein the blacklist indicates at least one target application to exclude from the result set or at least one application screen specified by at least one access mechanism to be excluded from the result set.

8. The computing device of claim 7 , wherein the SDK library further includes instructions for at least one of:

removing the at least one target application and the at least one access mechanism specifying application screens matching the blacklist from the result set received from the search system;

providing the blacklist to the search system as part of the query wrapper; and

preventing display of the at least one application screen matching the blacklist.

9. The computing device of claim 7 , wherein the at least one processor is further configured to provide the blacklist to the search system so that the search system excludes from the result set the at least one target application identified by the blacklist and the at least one access mechanism specifying the at least one application screen identified by the blacklist.

10. A method of operating a computing device, the method comprising:

storing, by a data store, information identifying a plurality of functions, wherein each of the plurality of functions corresponds to external functionality available from third party applications;

receiving, by at least one processor, a selection, from a first electronic device corresponding to a first application developer, of a first function of the plurality of functions to supplement functionality of a first application under development by the first application developer; and

providing, by the at least one processor, a software development kit (SDK) library associated with the first function to the first electronic device,

wherein the SDK library includes instructions for:

when a first screen of the first application including a first user interface element is displayed at a user device which executes the first application developed at least based on the SDK library, in response to user selection of the first user interface element, preparing a query wrapper including a combination of a predefined text string corresponding to the first function and a name of a first entity inputted at the user device,

transmitting the query wrapper to a search system,

receiving a result set from the search system, wherein the result set includes a plurality of items, and wherein a first item of the plurality of items includes an identifier of a target application and an access mechanism for a specified screen of the target application associated with the query wrapper,

displaying the plurality of items, and

in response to user selection of the first item, actuating the access mechanism to execute the target application and display the specified screen.

11. The method of claim 10 , wherein the access mechanism specifies downloading and installing the target application from a digital distribution platform prior to executing the target application.

12. The method of claim 10 ,

wherein the first item includes a second access mechanism, and

wherein the second access mechanism specifies executing a web edition of the target application to the specified screen.

13. The method of claim 10 , wherein the access mechanism includes a script to navigate from a default screen of the target application to the specified screen of the target application.

14. The method of claim 10 , further comprising:

providing a specification of the first user interface element to the first electronic device; and

providing, to the first electronic device, a function call for including the name of the first entity in the query wrapper.

15. The method of claim 10 , wherein visual properties of the first user interface element are adjusted in response to choices made by the first application developer.

16. The method of claim 10 , further comprising storing a blacklist in the data store, wherein the blacklist indicates at least one target application to exclude from the result set or at least one application screen specified by at least one access mechanism to be excluded from the result set.

17. The method of claim 16 , wherein the SDK library further includes instructions for at least one of:

removing the at least one target application and the at least one access mechanism specifying application screens matching the blacklist from the result set received from the search system;

providing the blacklist to the search system as part of the query wrapper; and

preventing display of the at least one application screen matching the blacklist.

18. The method of claim 16 , further comprising providing the blacklist to the search system so that the search system excludes from the result set the at least one target application identified by the blacklist and the at least one access mechanism specifying the at least one application screen identified by the blacklist.