Move from full UI refreshes to component-level rendering

One of the pieces of feedback we receive from clients most often is that Noloco feels “clunky”.

When we meet with these users, they show us a similar demo each time.

They make a change somewhere on the screen, then start to make a change to something else, but their second change gets cancelled in favour of a repaint.

Compare this with a tool like Airtable where changes are happening in parallel; I can start editing Field 2 while the changes to Field 1 are saving, and those two things will never interrupt each other.

This is most obvious in a table/grid of records where you want to make changes to several of them in quick succession.

I appreciate that this is presumably a very, very large development ticket, but if you zoom ahead to what the competition are doing, they have focused efforts on QOL improvements like this because Users feel like their software here is “fast” and “keeps up with me”, it’s never in the way.

Do you have anything like this on the roadmap?

2 Likes

Thanks for the feedback @Russ - as you said, not just a one-and-done, and something we’re very much looking to invest in (and have to be honest).

Expect some improvements in the areas around bulk editing and inline editing in the next couple of months

2 Likes