Does anyone know the URI structure required by the “ChatGPT” Android app to create a deeplink that will lead to the “ChatGPT” Android app and open a specific GPT there? I would greatly appreciate it if an OpenAI staff member could assist with this query.
This is important because without a deep link, Android users open the GPT link in their mobile browser instead of the “ChatGPT” mobile app, which significantly hinders the ease of opening GPT in the “ChatGPT” Android app. Furthermore, I have not found any public information regarding the required URI structure for such deep links that will lead to the “ChatGPT” Android app and open chosen GPT.
I’ve been conducting tests with GPT https links, such as https://chat.openai.com/g/g-QB8XfqvUd-test, across various third-party applications. I’ve noticed that in certain mobile messengers and social networks, these links tend to open in a mobile browser. Following your suggestion, I reviewed the Android settings for the ChatGPT app and found it set to ‘Always ask’, which I believe is the default for most users. This presents a challenge, especially as these links are used in third-party apps. Opening the link in a mobile browser complicates the user experience, particularly if the user is not logged into ChatGPT in their browser, a scenario that seems quite frequent.
I am keen to learn if there’s a viable method to create a deep link that reliably directs users to open GPT links in the ChatGPT app, especially considering the ‘Always ask’ default setting. I understand that Android offers functionalities like intents, and ChatGPT Android app probably used intent functionality, but I’m uncertain about the URI structure needed to craft a deep link that prompts users to open the link in the ChatGPT app, regardless in which mobile messenger or social network the link was opened.
Could there be a prescribed format for such a deep link, perhaps something in the vein of:
{Some ChatGPT scheme name}://g/g-QB8XfqvUd-test
?
If so, I would be immensely grateful if you could provide guidance on the appropriate scheme name to use for ChatGPT in these deep links. Your expertise and assistance in this matter would be greatly appreciated.
Your point is well taken. As a personal example, I recently discovered that my device is set to the ‘Always ask’ option by default. This was a setting I wasn’t previously aware of, and I hadn’t actively managed this aspect of my user experience before.
In my dealings with third-party apps, I’ve encountered an inconsistency: when I click on a GPT link, it often doesn’t prompt me to choose between opening it in a mobile browser or in the ChatGPT mobile app, despite having the ‘Always ask’ setting enabled.
This led me to seek potential solutions that could assist users facing similar issues. Ideally, if a user’s default is set to ‘Always ask’, the system should respect this preference and offer a choice of destination. That’s exactly the type of user experience I’m aiming to achieve.
However, I now realize that the resolution might primarily depend on the user, especially in terms of managing a setting that many may not be fully aware of or attentive to. Therefore, I find myself at an impasse, unsure of how to resolve this issue, and puzzled about why, in some third-party apps, a GPT link behaves in this manner.
