Yes, a Data Type is a Table. A Field is a Field. A Thing is a Row/Tuple/Object.
Worth mentioning “Field Type” and how that can implement Relationships. So beyond “text” and “number” a field type can take the type of an existing Data Type. So instead of a foreign key, we are setting the field to be a reference to another Thing. We could have Vehicle, which could have a field Manufacturer, or type Manufacturer … where there is another Data Type called Manufacturer. And we Set that field (on Vehicle) to be a particular row on the Manufacturer table.
This becomes powerful in Bubble because it enables the natural language data access. So for example, if Manufacturer had “Name of Sales Contact” … and we are displaying a list of Vehicles, we can navigate the relationship simply by using an apostrophe. So we can use Vehicle’s Manufacturer’s SalePerson’s Email Address for example. In SQL that would need a query, and you would need to know the foreign keys.
Lists are basically Bubble’s way of implementing “One To Many” relationships.
So you can have a list of texts. And as you go along your can add/remove texts from that list.
Where they really come into their own is when you have a list which has a field type which is another Data Type.
So … if you have a field on User called “Friend” which is type User and also a list, then you can use the same language as above. A repeating group that lists out Current User’s Friends.