Page Comparison

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

• Development “In progress”

• After it passes QA it will be deployed live (expected first week April)

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

• Requirements are clear

• Design iteration is needed on the screens to accommodate multiple agreements

• The development team started backend side

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

• Requirements are clear

• Design iterations needed on the screens to accommodate multiple brands (PLK, BK, FHS)

Salesforce tracking pixel

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

Tracking campaigns with events.

Needed for the PLK ES go-live

Feature - Salesforce tracking pixel

• Initial analysis on Whitelabel/mParticle - Done

• Waiting Email answer about Salesforce integration

• Meeting scheduled with Paula to align the requirements

Hero Component

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

Not needed for PLK ES go live

Feature - Customize Hero Component

• Define if will create a new component or reuse existent

• Confirm the solution for the requirements