Release notes
What changed in About Time Tours, in the order it changed, written as what it does for you rather than what it did to the code. Each entry is dated by the day the work landed in the app.
Recent months skew towards fixes. That is deliberate: the product is in beta on real showing days, and a stop that will not load matters more than a feature nobody asked for yet.
The app is published on the App Store and on Google Play, and it is in beta on both. That is a statement about pace rather than a disclaimer about quality. Things change often, some of them appear in a narrow form first, and this page is where they get written down.
Ordinarily a release-notes page pins each entry to a version. This one does not, and the reason is worth being straight about: the builds currently sitting in the two stores were cut from a working copy that had uncommitted changes in it. The exact contents of those binaries cannot be reconstructed from the repository, so a version number printed next to an entry would be a number nobody here could stand behind.
Production builds are now required to come from a committed tree, so this gets easier from here. Until the first store release under that rule, treat every date below as the day the work landed in the app, not as a promise about which binary you happen to be holding.
5 changes
If you signed in with Apple and chose Hide My Email, onboarding rejected the address Apple issued you and demanded a different one, then walked you through a name step Apple had already answered. Relay addresses are now treated as the ordinary deliverable addresses they are, and the name step is skipped outright when Apple supplies both parts of your name.
A client asks to see three houses. Approving the first one used to drop you into an empty tour with none of the properties in it, and you went and found the other two by hand. Approving now creates the tour and opens the editor with every pending request from that client already in it as a stop, thirty minutes apart, in order, with the client attached. Removing a stop you did not want is one tap. Choosing an existing tour instead still adds only the request you opened.
After a framework upgrade both map surfaces laid out at zero height and drew nothing. The search screen showed "Zoom in to see listings" over an empty rectangle and drawing your own area gave you a blank canvas. There was no error and no warning, which is why it took a device build and a process of elimination to find. Both maps size themselves properly now.
Opening the tour editor creates a draft immediately, and leaving by swipe-back, the Android back button or a tab stranded it. Those rows then turned up as "New Tour, 0 stops" in every tour picker. The editor now cleans up whichever way you leave it, and strays from before the fix are removed on refresh. The bar is deliberately narrow: still a draft, no stops, never renamed from the default, and more than a day old. A draft you named, dated or put a property into is yours and is left alone however old it is.
A client you had invited but who had not signed up yet rendered as a bare hairline in your client list — the card laid out at zero height, so all that painted was its border. Those rows are back, and a client with no name yet is labelled there with the email you typed instead of reading "Pending Client". Separately, text scaling is capped at 130 percent, so at accessibility text sizes names, chips and emails truncate with an ellipsis rather than clipping mid-letter.
4 changes
Working two service areas produced one blended feed with no way to tell which area a listing came from. Once you keep more than one territory, activity is sectioned by territory name; with a single territory the feed still reads by day, because one section wrapping everything tells you nothing. Sections follow the order you keep your territories in rather than what moved most recently, so the feed does not reshuffle itself between refreshes, and a listing that sits inside two overlapping territories appears under both — which is the truthful answer for each of them.
Listing prices are now compared between syncs, so a cut or an increase shows as its own filter alongside new and pending, with each row naming the previous price and the size of the move. The MLS feed exposes no price history to load in behind this, so it fills in from the day tracking started rather than showing changes that happened before it. Give it a few weeks in a busy area before judging it.
Draw a service area on the map, or list its ZIP codes, and the dashboard gains a Your Territory section plus a full activity feed of what came on the market and what went pending inside it over the last seven days. ZIP-code territories are new here too, for the agent whose farm is three postcodes rather than a shape.
Lead routing only matched service areas defined as a centre point and a radius, and the app only ever creates drawn ones — so a territory you drew on the map never received a lead at all. Routing now tests the lead against the drawn shape itself, and matches ZIP-code territories against the postcode on the request.
3 changes
When a listing was sold, cancelled or withdrawn, the stop it belonged to lost its details and your client's itinerary had a hole where a house used to be. Tour and itinerary views now keep loading those listings, so the stop still reads as a real address with real photographs and the day still makes sense to the person looking at it.
A tour, and a tour invitation your client receives, now carry an Add to Calendar button. Google and Outlook open a pre-filled event in the calendar's own web page; Apple Calendar gets a standard .ics file, or on a phone the system add-event dialog with its own Save button. Settings carries a Default Calendar App, so you pick once instead of answering the same question every Saturday.
Drive time is not the only gap in a tour day — there is parking, there is the conversation on the pavement afterwards. You can now set the padding between showings on an individual tour while reviewing the schedule, and set your own default in Settings. The confirmation times that go out to listing agents are built from the same number, so what you planned is what they are asked to agree to.
2 changes
When a listing agent comes back with a different time, that stop now carries a button to accept their time and the option to send one back, without leaving the screen where you are looking at the day as a whole. In the same pass, a stop order you arranged by hand is remembered, so re-running the optimizer no longer quietly throws your arrangement away.
Ordinary search returns a capped set of results, so typing one specific address could come back without the house you meant. Address queries now run their own lookup against the street number and street name inside the city, ZIP or county you are searching. Separately, an Include Pending toggle in the filter drawer decides whether pending listings appear at all.
Neither of these is a headline above, and for different reasons. One is not switched on at all. The other is off until you switch it on yourself, and is labelled beta in the app for a reason. Both get an entry on this page the day that changes.
Billing is not enabled. Nothing in the app can be bought, no card is asked for, and the beta is free. When that changes it will be announced here and on the pricing page, not discovered at a checkout screen.
An assistant that reads a tour’s drive times, confirmation statuses and counter-proposals and recommends a different order is off by default. An agent can switch it on in Settings, under “AI Scheduling Assistant”, where it is marked beta; the setting lives on that device rather than on the account. It returns suggestions to apply or ignore and reorders nothing on its own. The ordinary route optimizer — real driving times, no assistant involved — runs whether it is on or not.
iPhone, Android, or the browser. One account across all three.
Every capability in one place, with the limits named next to each one.
The flow end to end, from searching listings to closing out a tour day.
Coverage, cost, what your clients need, and what listing agents have to install.
The blank map, the empty drafts, the invitations that rendered as a hairline — none of those were caught by a test. Each one was found by running the app on a device until the failure reproduced, and the showing-request fix above started with a case somebody reported. If something is broken on your Saturday, telling us is the fastest route onto this page.
Listing search covers Oregon today. Check your market.