All product updates

No box in Cake stops you typing

Every box that used to stop taking letters takes them now. Cake leaves your Google events alone except for the time. A busy Google event you add after your times go out stops a client booking over it. Quick add can send a time for the client to approve.

No box in Cake stops you typing

An artist wrote past the limit on a note and the keyboard went dead, with nothing on screen to say a limit was there. Every cap that blocked keystrokes is gone.

The note on your request form takes 20,000 characters. Chat, the approve note, and the message you send with a decline take 10,000. A small count appears near the end, and past the ceiling a line names the box and the number while the box keeps taking your words.

Three boxes used to cut what you typed and say nothing about it: the heading on a note, the label on a question you added, and the title of a consent document. They keep every character now.

A client picking several long style options could not send the form. That is fixed. A consent document over the limit used to be refused with "This document needs a title and its full text", which sent you looking for text you had already written.

Close Cake fully and open it once to pick this up.

Your Google events stay yours

Available to artists who have connected Google Calendar.

Two updates on September 4 put artists' colors and notes back to default, because Cake was writing the whole event on every change. It writes only the time and its own block now, so a color you set, a title you rewrote, and a line you added under Cake's block all survive a reschedule and every update after it.

Change the time on Google and Cake puts it back, because the booking is what you and your client agreed. Your request thread says so when it happens.

A cancelled session keeps its event, marked Cancelled, with the time freed and your notes kept, so you can still find who cancelled.

A Google block stops a client booking over it

Available to artists who have connected Google Calendar.

Add a busy event to Google after your times go out, and the client who picks that time is turned away. Cake reads your calendar for that one time at the moment they tap.

If Google cannot answer, the pick is refused and your times stay open, rather than booking someone into an hour you may already be working. Your request thread names the time that was refused.

Quick add can send a time for the client to approve

Quick add has two exits now. Book it yourself, or send the time and let the client approve it. Draft the session, set the price and the deposit, read the address the link goes to, and send.

The client gets one link carrying that time. What their tap does follows the deposit you picked:

  • collect it outside Cake: their pick holds the time and your confirm books it
  • waive it: their pick books, unless you confirm every booking

Collecting the deposit in Cake is still not open, and Cake says so when you pick it. A client with no email address gets a link you copy and send yourself.

Calendar opens where you left it

Pick Month and a date, walk away, come back through the side rail: Calendar opens on Month and that date. A refresh holds it. So does a window you opened fresh. A link that names its own view and date still wins.

A session keeps the time zone it was agreed in

The hour on a booked session belongs to that session, not to your account. Move to another zone in settings and every session already agreed reads the hour your client was given: on the client's page, in the booking and reschedule mail, on the calendar file, and on the Google event. Sessions already on your books were stamped for you, so there is nothing to rebook and nothing to reconnect.

Your account zone still lays out your week and decides what today means.

Older Google events read the client's name

Available to artists who have connected Google Calendar.

Every Cake event already on your calendar was rewritten once with the piece, the booking, the client, and your own question answers. Their titles read the client's name with the placement and style. No Cake event says "Session with" any more, including in the calendar feed you can share.

One studio, and no way back to the old one

The retired studio screens are out of the code, and the switch that used to serve them is gone with them. An old bookmark to that address now says nothing lives there. On a phone, your Payments room was still serving a retired screen with its own stale wording; it serves the studio's own room now.

  • The outline Requests and Calendar draw while they load now lands its boxes where the loaded screen puts them, measured to within two pixels on a phone.
  • A test that failed at random and held up a release stopped failing.
  • The browser tests were cut to the one that gates a merge, and that gate is back on for every change.
  • Cake's own checks stopped running the whole suite on every change, so a fix reaches you sooner.
  • The packages Cake runs on were updated, and the alerts against them are at zero.
  • The instructions Cake's own agents follow now say how to credit an artist who asked for a change, how to write a list, and when a change is ready for a person to test.

With feedback from