<?xml version="1.0" encoding="utf-8"?>
Open full project

Here I’ve created a desktop iteration of a checkout page design that supports Visa, MasterCard, and Amex. I’ve included all the necessary fields for customers to complete purchases in one single page to help reduce cognitive load and friction.

A one-click Apple Pay button at the top of the form allows users to skip the tediousness of filling out all the checkout fields manually. For those who don’t have access to Apple Pay, the address section of the form includes a self-filling address field, allowing users to skip that manual input. The option to enter this information manually is of course also available by clicking the ‘Enter address manually’ link below the address fields, allowing for the user to have this option if preferred or required.

There are multiple payment method options, from traditional credit cards to other alternatives like Affirm and Cash App, to help ensure easy and quick payments for users.

Warning, Error, and Success states have been included in red and green respectively, along with the appropriate icons (check mark, exclamation mark). Short messages are displayed below the cells in question, indicating to the user how to proceed in clearing the Warning or Error state and completing the purchase.

The left side of the checkout page displays the price, code, and image of the item the user is attempting to purchase. The option to delete or add more of those items is also displayed in case the user has as second thoughts.

I’ve also included a “Need Help?” hyperlink at the bottom of the checkout page to offer users an additional route to support if needed.

Share your insights — leave a project review and help others grow their skills

Reviews

6 reviews


I'm curious to know if people would actually use the "Delete" icon on the bottom or if they would just exit the page. I see room for an A/B testing


Thank you for your presentation here. I like the fact that you put the Apple Pay to make it easier for the checkout and the layout for the shipping. There are some things you should think about just to get a better version perhaps.

Is it better to put the name in the same block as the shipping address or is it more of a container like email?

If I leave red color stroke of the card number on red would i alert the user with no reason? ( I assume that you are just showcasing what would happen if he didn't fill the space - btw, great job splitting the number into 4 digits)

What colour is usually the apple pay button? should i maintain the consistency of my brand and use the same color as my button or use their pattern?

Great work again! Those questions are just to make you think more about it!


You did great job on designing the checkout page! I like that you follow some of the commonly used layout that is going to be easy to understand. Providing the Apple Pay as option to skip the form is also great option. Placement of the Apple Pay button makes more sense in previous step of the checkout or on product detail page. As it's skipping the whole process https://developer.apple.com/apple-pay/

I have some accessibility concerns on aggregated Shipping Address inputs as there are not visible label while input is filled. I would change the logic for the checkbox "Billing Address is the same". As in most cases, all users according that login will be forced to click on the checkbox. Makes more sense to have checked checkbox with this copy. Or reverse copy "The Billing Address is different" and provide additional inputs on interaction. Also you are displaying live validation state for email input while email is not filled-in yet.


I like this no-fuss design! Really the only slight suggestion that I have is to maybe place the basket icon in line with the Quantity box, or a simple X. Depending on the product's image, maybe some users would miss the icon below it, but other than that excellent work!


UI and UX.

Overall the project looks good, has a familiar layout. The main issue I see here is the way it way built. I think that the era of rectangles for inputs is already gone, so we, as web designers must be careful how the design is built, is easy to make it responsive so the handover to devs should be smooth.

Also is not a good practice to use placeholder content at this stage in the project (work only for low-fi wireframes).

Also, when sharing a project, give view-only acces to anyone else but you.

For next projects you should definitely try autolayout frames and components with variants.

All good!


27 Claps
Average 4.5 by 6 people
5 claps
4 claps
3 claps
2 claps
1 claps
<?xml version="1.0" encoding="utf-8"?>