Buzzy Documentation
  • Welcome to Buzzy
  • Getting Started with Buzzy
    • Getting Started Guide
      • 1. Starting with Buzzy AI
      • 2. The Buzzy Workspace
      • 3. Create a new app
      • 4. Preview and edit your app
      • 5. Manage your app
      • 6. Import your app to Figma
      • 7. Using Buzzy with Figma
      • 8. The Buzzy Figma plugin
      • 9. Creating a simple app
      • 10. Screens and navigation
      • 11. Forms, fields and data
      • 12. Data-driven menus & content
      • 13. Data edit and delete
      • 14. Search, sort and filter
      • 15. User login and registration
    • Buzzy AI or Figma first?
  • Working with Buzzy
    • Buzzy AI
      • About Buzzy AI
      • Kickstart with AI
      • Enhance with Figma
      • Extend with Code
      • Example prompts
      • Tips
      • Troubleshooting Buzzy AI
      • AI tokens and pricing
    • Buzzy for Figma
      • About Buzzy for Figma
      • Learning Figma
      • Creating a new app directly in Figma
        • Step by step version
      • Automarkup
      • Responsive layouts
      • Responsive layout checklist
      • Overflow and scrolling
      • Forms and fields
      • Images and galleries
      • Logging users in to your app
      • Theming
      • Troubleshooting Buzzy for Figma
      • Plugin error messages
    • Buzzy Deployment & App Stores
      • Setting up your custom Buzzy app
      • Connecting your own server
      • Apple & Google App Stores
    • Buzzy Marketplace
      • Buzzy Accreditation
    • Buzzy Project Guide
    • Buzzy App Examples
      • Buzzy Templates
      • AI-Powered Chat App
      • AI-Powered Custom T-Shirt App
      • AI-Powered Strategy App
      • AI-Powered Stock Portfolio App
      • Golf Course Finder
      • Personal Finance App with Figma AI
    • FAQs
  • The building blocks
    • Datatables, Fields & Data
      • Introduction to Fields
      • Basic Fields
        • Text
        • Number
        • Date
        • Location
        • Toggle
        • Checkboxes
        • Checklist
        • Selectlist
        • Rating
        • Attachments
        • Images
        • Signature
        • Audio Recording
        • Embedded Link
      • Advanced Fields
        • Formula
        • Sub tables
        • Linked Table field
        • Button
        • Teams
        • Payment
        • Notification
        • Event
        • User Vote
      • Display Fields
        • Header
        • Display Text
        • Image
        • Divider
      • Metadata Fields
        • Author Name
        • Author Phone
        • Submitted
      • Filter Controls
        • Viewers
        • Tags
        • Condition
      • External Fields
        • IBM Connections File
        • Box File
      • Sort Fields
      • Formulas
      • Datatable to Datatable Relationships
      • Security and Access Control
      • Displaying a field based on the values of other fields
      • Hiding a field based on role using a display formula
      • Importing data from a text file
      • Importing data from a URL
      • Import data from Datatable
      • Export data using Chrome
      • Export data in Browser
      • Export data using Safari
      • Datatable Field Type - Cheat Sheet
      • Troubleshooting Fields & Data
    • Code widget (custom code)
      • Code Widget Fields - Advanced Guide
      • New Async API + React HTML Components
      • Examples
        • Image Galley Slideshow
        • Ratings Average and Distribution
        • Event Locations Map
    • Analytics
  • Troubleshooting
    • App Error Codes
      • Action Error
      • App Not Found
      • Component Missing
      • Component Not Set
      • Component Settings Error
      • Datatable Not Found
      • Datatable Not Set
      • Field Not Found
      • Field Not Set
      • No App Selected
      • No Context Name
      • No Screens Found
      • Runtime Exception
      • Screen Not Found
      • Screen Not Set
    • Troubleshooting Buzzy AI
    • Troubleshooting Figma
  • REST API
    • Buzzy REST API
      • Integrating 3rd party applications
      • REST API
        • login
        • createappwithprompt
        • MicroApp Data Operations
          • microappdata
          • microappdata/row
          • insertmicroapprow
          • updatemicroapprow
          • removemicroapprow
          • microappchild
        • User & Organization Operations
          • userid
          • insertteammembers
          • teammembers
          • insertorganization
          • insertteam
        • enforceteammembership
      • Node.js API Client
      • Datatable Rules
      • Datatabledata Tutorial
      • Integrating with Mailchimp
      • Python Access Datatable
  • Advanced Deployment Settings
    • Installation
      • Pre-installation Planning
      • Deployment
        • Introduction to deployment
        • Minikube install guide
        • AWS ECS Fargate install guide
        • HCL Connections install guide
        • Azure AKS install guide
        • Windows container install guide
      • Buzzy settings
      • Whitelabelling Buzzy
      • Certificates
      • Release Management
    • Performance and Reliability
    • Security
      • Platform
      • Users and Roles
      • Datatables
      • Audit Trail
Powered by GitBook
On this page
  • Optimising your initial prompt
  • Optimising your change requests
  • Understanding the Brief tab (Workspace & Figma plugin)
  • Identifying the handover point between the AI assistant and the user
  1. Working with Buzzy
  2. Buzzy AI

Tips

PreviousExample promptsNextTroubleshooting Buzzy AI

Last updated 5 months ago

Optimising your initial prompt

When generating your app brief, try to include some basic description of your data relationships in your prompts. This will help make sure your data model includes the relevant relationships. This is especially important if the app requires complex many-to-many relationships. Some examples of prompts you could use:

  • Each recipe can have multiple reviews. Each review is linked to one recipe.

  • A customer can have multiple projects, and a project can have multiple customers.

  • Each dog has only one breed, but a breed can be associated with multiple dogs.

Good questions to ask yourself when creating your prompt:

  • What kind(s) of users will be using the app? Is there one general user type or do I need to distinguish multiple users (e.g. customer vs admin, patient vs practitioner, teacher vs student etc.)

  • What are the relationships among my data? Can one object be linked to multiple other objects? Can one object be linked to only one other object?

  • What concrete actions would a user be expected to perform when using the app? What verbs can I use to describe those actions (e.g. “Users should be able to submit a review/deactivate a program/book an appointment…”)?

Optimising your change requests

The AI Assistant can help you make some changes to your app including editing the data modal, the app name or even do some simple design changes. To help the AI Assistant understand your change request, explore these to get an idea of what to ask and how to ask it.

Understanding the Brief tab (Workspace & Figma plugin)

The functions in the app brief represent the main features of the app and the actions that a user would be expected to take in the app. In this context, the functions do not relate to UI specifications (e.g. “The app should have a navigation bar”, “The user should be able to access a dashboard”).

Identifying the handover point between the AI assistant and the user

In using Buzzy AI, we want to emphasise the importance of collaboration between you - the user - and the Buzzy AI assistant. It is crucial to understand that the AI assistant serves as a powerful co-design partner, enhancing and streamlining the app creation process. But for most complex use cases, it does not encompass the entirety of the process and is not a substitute for your creative input.

It is important to recognise the handover moment - the point where you have maximized the AI assistant's capabilities and are ready to take the reins manually. After you've published the first version of the app, which features the core functionalities, it is generally time to start iterating and refining using your own expertise.

Fine-tuning such as UI improvements and customisation will fall under your purview as the app's designer and will have to be implemented manually. You'll find some guidance on that topic .

example prompts
here