Launched four MyGPTs, I have many questions for dev team

ChatGPT
, , ,
1

Hi,

I have launched four myGPTs and need tirekickers from the community. I also have many questions and suggestions for the dev team.

First, tirekickers wanted!

Feedback:

  1. I hope these will be available outside of ChatGPT Pro soon. Right now, it is hard to find tirekickers because only a small % of my total circle is paying for Pro, and random people don’t want to sign up for pay service even with free trial.
  2. the “visitors” stat next to the bubble icon on the Explore page appears to be the number of unique non-me visits, is that correct? More detailed stats would be helpful, for example duration and number of “rounds”.
  3. will we be able to receive the feedback thumbs down/thumbs up/ comments info? Otherwise, no way to know if the chat is staying on track in the wild.
  4. @Sama made a comment after dev day to the Verge that revenue share would be DAU-based and tiered. This is very bad for devs who want to focus on professional users. We have to have a subscription pricing plan with healthy monthly price maximums or at least a one-time join fee.
  5. It appears that behind the scenes my guidance to the GPT is divided into several sets of instruction buckets which on editing are then regenerated into an overall plan for the GPT.
    a) it is disconcerting that changing the name or some other aspect of the GPT produces text or visual changes elsewhere in the configuration, but I got used to it.
    b) it would be super helpful to have visibility into the buckets and be able to modify them individually.
  6. Also super important to have an API and be able to get and post configurations.
  7. As soon as I started sharing my GPTs with my professional clients (authors whom I publish), it became apparent that they are all going to want to be able to collaborate on the GPT. Collaborators have to include a) people outside my “organization” b) non-Pro-customers (I can’t expect authors to pay for the privilege of providing their input.) And the creator has to have veto power over collaborator contributions.
  8. Can you provide an icon or something next to each GPT, or on the admin page, that confirms Copyright Shield ON for all/each app? Another idea is to have a subtle icon display on the user-facing GPT page, but that has pros and cons.
  9. The Explore page is really two pages, “Browse My GPts” and “Admin”. I want them separate. I assume that Explore will become “Discover and Add to My GPTs” in the near future.

HTH,

Fred

2

So, I’m not OAI staff, but I can make some educated guesses here.

While we still don’t know whether or not GPTs from GPT store will be released to non-plus users, my guess is going to be; don’t bet on it.

Consider this: a revenue share is a means to share acquired revenue and profits that you have contributed towards increasing for the greater company. I bet you anything OpenAI’s intentions is to have as many people sign on to GPT plus as possible. Free users are not making OAI money; plus users are. So, it’s likely that if you can make a GPT so useful that people are signing up to GPT plus just to use your tool, then you’re going to get revenue share because you made GPT plus a bunch of money. If you want a slice of that sweet, sweet, revenue pie, you have to think about how you’re going to make OpenAI money, and how OpenAI wants to make money with these tools.

You can refer a friend to give somebody else a trial for ChatGPT plus, but remember devs are using the API calls to make assistants (which are different than ChatGPT features), not ChatGPT. API use does not require a plus subscription, so if you want a collaborative dev team with non-plus users, you would have to pivot to using the API instead, which does prevent you from publishing on GPT store (for now). Do not expect non-plus users to be able to edit or develop custom GPTs in the near future. That is, for all intents and purposes, practically one of the biggest selling points that distinguishes plus subscribers from normal users.

Finally, Copyright Shield isn’t like Brave Shield; it’s a formalized commitment towards allowing you to direct the lawsuit to OpenAI if you get sued. It’s not a technical feature; it’s merely giving you the permission to ask OAI for help if you end up in legal trouble for your projects.

The rest, like metrics, likes, and comments, are likely features that will be a part of the GPT store, but as of now those precise design elements aren’t fully known yet. However, you can think of this like providing us an IDE to build your App before the App Store is released to the public.