Tips

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 example prompts 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 here.