You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Okay, here is the updated design for the "combined shipping rates and times": https://d.pr/i/aPCjIt
I tried to keep it as close to the original as possible, while still making it user-friendly - it IS an intimidating setting.
[…]
Appreciate any feedback or questions on the design though.
Also, if this design change doesn't make it in for Tranche 2 (likely won't, since we're pushing for that this week), I think it's fine. We can just make a special note of it to testers and ask them to choose manual for both or neither.
Technical
We are in the middle of re-creating these components for Edit flow to be more reusable, and in the longterm used shared between onboarding end edit flows. On the meeting with @jconroy and me, we agreed to implement edit flow the "new way". It will introduce some inconsistency in the meantime, but since we are rewriting those components anyway, it would be a less wasted effort.
The text was updated successfully, but these errors were encountered:
tomalec
changed the title
Adjust free campaigns setup and edit ro redesigned "shipping rates and times"
Adjust free campaigns setup and edit to redesigned "shipping rates and times"
Mar 11, 2021
@j111q WDYT of using a smaller gap between Shipping rate & time cards?
Here is the example of half of the size.
That may suggest that all three cards are related to each other, and the forth card falls into a outer scope, just by looking at cards (Gestalt proximity)
This is a follow-up issue from shipping rates and times
User story
@j111q:
Technical
We are in the middle of re-creating these components for Edit flow to be more reusable, and in the longterm used shared between onboarding end edit flows. On the meeting with @jconroy and me, we agreed to implement edit flow the "new way". It will introduce some inconsistency in the meantime, but since we are rewriting those components anyway, it would be a less wasted effort.
Figma link
https://www.figma.com/file/jZUpa8eTrnrK1Lwt2ry7zk/Native-Google-Integration?node-id=5918%3A172
The text was updated successfully, but these errors were encountered: