![]() Normally, you might have to switch back and forth between using ChatGPT versus using the sales package. The plugins add the following switcheroo direction. That would be the already conventional App-to-ChatGPT routing. Maybe they request a bunch of emails is composed for a prospects list. Going back to the sales package example, a user in the sales package might make use of ChatGPT while inside the sales app. They are not mutually exclusive of each other. ![]() Now you can be using ChatGPT and have it invoke some outside app that provides complementary capabilities or useful augmentations for ChatGPT b) Driving up the street via ChatGPT-to-App.You could perchance use someone else's app that happened to have set up a connection to ChatGPT via the API a) Driving down the street via App-to-ChatGPT.Look at it this way, as though driving on a street: Whereas the up-until-now API connections meant that other apps would invoke ChatGPT, the hot and heavy facets of plugins are that this means you can now use other apps while making use of ChatGPT. Some are saying that the plugins will inexorably and dramatically shift ChatGPT into the enviable position of becoming ChatGPT as a platform. Try this on for size: ChatGPT as a platform. There will be a lot more interest in further piling into the ChatGPT bandwagon. The bandwagon has now gotten even more attractive. Let’s step up the game and add plugins into the mix. This is a bandwagon that is certainly good for the other allied software makers and equally good for OpenAI and their persistent and outsized efforts to garner larger and larger usage of ChatGPT (a seemingly never-ending quest). The other and especially vibrant plus is that your software gets that oh-so-awesome ChatGPT afterglow. One cheerful consideration proffered the obvious point that adopting ChatGPT usage could enhance the features of your software. The special bonus was that the software maker could then tout that they too are a card-carrying member of the heralded ChatGPT wonderment club. You might ostensibly declare that it was nearly a no-brainer to proceed to get connected. Voila, your software package suddenly can do all manner of Natural Language Processing (NLP).Īll told, this meant that the uses of ChatGPT could expand immensely.įirms that provide apps were thirstily lured to the ChatGPT API like a siren call. Rather than trying to program or code such a capability, all they need to do is include a portion that makes use of the API connecting to ChatGPT. Essentially, allowing one program to access another program.įor example, suppose a maker of a sales package wants to allow their users to generate snazzy emails for sending to sales prospects. This is undertaken by a programming convenience known as an API. In short, other software makers could opt to leverage ChatGPT by connecting their software to ChatGPT. The availability of an API was a smart move and meant that more than just direct usage would arise. When ChatGPT was first starting out back in November, I had predicted that the third item listed above would gradually and inevitably bolster the use of ChatGPT to heightened levels of everyday usage, see my written analysis at the link here.
0 Comments
Leave a Reply. |