Dooney-Ecomm-DesignPrinciples

	A	B	C	D	E	F
1	Design Principle		Already in Place?	Recommended in SF Review?	Incorporate?	Comments / Notes / Next Steps
2	1	Make guest checkout prominant and easy to find. Place above the fold and above account signup/signin.	Yes			Guest checkout button labels should read as "[lock icon] Guest Checkout"
3	2	Always present the user with the proper keyboard	Yes	fgfgf
4	3	Always offer Up/Down arrows to facilitate jumping to form fields	Yes
5	4	Avoid using drop down lists for the user's State and CC expiration date	Partial			CC expiry has good auto-formatting. State uses list…
6	5	Offer recognizable payment options (PayPal and Apple Pay)	No			Has 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	6	The most common checkout option should be the most prominant on the page	Unclear			What 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 cart	No			Design principle recommends avoiding mini-cart... go direct to Shopping Bag page
13	2	Make it easy for users to update the contents of their shopping cart	Yes
14	3	Give users a clear Remove button next to each item in their cart	Yes			Not available in mini-cart view. If keeping mini cart, consider adding remove btn
15	4	Don't use an update button for committing changes to the shopping cart	Yes			Users 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	6	Make the order summary easy to find in mobile layouts	No			Could be moved further up the page. Below fold on iPhone 7+.
18	7	Use the user's current location to determine sales tax, delivery costs and any pickup options available	No			Sales 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	8	Calculate fields automatically based on users' prior inputs	Needs more review			Consider asking key questions up front like: What zip code are you shipping to? (auto-pop city and state).
20	9	Browser autofill and saved data should work on form fields (name, address, email address, phone number, password and credit card)	Needs more review			Works on Chrome (Windows 10).
21						Works on Mobile Safari (iPhone 7+)
22	10	Allow 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	1	Wait until checkout to communicate taxes and typical shipping rates	Needs more review			On pageload, ship free option is preselected...
29	2	Be upfront about non-standard fees	Needs more review			What type of non-standard fees exist?
30	3	Communicate abnormally high shipping and delivery costs early	Needs more review			Requires user selection...
31	4	We 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	1	Combine First and Last Name fields into one single field (Full Name). Keep users inside input field.	--		--	Ask engineering about complexity to implement.
37	2	Address (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	3	Email: Inline Validation (auto complete for common/popular email prefixes)	--		--	Ask engineering about complexity to implement.
39	4	Credit Cards: use input masks and single line for card number, expiry date and pin.	--		--	Ask engineering about complexity to implement.
40	5	Same 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