Skip to content

Answers use only the pages of this documentation, and every answer links to the pages it came from. Your question is sent to our answering service to be answered, and kept so the people who write these pages can see what readers ask.

✏️ Edit and refine

Direct editing, panels, branding, data, and integrations in the Ada builder.

Ada is not the only way to change an app. Use the preview and side panels for small, deliberate edits.

In select mode, choose a title, button, card, or image in the preview. The element panel exposes understandable settings such as text, color, size, spacing, alignment, icon, and destination.

A color change should make its scope clear:

  • This element changes only the selected element.
  • Everywhere changes the shared theme color and updates every screen that uses it.

Changes to data, navigation, permissions, and integrations deserve the same review as an Ada-generated change.

Testers should expect dedicated areas for:

  • Screens, including the screen structure and the data it loads.
  • Branding, including colors, fonts, and short-message styling.
  • Settings, including the app name, icon, platform identifiers, access, and publish readiness.
  • Languages, including translations and preview language switching.
  • Integrations, including maps, payments, sign-in, notifications, analytics, and error reporting.
  • Custom actions, for connecting the app to an external service.
  • Database, for collections, records, and relationships.
  • Publish, for builds and releases.
  • Versions, for restoring earlier app states.

The builder should keep the current app context when you open account, team, or invitation settings. A failure should identify the failed operation in normal language and offer a useful next action.