Features and packages
Ask the agent in a thread for the feature that you want, or for a package by its name. The agent builds the feature into a copy of your app, and you check it before you push.
What to ask
To ask for a feature, describe what people can do with it and the screen that it belongs on.
To ask for a package, name the package and say what to use it for.
What the agent can’t try
To add a feature such as maps, ask the agent in a thread. While the agent builds a feature like this, it tells you that it can’t try the feature.
Agent questions
If the agent needs a decision from you, it asks you in a card, such as a Question card, above the message box. See Agent questions.
Review
After the agent finishes, read the turn’s Summary and review its Changes. Check the affected screens in Screens, and try the change in Preview. If the change uses records or sign-in, test it with the thread’s own data in Data.
After you push a backend change, check the result in Backend.
When a turn changes your app’s packages, its Summary shows a row that names the packages in plain words, for example Fl chart for fl_chart. What the row says depends on the change:
- If the turn only adds packages, the row says New add-on, or New add-ons for more than one.
- If the turn only removes packages, the row says Removed add-on or Removed add-ons.
- For any other package change, such as adding one package and removing another, the row says Updated add-on or Updated add-ons.
Push
When the feature works as expected, push the thread to your app. See Push.