Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Enhancement]: Block-based checkout: Collapsed order summary on mobile, sticky on desktop #45285

Open
nikkivias opened this issue Mar 4, 2024 · 8 comments
Assignees
Labels
block: checkout Issues related to the checkout block. focus: checkout Issues related to checkout page. needs: design feedback Issues for which we requested feedback from design team. team: Rubik Store API checkout endpoints, Mini-Cart, Cart and Checkout related issues type: enhancement The issue is a request for an enhancement.

Comments

@nikkivias
Copy link

nikkivias commented Mar 4, 2024

Describe the solution you'd like

The current checkout experience where the Order summary is concerned needs improvement. We want to investigate if the following proposed solutions are feasible.

On mobile

Upon entering checkout the order summary takes up much of the space above the fold that it often pushes down the first actionable item on the page (e.g. Contact). Furthermore, when scrolling down to the end of the page, there is no access to the order summary unless the user scrolls all the way back up.

💡 Proposed solution

Implement an order summary that is:

  • collapsed by default
  • expands as an overlay
  • hides/shows depending on scroll direction so it can be out of the way as they accomplish the page (video example below)
  • add a final Order summary before Place order button

Collapsed on default, overlay when expanded

CleanShot 2024-03-04 at 16 05 11

Final order summary section (sticky summary is hidden in this view)

CleanShot 2024-03-04 at 16 09 17@2x

Example of scroll interaction behaviour:

CleanShot.2024-03-04.at.15.58.17.mp4

cc: @pmcpinto

Describe alternatives you've considered

No response

Additional context

No response

@nikkivias nikkivias added type: enhancement The issue is a request for an enhancement. status: awaiting triage This is a newly created issue waiting for triage. labels Mar 4, 2024
@jonathansadowski jonathansadowski added focus: checkout Issues related to checkout page. team: Rubik Store API checkout endpoints, Mini-Cart, Cart and Checkout related issues block: checkout Issues related to the checkout block. labels Mar 4, 2024
@pmcpinto pmcpinto removed the status: awaiting triage This is a newly created issue waiting for triage. label Mar 5, 2024
@pmcpinto
Copy link
Collaborator

pmcpinto commented Mar 5, 2024

Two notes for the engineering team:

  • The mobile and desktop flows don't need to be implemented in tandem. We can sequence them and implement them separately.
  • Both are good a/b testing candidates, so that we can measure the impact of these changes.

@senadir senadir assigned senadir and unassigned senadir May 10, 2024
@senadir
Copy link
Member

senadir commented May 10, 2024

Hey @nikkivias @pmcpinto I removed the sticky on desktop part of this issue, as those are 2 different things with different scope.

Sticky one is already requested here #42230

@senadir
Copy link
Member

senadir commented May 10, 2024

@nikkivias just to confirm:

  • You want the exact same order summary in 2 places, at the top of the page, and before the place order button.
  • I'm not sure I understand the scroll effect you're looking for, does it mean it shows the sidebar if you're scrolling back up, but hides it if you're scrolling down?

@senadir
Copy link
Member

senadir commented May 10, 2024

I wanted to pick this next, but I'm porter next week, if I'm not the one picking this up, a suggestion to whoever is picking this up, instead of replicating the order summary component, touching the editor component, or the structure, just use a slotfill, inside the sidebar and above the place order button. You'd have 2 slots and 1 fill.

Ideally the top order summary is the current one in its placement, and the one above the button is the slotted one.

@opr
Copy link
Contributor

opr commented May 13, 2024

@senadir the slots we add would be for internal use only, correct?

@senadir
Copy link
Member

senadir commented May 13, 2024

Yes, ideally. Any concerns there? I still think slots have a place in extensibility.

@opr
Copy link
Contributor

opr commented May 13, 2024

No concerns, just checking. Yes they do have a place in extensibility but I don't think we should expose these publicly until we see a solid use case for it, outside of this one.

@senadir senadir self-assigned this May 14, 2024
@senadir senadir added the needs: design feedback Issues for which we requested feedback from design team. label May 29, 2024
@nikkivias
Copy link
Author

Updating this issue with the latest mock up and prototype

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
block: checkout Issues related to the checkout block. focus: checkout Issues related to checkout page. needs: design feedback Issues for which we requested feedback from design team. team: Rubik Store API checkout endpoints, Mini-Cart, Cart and Checkout related issues type: enhancement The issue is a request for an enhancement.
Projects
None yet
Development

No branches or pull requests

5 participants