She got everything done. We had a customer and bookings database at the end, about 30 minutes in actually. But it confused her in places, bugged in other places, and did not wow her in any way.
[ ] Did not notice the Save button on the record row. Clicked away and lost her data. I had to explain to her that there was a small save button on the right hand side of the row
[ ] Added Customer and Booking table as first action.
[x] Added "Bookings" as a "Link to other record" field to Customer. While Cozemble is meant to link from Customer to Booking, this is what she is used to doing in Airtable, and it (I guess?) permits viewing and editing data from either end of the relationship. Need to look into this.
[ ] It became impossible to rename this field - the Customer.Bookings field. It kept staying as "Field 5".
[x] Opened the table edit dialog (by clicking on the caret beside the Customer table name) then clicked the Booking table name, and the table edit dialog stayed on Customer
[ ] Added a field (Bike Make) to Booking, did not click Save, clicked Add Field again, and things got messed up
[ ] When it came to adding the Notes field to the Booking, she did not see the "Multiple lines of text" checkbox under text, she was expecting to see Field types of "Text", "Long Text" and "Rich Text", which is Airtable lingo.
[ ] She typed dates into text fields, rather than use the date picker. I think she did not see the date picker icon, and/or was expecting one to pop immediately. Additionally, when typing the date, as soon as she entered the first character of the year, the input submitted the value and tabbed to the next field.
[ ] She wanted tab and keyboard arrow navigation when navigating the data cells i.e. not in edit model. Because she wanted to copy and paste a value from one cell to another
[ ] She wanted to add a second booking for the same customer with a different bike. Her instinct was to create another row.
[ ] When filtering on dates, she wanted abbreviations for common date options, like today, tomorrow, next Wednesday
[ ] She also expected to be able to free text search on dates. If we're going to do this, identifying which date format is in effect (in the user's mind, not in system config) will be a challenge.
[ ] When she added a new customer when adding a new booking record, the new customer did not get put into the Booking.Customer cell. This may be due to the fact that Customer was a bit messed up with the Customer.Bookings field, but need to check.
[ ] She did not get "Sub sections" at all. When I asked her about it, we were looking at Customer data. She said maybe it is a sub account, or an address book. So she, like all others, thought this was a data entry thing, not a model building thing.
[ ] She expressed a need for an Autonumber field, a RecordID field, and a formula field so she could make ID fields of her own format. The RecordID field was so she could make urls to external services with ?recordId=${RecordId} in it. The custom format ID fields is so she can make friendly IDs, like YYDDDNNN
[ ] She expressed a need for a drop down field, single select for something like "Employee.Level" and multi select for tagging.
[ ] She asked what does Unique. She was trying to add Level to an Employee record that she added as a sub record of Customer, and she was reaching for the ability to make level a drop down list. But it did make me wonder about the understandability of Unique in a nested context. Logically its no different to Customer.Email being unique at the top level, but it feel weirder when nested.
She got everything done. We had a customer and bookings database at the end, about 30 minutes in actually. But it confused her in places, bugged in other places, and did not wow her in any way.
?recordId=${RecordId}in it. The custom format ID fields is so she can make friendly IDs, likeYYDDDNNN