Bubble Convention
  • Introduction
    • About Bubble Convention document
    • About CitizenDev
  • Naming Cheat Sheet
  • Naming conventions
    • Page naming
    • Element naming
      • Groups
      • Reusable elements
      • Visual elements
      • Input elements
      • Custom states
      • Other notations
    • Style naming
    • Workflow naming & organization
    • Database naming
      • Data types & fields
      • Option sets
      • Privacy rules
  • Usage recommendations (upcoming)
    • Upcoming
  • Miscellaneous
    • Other recommendations
    • References
    • Copyright
    • Contribution guide
    • Changelog & version
Powered by GitBook
On this page

Was this helpful?

  1. Naming conventions
  2. Element naming

Visual elements

Visual elements are simple to name. Bubble has already done a great job at automatically naming text elements, for instance.

It is recommended to simply express the semantic meaning of the element as followed:

  • Non-dynamic elements: You should keep the element type first, and then its name, like usual: {Element type} {Name}. For instance: Button Submit Feedback.

  • Dynamic elements: Use {Element type} {Data field} or {Element type} {Operations}. For instance: Text username or Text firstName + lastName.

PreviousReusable elementsNextInput elements

Last updated 1 year ago

Was this helpful?