Skip to main content

Improvements to expand and edit records


Show first post

115 replies

ScottWorld
Forum|alt.badge.img+33
  • Brainy
  • 8764 replies
  • January 27, 2022
SergioCodes wrote:

Aaagh !!!

Why Airtable ?? Why??

I was writing 500 words complaining about this thing; I´m tired of complaining about bad decisions in terms of pricing, performance, etcetera.

So I will only say:

WE NEED FIELD TYPES

Look at these fields:

Both seem editable; I should click Customer Key and update it; guess what happens when I double click ???

GGGAASDSAND LSAD DAASDSAD ASD ADS N (me being frustrated with the keyboard )

So I´m kindly asking you to return the old expandable view, let´s pretend that the old is the new and everybody will celebrate :tada:

Thanks


Haha, great idea! Bring back the old view, and all of Airtable’s customers will celebrate the “new & improved” detail view!! :stuck_out_tongue_winking_eye:


kuovonne
Forum|alt.badge.img+27
  • Brainy
  • 6001 replies
  • January 27, 2022

Instead of simply bringing back the old view, could we have the people who designed the new View Sidebar look at the feedback people are providing and come up with a new design that is better than both the current and the previous designs?


Forum|alt.badge.img+4
  • Inspiring
  • 150 replies
  • January 27, 2022

i know i said i wasnt gunna say anything else but I wanted to jump on the thank you @Jordan_Scott1 train. you’re amazing and we love you and I’m sorry you’re the one who always ends up getting yelled at because the people above ya wont face us. you are strong my friend I couldn’t do what you do.


Cara_Van_Meter
Forum|alt.badge.img+12
  • Participating Frequently
  • 23 replies
  • January 27, 2022
SergioCodes wrote:

Aaagh !!!

Why Airtable ?? Why??

I was writing 500 words complaining about this thing; I´m tired of complaining about bad decisions in terms of pricing, performance, etcetera.

So I will only say:

WE NEED FIELD TYPES

Look at these fields:

Both seem editable; I should click Customer Key and update it; guess what happens when I double click ???

GGGAASDSAND LSAD DAASDSAD ASD ADS N (me being frustrated with the keyboard )

So I´m kindly asking you to return the old expandable view, let´s pretend that the old is the new and everybody will celebrate :tada:

Thanks


Like Coke Classic! :rofl:


Forum|alt.badge.img+12
  • Known Participant
  • 28 replies
  • January 27, 2022

The first reaction of casual users is : “it’s cool, it’s cleaner”.
Only hardcore users see the drawbacks of this new design.
This new design is going to please new users.

If you want to attract new end users… Good Move.
If you want to keep your community of makers… :( :frowning:

This is aligned with the new plan strategy.


Forum|alt.badge.img+19
  • Author
  • Retired Employee
  • 141 replies
  • January 27, 2022
Jen_Rudd wrote:

Control + F is not longer able to be used with the expanded record, this needs to be resolved as we can’t get the browser to search the record, only the grid below which is greyed out because the record is open. For long records, it is difficult to see the data you need.


Thanks for flagging this @Grow_With_Jen - this was an unexpected bug and the team is working on getting this fixed as quickly as possible!


Forum|alt.badge.img+6
  • Participating Frequently
  • 6 replies
  • January 27, 2022

Chiming in with all the other unhappy core users. Have built quite a large and interactive base for my CSO and likemany of the others spent the better part of the day thinking I had a bug in my browser that was making expanded records display wonky. Complain number one is no warning that such a substantial change was taking place. Complaint number two is if your enhancement looks so off that it is misperceived as a bug on the windshield instead of an improvement then perhaps said improvement needed a bit more user acceptance testing before being rolled out. NB Also as a 60-year-old eye glass-wearing user who uses Airtable 8 hours a day, the lack of division between the fields is extremely fatigue-inducing. I can only image how others with more severe vision deficiencies feel about the all white without a distinction or separation between fields.


Forum|alt.badge.img+19
  • Author
  • Retired Employee
  • 141 replies
  • January 27, 2022
Rebecca_Elam wrote:

i know i said i wasnt gunna say anything else but I wanted to jump on the thank you @Jordan_Scott1 train. you’re amazing and we love you and I’m sorry you’re the one who always ends up getting yelled at because the people above ya wont face us. you are strong my friend I couldn’t do what you do.


thank you, friends :heart:


Forum|alt.badge.img+13

Hi all –

Overall, I appreciate the intentions behind this update. Side-by-side labels and fields makes this a much easier screen to scan down, especially now that they are in mixed case. It is definitely a more usable layout. @Jordan_Scott1, please share that positive feedback with the team as well!

At the same time the layout is more usable, some of the design choices applied to it really have reduced its usability. However, they are also easy fixes, I think.

The “editability status” of fields is less clear than it used to be/could be. I can see how it is tempting to remove all the bounding boxes from the fields – it is much less cluttered. But the moment the designers felt they needed to add cue text (“Start typing…”) to the fields, it should have signaled the UI was not communicating enough information to the user. A user shouldn’t have to read something to know a field can be edited.

  • Potential solution for editable fields: A low-contrast key line around editable fields plus lightening the background color on mouseover would probably address this. And if the field is a drop-down, the drop-down arrow should also always be there. Together those changes would communicate a users’ possible interactions and clarify field type.

  • For all fields: I agree that the icons for field type should come back – they are useful in the grid and here.

(Aside: I wonder if part of the challenge for the designers is the fact that the item view sheet is gray. That choice reduces the designers’ options while simultaneously reducing the contrast – and thus the readability – of the UI. I haven’t done any calculations on this, but I wonder how accessible some of these low contrast gray-on-gray choices really are.)

Lastly, a broader suggestion Re the record detail UI: It might be worth asking why this part of the UI is a modal which appears in front of the entire interface. That choice doesn’t seem to add much utility – you can barely see other records behind it – while simultaneously limiting the available space for the expanded record itself. Instead, the record could expand to be in front of the grid/view space itself. An ‘x’ close button in the right top corner would close the record and return to the grid behind it. The benefits of this would be:

  • More space! A responsive layout in this context could even permit two columns of fields on larger screens.
  • The details sidebar would be on the right, as it is now, mimicking the automations and apps sidebar, which would make the UI generally more consistent.
  • easier access to navigation - one click to a view or table.

There are some questions to consider (Does the open record persist if I change view or tab and return?) and some fun possibilities (Pin a record open/minimized as a window like gmail), but I thought it might be an idea worth sharing.


Forum|alt.badge.img+19
  • Inspiring
  • 3264 replies
  • January 27, 2022
David_Solimini wrote:

Hi all –

Overall, I appreciate the intentions behind this update. Side-by-side labels and fields makes this a much easier screen to scan down, especially now that they are in mixed case. It is definitely a more usable layout. @Jordan_Scott1, please share that positive feedback with the team as well!

At the same time the layout is more usable, some of the design choices applied to it really have reduced its usability. However, they are also easy fixes, I think.

The “editability status” of fields is less clear than it used to be/could be. I can see how it is tempting to remove all the bounding boxes from the fields – it is much less cluttered. But the moment the designers felt they needed to add cue text (“Start typing…”) to the fields, it should have signaled the UI was not communicating enough information to the user. A user shouldn’t have to read something to know a field can be edited.

  • Potential solution for editable fields: A low-contrast key line around editable fields plus lightening the background color on mouseover would probably address this. And if the field is a drop-down, the drop-down arrow should also always be there. Together those changes would communicate a users’ possible interactions and clarify field type.

  • For all fields: I agree that the icons for field type should come back – they are useful in the grid and here.

(Aside: I wonder if part of the challenge for the designers is the fact that the item view sheet is gray. That choice reduces the designers’ options while simultaneously reducing the contrast – and thus the readability – of the UI. I haven’t done any calculations on this, but I wonder how accessible some of these low contrast gray-on-gray choices really are.)

Lastly, a broader suggestion Re the record detail UI: It might be worth asking why this part of the UI is a modal which appears in front of the entire interface. That choice doesn’t seem to add much utility – you can barely see other records behind it – while simultaneously limiting the available space for the expanded record itself. Instead, the record could expand to be in front of the grid/view space itself. An ‘x’ close button in the right top corner would close the record and return to the grid behind it. The benefits of this would be:

  • More space! A responsive layout in this context could even permit two columns of fields on larger screens.
  • The details sidebar would be on the right, as it is now, mimicking the automations and apps sidebar, which would make the UI generally more consistent.
  • easier access to navigation - one click to a view or table.

There are some questions to consider (Does the open record persist if I change view or tab and return?) and some fun possibilities (Pin a record open/minimized as a window like gmail), but I thought it might be an idea worth sharing.


Classic or Experimental?

It’s really great to see all the passionate feedback and great ideas for improving the new expanded view. Such changes fall into the innovator’s dilemma - users want each new version to remain the same, but be wholly different. Often, abrupt UX changes are like elections - at least 50% of the audience will be disappointed.

It’s a paradox, of course. However, experienced engineering teams know that they can easily disappoint near-zero per cent of the users by simply adding a user setting -

  • Classic
  • Experimental

I have a much simpler ask - please inform the dev team when it comes to changing long-standing UI features, almost every user will be comfortable with a “classic” and “experimental” option. Users are free to choose either without disrupting their individual comfort and use cases.

Most advanced software asks which you prefer and integrates feedback options in the selection process. When they opt-out of the experimental version, you needn’t know anything more; the user preferred the classic UX. This alone is a data point and it’s captured effortlessly while also giving the user exactly which UX they prefer.

Example…


Forum|alt.badge.img+6
  • Participating Frequently
  • 9 replies
  • January 27, 2022

@Jordan_Scott1 Your work (and the work of your team) is hugely appreciated, and I am a huge supporter of Airtable’s excellent and consistent progression, but there are some serious missteps here. We urgently need to see a return of the icons to clarify (for example) what is a formula and what is editable. I also echo previous posts about confusion over the ‘Start typing’ notification when a field might be automated. As an Airtable user of over 4 years, this is the first time that I feel like a development needs to be entirely rolled back.


ScottWorld
Forum|alt.badge.img+33
  • Brainy
  • 8764 replies
  • January 28, 2022

I totally agree with everything that @Bill.French said. You can’t blindside users like this and make the product infinitely more difficult to use. Give people a choice to opt-in to experimental features, just like Google does, and then refine those experimental features based on user feedback.

I mean, at the very least, the field type icons need to come back. It’s unusable without those.

Then we can start addressing the rest of the issues. :stuck_out_tongue_winking_eye:


  • Participating Frequently
  • 7 replies
  • January 28, 2022
kuovonne wrote:

I would like to extend a welcome and thank you to all of the users who normally do not visit this forum, but came here anyway to express their feelings about this feature change.

@Dara_Brannan @Jeremy_Luebke @Jeremy_John_Thompson @Admin_Promis_Jure

It is no surprise that third party consultants like myself provide feedback here. I think it says something that the rest of you felt strongly enough about these changes to either dust off your community account or to create a new account to have your say.

So far the only Airtable employee to post in this thread is @Jordan_Scott1 who started this thread. I am quite sure that she has read and taken to heart each and every one of your posts, even if she is not at liberty to reply at the moment. I am sure she is doing her best to communicate your feedback to the people who actually make design decisions like this.


Yeh and also, I appreciate your effort to make it known. My guys are pretty upset, and im struggling, so i appreciate your well thought out and proffesional analysis of it and your decent reporting of it here in the forum, Many of us are too busy and hectic to take the time to do it so well, so sincerely thank you!


  • Participating Frequently
  • 7 replies
  • January 28, 2022
David_Solimini wrote:

Hi all –

Overall, I appreciate the intentions behind this update. Side-by-side labels and fields makes this a much easier screen to scan down, especially now that they are in mixed case. It is definitely a more usable layout. @Jordan_Scott1, please share that positive feedback with the team as well!

At the same time the layout is more usable, some of the design choices applied to it really have reduced its usability. However, they are also easy fixes, I think.

The “editability status” of fields is less clear than it used to be/could be. I can see how it is tempting to remove all the bounding boxes from the fields – it is much less cluttered. But the moment the designers felt they needed to add cue text (“Start typing…”) to the fields, it should have signaled the UI was not communicating enough information to the user. A user shouldn’t have to read something to know a field can be edited.

  • Potential solution for editable fields: A low-contrast key line around editable fields plus lightening the background color on mouseover would probably address this. And if the field is a drop-down, the drop-down arrow should also always be there. Together those changes would communicate a users’ possible interactions and clarify field type.

  • For all fields: I agree that the icons for field type should come back – they are useful in the grid and here.

(Aside: I wonder if part of the challenge for the designers is the fact that the item view sheet is gray. That choice reduces the designers’ options while simultaneously reducing the contrast – and thus the readability – of the UI. I haven’t done any calculations on this, but I wonder how accessible some of these low contrast gray-on-gray choices really are.)

Lastly, a broader suggestion Re the record detail UI: It might be worth asking why this part of the UI is a modal which appears in front of the entire interface. That choice doesn’t seem to add much utility – you can barely see other records behind it – while simultaneously limiting the available space for the expanded record itself. Instead, the record could expand to be in front of the grid/view space itself. An ‘x’ close button in the right top corner would close the record and return to the grid behind it. The benefits of this would be:

  • More space! A responsive layout in this context could even permit two columns of fields on larger screens.
  • The details sidebar would be on the right, as it is now, mimicking the automations and apps sidebar, which would make the UI generally more consistent.
  • easier access to navigation - one click to a view or table.

There are some questions to consider (Does the open record persist if I change view or tab and return?) and some fun possibilities (Pin a record open/minimized as a window like gmail), but I thought it might be an idea worth sharing.


bam ,spot on. Thank you for explaining it so authoratively, i completely love this post.


Forum|alt.badge.img+11

Why was this not announced ahead of time? My users and I have wasted time trying to puzzle out why things have ‘gone wrong’. Was it not piloted? I agree with all the comments below and strongly urge you to reverse this change immediately and go back to the drawing board. My 15 users utilize expanded views all the time and constantly navigate between tables from them.


Forum|alt.badge.img+10
  • Known Participant
  • 11 replies
  • January 28, 2022

The new look is awful according to my colleagues - and I agree. They are all telling me it is more difficult to edit in expanded records. Normally they love the improvements you regularly make. Not this one. please change it back or give us an option to switch it off.


Forum|alt.badge.img+10
  • Known Participant
  • 11 replies
  • January 28, 2022
Margaret_Picker wrote:

Why was this not announced ahead of time? My users and I have wasted time trying to puzzle out why things have ‘gone wrong’. Was it not piloted? I agree with all the comments below and strongly urge you to reverse this change immediately and go back to the drawing board. My 15 users utilize expanded views all the time and constantly navigate between tables from them.


Us too. My colleagues blamed me for this awful change


Forum|alt.badge.img+3
Julien_Mottet1 wrote:

The first reaction of casual users is : “it’s cool, it’s cleaner”.
Only hardcore users see the drawbacks of this new design.
This new design is going to please new users.

If you want to attract new end users… Good Move.
If you want to keep your community of makers… :( :frowning:

This is aligned with the new plan strategy.


That was exactly my reaction.

Huh clean new interface.
Checks Airtable forums for an update.
Returns to Airtable
Yikes.


Justin_Barrett
Forum|alt.badge.img+20

Gotta chime in on this. As @David_Solimini said, the layout is an improvement, but many other things are not.

  • Don’t like the dashes for empty fields (as @kuovonne said, it’s not just here; they’re annoying in interfaces as well)
  • Bring back the icons, please?
  • Currently a field only becomes “visible” when you mouse over it. It should be visible all the time. That said, I like how non-editable fields (formulas & other calculated fields, locked fields, etc.) don’t “highlight” upon mouseover, but seeing where the field is would still be nice. Maybe change the cursor to a lock when mousing over any non-editable field?

Simple and clean is great, but clarity is also important. The new design is clean and unclear, and lack of clarity means it’s not truly simple.


I’m sorry but the new expanded records are SO hard to see! Everyone in my office has been struggling. I can’t understand why everything is white and indistinguishable.


Forum|alt.badge.img+2

OMG, it’s horrible. I can’t see anything. I may have to give up AirTable unless this changes back.


This update is far from an improvement. Without backgrounds or borders around editable fields, it’s difficult to see where to edit at all. I agree with other users comments, regarding the “start typing” prompts which only create confusion for other team members. Alongside project planning our teams use Airtable for content planning which is image heavy. Now when the activity column is open, image files and other docs stack one on top of the other taking up far more space in the expanded view. It makes for a very long scroll. Please reverse the changes or give users the option to return to the “classic” view.


Everything about the new expanded record field feels like it was created for the look rather than use. Giving users the option to customize how their expanded fields look would be great but this update feels like a step back. Echoing previous sentiments here, I thought there was something wrong with my editable rather than this being an update.

Having the field names to the left is a simple modification however with no backgrounds, borders or other such contrast in the fields it creates incredible strain in following where you are in a record.

Removing the field type icons ensure confusion when filling out records.

While the enlarged attached files field could be of use again maybe give the option to toggle between? Our company uses AT for creative and content management so sometimes we could have over 20 attachments in one field which creates a doom scroll.


Jen_Rudd
Forum|alt.badge.img+14
  • Inspiring
  • 49 replies
  • January 28, 2022
Jordan_Scott1 wrote:

Thanks for flagging this @Grow_With_Jen - this was an unexpected bug and the team is working on getting this fixed as quickly as possible!


Thanks, @Jordan_Scott1


Forum|alt.badge.img+4
  • Participating Frequently
  • 5 replies
  • January 28, 2022

I echo what so many others have added here, that these improvements, while I’m sure well-intentioned, are making it more challenging to navigate in an expanded view.

The background / border issue for me seems the most egregious, as that color contrast was necessary for my eyes. I could do without the ‘start typing…’ hint text, as well. Icons are a MUST for me.

Just adding my feedback along with others, to hopefully enhance this experience. Yes, any change will come with transition, but we lost some necessary functionality with this change.


Reply