The goal here was to explore a way to allow folks to see and enter common 🇺🇸 USA and 🇨🇦 CA based time zones quickly.

The assumption here is that ET, CT, MT, PT are more common than any others.

The map is unnecessary but visually engaging. It works to reinforce the selection and provide intuitive feedback that doesn’t require reading long strings of text like America/Indiana/Vevay.

If you do require a very specific time zone, the input also supports fuzzy searching of city, state, country, and province.

The goal here is to provide a better way to enter most time zones, while not sacrificing edge case input.

Try it out yourself and let us know what you think!

---

Related to this we did some basic investigation into time zone, timezone, time-zone usage.

The hyphenated time-zone came first, time zone settled in as the dictionary standard, and now timezone is taking over but not dominant.

timezone → Everyday, technical, and UI writing — the modern default

Example: Select your timezone from the dropdown.

time zone → Formal, editorial, or dictionary-standard contexts

Example: The meeting is scheduled across three time zones.

time-zone → Only as a modifier directly before a noun

Example: The app handles time-zone conversions automatically.

Google Books Ngram Viewer of these 3 terms.

This leaves the question open, but in Voxie we should pick one and stick with it, with the caveat that time-zone is specific to a particular grammatical context.

What’s New

• canvas position gets tracked now so going back from flow editing lands you in the same spot you were before
• brings back missing un-publish and pause buttons. Adds them to the version history section
• mini flow
  • click to deselect nodes
  • add edit button to mini flow header card
  • add scale effect to header card
  • add support for command clicking flows to open in new tabs
• fix save bug on trigger node
• tidy up buttons and other ui

Prototype URL: https://proto-workflow-builder-mk1.vercel.app/

When a workflow has a new version published, you are given a choice to either stop all in-progress flows or let those flows continue on in that version. If you allow the old version to continue on, this is called draining, and we need a way to show that the old workflows are still in a draining state. This interface tries to show that in a subtle and elegant manner.

You can give this a try:

https://proto-workflow-builder-mk1.vercel.app/flows

1. create a flow
2. add a wait node of 1d ay or more
3. publish
4. start the simulator
5. give a few seconds to build up a backlog of waits
6. edit the flow in some way
7. publish new version
8. choose Let existing instances finish in current version
9. go checkout main canvas to see the draining

The billing configuration sections of Kiosk mode were not looking up to Voxie interface quality standards.

These layouts look to remedy these issues:

• incorrect colors
• misuse of callout/alert components
• overly complex view/edit interface
• inconsistent and random price display 0.25, $0.00000 all should be $0.00
• divergence from our settings ux (update per card)
• better historical navigation and display

Mockups

• Estimated Throughput
• Billing Configuration

Prototype now has the ability to add and use Snippets, similar to the current Voxie production applications and its Message Builder components.

Give it a go

This is a refinement to the UX of Workflow Builder. Now, in order to connect 2 flows together, Flow A can only connect to Flow B if Flow B has the trigger set to Flow Input.

This limits what is technically possible, however in trade we get a system that is much easier to communicate and reason about. This also prevents users from making highly abstract connections between resources that could lead to unwanted side effects.

Give it a try

Test mode

• Toggle-on-click
• More visibility to active-step indicator
• Shared-component UI
• Correct trigger-event-type mapping
• Test contact fields now match full contact data model

Logic Nodes

• Renamed Gate to Filter
• Fixed infinite loop on copy/paste bug
• Treat Filter as linear (clean delete, multi-select, branch path)
• CaseSensitive stored as boolean
• Contains_any/equals_any operators added to string fields
• Consolidated validation alerts
• Fixed ItemSelector height issue on selection

Canvas

• Fix white-screen crash and missing flows when grouping by trigger
• Fix hover paste/cancel buttons on the edit canvas
• Show marching ants + validation alerts for all incomplete nodes (not just the selected one)
• Remove Segment / External List choices from the Update node
• Warn about branch deletions using trash-can iconography
• Add exists / does_not_exist operators for custom attributes
• Wrap node details instead of truncating
• Muted style buttons for flow card
• Restore canvas position after publish (matches existing back-button behavior)

Console

These are only relevant for this prototype but still needed some love.

• Console toolbar defaults to minimized
• Fix invisible close button on dark background

Kick the tires

This is a small quality of life update for us that shaves minutes of manual effort away each week.

For this demo site you are looking at, we host the image and video assets on the Voxie Cloudinary account. This used to require uploading those manually.

This is a small bit of AppleScript and 2 wrappers: Launchbar Script and macOS Service Workflow Script.

This lets us select an image or video on our Macs and in 1 action upload and get that URL copied to clipboard.

☹️ Old Method

1. Open Cloudinary
2. Log in
3. Navigate to ui-team folder
4. Drag or select image to that folder
5. Refresh page
6. Copy uploaded URL
7. Paste to demo site code

😁 New Methods

Using Launchbar

1. Select image
2. Activate Launchbar
3. Choose Cloudinary Upload
4. Paste URL to demo site

Using macOS Service

1. Right click image
2. Choose Cloudinary Upload
3. Paste URL to demo site

---

Bonus feature is you can use it on many images at once. So for 5 images this can take ~35 steps and compress that to 3 steps, a 12x improvement.