The App Details section is where you configure essential information about your app. Below is a breakdown of each field and how to fill it out.


1. App Title

  • Description: The name of your app that will be displayed to end-users.
  • What to Do:
    • Enter a clear, descriptive name that reflects the app’s functionality.
    • Make it easy to understand for your target audience.

Example: AI Content Generator, Chat Helper, etc.


2. Slug (Optional)

  • Description: A unique, URL-friendly identifier for your app.
  • What to Do:
    • Leave it blank to automatically generate a slug based on the title.
    • You can also manually enter a custom slug using lowercase letters, numbers, and hyphens.

Example: ai-content-generator


3. Base Credits

  • Description: The flat number of credits required for the app’s usage before any additional charges apply.
  • What to Do:
    • Set a base credit amount based on how much you want users to be charged initially.
    • This value is charged regardless of API usage.

Example: Enter 10 for a base credit of 10.


4. Credit Charge Method

  • Description: Determines how credits will be deducted when using the app.
  • What to Do:
    • Select one of the following options to define how your app charges for usage.

Available Options:

a) Combined Credits (base credits + usage credits for extra usage)

  • How It Works:
    • Charges the set Base Credits first.
    • Any extra API usage is charged as Usage Credits on top of the base.
  • Best For:
    • Apps that want predictable base pricing with additional charges for heavy usage.

Example: If Base Credits are 10 and API usage exceeds the threshold, additional credits will be deducted.


b) Usage Credits Only (based on total API cost, configured in website settings)

  • How It Works:
    • Ignores the Base Credits and only deducts credits based on API usage.
    • Credits are calculated dynamically depending on the total API cost.
  • Best For:
    • Apps where costs fluctuate significantly depending on the amount of usage.

Example: Credits will only be deducted when API calls are made, aligning directly with the usage cost.


c) Base Credits Only (regardless of extra usage)

  • How It Works:
    • Charges only the Base Credits, regardless of how much the app is used.
    • No additional charges apply, even if the app exceeds the expected API usage.
  • Best For:
    • Fixed-price apps where predictable, flat-rate billing is required.

Example: If Base Credits are set to 10, users will always be charged 10 credits, regardless of usage.


5. Categories

  • Description: Tags that help classify your app for easier search and organization.
  • What to Do:
    • Add relevant categories by typing a keyword and pressing Enter to confirm.
    • Use descriptive tags that reflect your app’s purpose.

Example: “AI,” “Chatbot,” “E-commerce”


6. Website

  • Description: A dropdown menu that displays a list of websites that have been added to the platform. This assigns the app to a specific website, creating a 1-to-1 relationship between the app and the selected site.

  • What to Do:

    • Select the appropriate website where this app will be used.

    • If no websites are listed, ensure that at least one website has been added to your account.

Note: While this selection is currently optional, it will become required in the near future. Eventually, the relationship between the app and the website will be automatically assigned based on the selected website during app creation.


7. Featured Image

  • Description: The main image that represents your app.
  • What to Do:
    • Upload an image with dimensions of 1600px x 300px.
    • Drag and drop the file or click Browse to upload.

Tip: Use a clean, high-resolution image that visually represents your app.


8. Subtitle

  • Description: A brief summary that appears below the app title on the App List Page, providing users with a quick overview of the app.

  • What to Do:

    • Enter a concise and informative subtitle (maximum 120 characters).

    • Ensure that the subtitle highlights the app’s core function or value.

Note: The Subtitle is intended for a short overview, while a more detailed description should be provided in the Description section, which is displayed on the App View Page.


9. Description

  • Description: A detailed explanation that appears on the App View Page, providing users with comprehensive information about the app.

  • What to Do:

    • Use this section to describe the app’s functionality, features, and any relevant usage instructions.

    • Format the content using available text editing tools to enhance readability.

    • Avoid duplicating the Subtitle information; focus on adding more in-depth details.

Note: This section helps users understand the full capabilities of the app, making it essential for conveying detailed information.


10. Example

  • Description: An optional section that allows adding an example or sample content related to the app. This is useful for demonstrating how the app works or providing a sample output.

  • What to Do:

    • Use the text editor to format and input the example.

    • Include relevant images, links, or text to illustrate the app’s functionality effectively.

Note: Adding an example can help users better understand the app’s purpose and expected results.


11. Export Options

  • Description: A set of options that allow exporting the app’s data in different formats.

  • What to Do:

    • Export .RTF (Including Images): Generates a .RTF file that includes both text and images.

    • Save Image: Exports the example or app results as an image.

    • Export Text: Outputs the app results as plain text.

    • Edit Results: Allows editing the results before exporting.

Note: Use these options to customize the export format based on your requirements.


FAQs and Troubleshooting

Q: What happens if I don’t add a slug?

A: A slug is auto-generated from your app title.

Q: Can I change the credit charge method after publishing?

A: Yes, but be mindful of any impact on existing users.