Tactical UX project status - May 11

Standardization of the Favorite icon (Heart)

On our application, the favorite icon is a heart, when this icon is shown on the application we don't have a pattern of color and behavior.

Each screen using this heart icon need to configure all design attributes and behavior (ex: Animation), consequently, we have for the same market and brand different configs to the icons.

Not needed for PLK ES go live

Feature - Heart Color

IN PROGRESS

• Development completed

• QA pending (de-prioritised in favour of Agreements feature)

User acceptance of updated Agreements

The ability for Iberia to update legal agreements (Terms and Conditions and Privacy Policy). Specifically, when the Privacy Policy gets updated, guests must accept changes.

Needed for the PLK ES go-live

Feature - Agreements

IN PROGRESS

• Reduced scope

• Development in progress, expecting to release by 14th April

Highlight current day of the Store

When listing the weekday opening hours of the restaurants is difficult for the user to see if it is open at the moment. 

Not needed for PLK ES go live

Feature - Highlight current day

IN PROGRESS

• Requirements are clear

• Design iterations finalised

• Pending development (team focusing on Agreements)

Salesforce tracking pixel

Track outbound (e-mail and push) campaigns with Pixel Salesforce.

Tracking campaigns with events.

Not needed for the PLK ES go-live

Feature - Salesforce tracking pixel

IN DISCOVERY

• Completed analysis on Whitelabel/mParticle

• Waiting Email answer about Salesforce integration

Hero Component

• It is possible to use the current version of the Hero Component(TO DEVELOPMENT)
• Not so much space between component composition(CONFIGURATION)
• The first CTA must be higher(TO DEVELOPMENT)
• The second CTA is optional(TO DEVELOPMENT)
• Remove white space when the second CTA and/or terms and conditions are not set (TO DEVELOPMENT)
• All banner image is also clickable 

Not needed for PLK ES go live

Feature - Customize Hero Component

IN DISCOVERY

• To define if will create a new component or reuse existent(REUSE COMPONENT)

• Confirm the solution for the requirements