Skip to content
This repository was archived by the owner on May 10, 2023. It is now read-only.
This repository was archived by the owner on May 10, 2023. It is now read-only.

UX: Composer Redesign | accomodate multiple post actions #3

@KyleTryon

Description

@KyleTryon

When a user authors one or multiple posts (thread), they will have multiple possible options for actions to take. Users can schedule and post content in one of the following ways:

  • Post immediately
  • Add to queue (Auto schedule)
  • Schedule and add to queue

The Composer component needs to be redesigned to accommodate the multiple possible posting actions, and better integrate thread posts.

image

1. Post Button

Marked here as circle 1, the post button as it is, now assumes that you will be posting to the scheduled time, indicated by the date-time component, labeled in circle 2.

My immediate thought is to create a button with a "default" value, such as "Post" for posting immediately, and have a built-in drop-down menu for the other possible posting options. And maybe, we would save the last option a user selected for the default status of the button?

Here is an example of the type of button component I am thinking might resolve this issue: https://tailwindui.com/components/application-ui/elements/dropdowns

image

Probably something more like this, where there is "two" buttons, one for the action, and one for the drop down.
image

Is this intuitive enough?

2. Date-Time Schedule

Marked in circle 2, is the scheduled time for when to post. Right now, this is automatically set to the current time, clicking on the calendar will bring up a native calendar and time input for a future date.

One request we have seen a few times already, some users would like to add items to their queue, but not worry about scheduling the post. Instead, users would like the ability to build up a backlog of queue items that automatically post X times per day.

If we do not need the date/time for items added to the queue, where should this date-time component live? Should it always be visible? Would it disable if the queue option is selected?

3. Create Thread button

Finally, the third circle shows how a user can click a button to turn a single post into a thread. This design can likely be improved and does not yet consider what multiple composers would look like on the screen. We likely do not want the "post" button on each post when dealing with threads.

How should we redesign the thread button? Does the post button need to move outside of the composer because of this?

Metadata

Metadata

Labels

design neededLooking for UX/UI designer input

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions