Changelog
What changed, when, and why it matters to a store. There are no version numbers, because a version number tells you nothing about whether a change affects you. Each entry says what was added, fixed or changed, and what a merchant or a shopper will notice.
-
Tamil and Hindi keyboards no longer send half a word
Tamil and Hindi keyboards sent half a word. The message box now waits for the word to finish.
-
Say what went wrong after a thumbs-down
After a thumbs-down, the shopper can say what went wrong. The shopper’s words appear in the review queue.
-
Sign-up, log-in and plan buttons in the chat
The assistant can open your own account, cart, checkout or plan page. On WooCommerce it opens inside the chat and notices when the shopper has signed in or ordered.
-
The conversation follows the shopper across pages
A chat started on one page is still there on the next, and in a new tab.
-
Product cards load in two store requests instead of eleven
The row of products under an answer appears in one go instead of filling in one card at a time, and a product a shopper has already seen in the chat comes back at once.
-
The assistant no longer links to pages that do not exist
A visitor could be sent to a page on your site that does not exist. A link into your own site is now only ever a page the assistant has read, so every link it offers opens.
-
Phones get the whole screen
The chat fills the visible screen and stays above the keyboard.
-
Products sold by weight or colour
Products with options now carry them through the whole flow. The catalogue stores the real price span rather than the cheapest variation, the assistant states the range and asks which option before adding anything, and cards show the choices as chips that resolve to the variation the cart needs.
-
Cards match the answer that carries them
Product cards were chosen from whatever retrieval returned, so a one-word query could card a pickle beneath an answer about powders. They are now chosen from the products the reply actually names, and a reply that names nothing shows no cards.
-
A slimmer scrollbar, and a heading on every page
The chat panel’s scrollbar was rendering at the browser default, 15px down the side of a 380px panel. It is 10px now. In the console, every page has a heading and a sentence saying what it is for; two of twenty-two had one before.
How to read an entry
Every entry is labelled added, changed or fixed. An added entry is something new you can use. A changed entry alters how something you already use behaves, and says what you need to do, if anything. A fixed entry describes a bug, what it did, and on which stores it could have shown up. We describe bugs plainly because a changelog that only lists improvements is not a changelog.
Why we keep it
A merchant should be able to find out when the assistant started behaving differently, and why. When a shopper reports something odd, the first question is often “did anything change?”, and this page answers it with a date. It also keeps us honest: a change that is embarrassing to describe is usually a change worth reconsidering.
What does not appear
Internal refactoring, dependency updates and anything a merchant or shopper cannot notice. A changelog full of those makes the entries that matter harder to find. If a change could alter an answer, a price shown on a card, the look of the widget or anything in the console, it is listed.