Based on the discussion and background in #452, we’ve put together some prototypes below, which we can use further to discuss availability settings, wording, logic, etc.
Let us know your thoughts in #452. Thanks!
P.S. Make sure to click around the prototypes because some fields only appear under specific conditions.
Availability pulse
What: A streamlined pop-up/modal that experts update weekly or when triggered by an action that indicates a change in availability e.g., an expert that is set as unavailable comments on a new task.
Where: We’ll probably display your current availability color or setting in the app header. Clicking it would show you your full pulse settings and allow a manual update.
Public appearance settings
What: More granular appearance settings that experts can configure on an ad-hoc basis.
Where: We’ll probably place these near the other app settings. They may also be linked to from the pulse popup since the two are related.
We are limited with the UI here, so we can’t add explanations for the Auto options, which we think are great defaults for most use cases.
When Preferred projects is set to Auto – based on my availability pulse, we imagine the setting can auto-update as follows:
- 🟢 availability pulse = Everyone can select me as preferred
- 🟡 availability pulse = Only my existing clients can select me as preferred
- 🔴 ⚫️ availability pulse = No one can select me as preferred
When Codeable website profile is set to Auto – based on my availability pulse, we imagine the setting can auto-update as follows:
- 🟢 🟡 🔴 availability pulse = profile is shown on website
- ⚫️ availability pulse = profile is hidden from website