Dooney-Ecomm-DesignPrinciples
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

View only
 
 
ABCDEFGHIJKLMNOPQRSTUVWXYZAA
1
Design Principle
Already in Place?
Recommended in SF Review?Incorporate?Comments / Notes / Next Steps
2
1Make guest checkout prominant and easy to find. Place above the fold and above account signup/signin.YesGuest checkout button labels should read as "[lock icon] Guest Checkout"
3
2Always present the user with the proper keyboardYesfgfgf
4
3Always offer Up/Down arrows to facilitate jumping to form fieldsYes
5
4Avoid using drop down lists for the user's State and CC expiration datePartialCC expiry has good auto-formatting. State uses list…
6
5Offer recognizable payment options (PayPal and Apple Pay)NoHas customer demand for these options been explored? Yes, these are available on ILD and will be available on Dooney again soon. We need to design for these to be added in the coming months.
7
6The most common checkout option should be the most prominant on the pageUnclearWhat is the most popular payment option? Even when presented alternative payment methods historically, the most popular payment method has always been credit cards.
8
Reference: Mobile Checkout Experience Tips (NN/g)
9
10
11
Design Principle
Already in Place?
Incorporate?Comments / Notes / Next Steps
12
1*Provide quick access to the mobile shopping cartNoDesign principle recommends avoiding mini-cart... go direct to Shopping Bag page
13
2Make it easy for users to update the contents of their shopping cartYes
14
3Give users a clear Remove button next to each item in their cartYesNot available in mini-cart view. If keeping mini cart, consider adding remove btn
15
4Don't use an update button for committing changes to the shopping cartYesUsers do not have to use an "update" button to committ changes
16
5*Support the continuity of the shopping experience across multiple devices (Safari / Handoff)Needs more review
17
6Make the order summary easy to find in mobile layoutsNoCould be moved further up the page. Below fold on iPhone 7+.
18
7Use the user's current location to determine sales tax, delivery costs and any pickup options availableNoSales tax and shipping estimates show 0.00 on order summary screen. All orders ship free… consider changing Shipping calculation line to show "FREE" unless paid shipping option is selected by user.
19
8Calculate fields automatically based on users' prior inputsNeeds more reviewConsider asking key questions up front like: What zip code are you shipping to? (auto-pop city and state).
20
9Browser autofill and saved data should work on form fields (name, address, email address, phone number, password and credit card)Needs more reviewWorks on Chrome (Windows 10).
21
Works on Mobile Safari (iPhone 7+)
22
10Allow users to take photos of their credit cards to populate information
Partial (Mobile Safari)
This is working on mobile Safari browsers. Is there a demand/interest to implement for other browsers? Consider server side solution that removes the browser barrier from the user experience altogether… Perhaps looking into research that reviews how often users actually use this feature when offered would be helpful to know... Agreed, requires more research to determine usage and server-side options.
23
Watch Mobile Safari using browser-based functionality
24
Reference: The Mobile Checkout Experience (NN/g)
25
26
27
Design Principle
Already in Place?
Incorporate?Comments / Notes / Next Steps
28
1Wait until checkout to communicate taxes and typical shipping ratesNeeds more reviewOn pageload, ship free option is preselected...
29
2Be upfront about non-standard feesNeeds more reviewWhat type of non-standard fees exist?
30
3Communicate abnormally high shipping and delivery costs earlyNeeds more reviewRequires user selection...
31
4We should review/consider other recommendations from accelerator deck.
32
Reference: Salesforce Team (email citations from Cindy Ascolillo)
33
34
35
Design Principle
Already in Place?
Incorporate?Comments / Notes / Next Steps
36
1Combine First and Last Name fields into one single field (Full Name). Keep users inside input field.----Ask engineering about complexity to implement.
37
2Address (use Google's Places API / Geolocation) as single field entry. Alternately, use Zipcode to lookup City and State.----Ask engineering about complexity to implement.
38
3Email: Inline Validation (auto complete for common/popular email prefixes)----Ask engineering about complexity to implement.
39
4Credit Cards: use input masks and single line for card number, expiry date and pin.----Ask engineering about complexity to implement.
40
5Same as Billing: Auto default to "Yes"----Seems relatively straight forward...
41
Reference: Luke Wroblewski Conversions @ Google November 2017 Part 1 (52:50 playhead)
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
Loading...