Animation and Motion

[gouttierre]

[robertpenner]

Bookmarking

[briandrouin]

Design Contact: Karina

ADO task

[gouttierre]

📢"Karina looked at the various scenarios with Dan from the Team's Team. They are looking for other teams to contribute and build it. The easiest way to adopt the motion into a tokenized way is to have them built in so they do not get removed when a problem occurs. The design is in the conceptualizing phase."

[miroslavstastny]

Moving from Dec 2023 to Feb 2024 - there is still a lot of alignment needed across multiple teams and design (how motion is defined in the design system).

cc @gouttierre

[gouttierre]

📢

• "The ETA has moved from Dec 2023 to Feb 2024.
• "Karina and the team are making progress. There is a new PM driving some of the alignment. The design team is working on systemizing the design process while reviewing all past motion iterations to streamline the workflow and take advantage of existing motion patterns. It's a considerable effort, but things are progressing."
• "Cc @JustSlone, here is another component ETA that has shifted."

[briandrouin]

Karina is looking to see if names for some of the tokens can be changed so we can start applying them to our components.

[gouttierre]

📢"Karina is looking to change the token names for the motion. This would be the first step needed to be taken to start tokenizing the motion to start applying it to the components."

[gouttierre]

📢

• Karina is almost done with audit and will be presenting to Mark S in Feb. Assessing the motion currently in place and prioritizing from p0 to p2 on what must be changed.
• Shift has gotten a new motion package in preview and is working with UXEs to see how it meets their requirements. Robert will create a draft PR for discussion for the curve's visualization to storybook.

[gouttierre]

📢

• The v-team will be presenting to Shift later this month before he can resume development.
• Design is buttoning up their audit and prioritization to then give the motion step forward. Once the audit is done, and the designer knows in which priority they want to address the components, it's about finding the developers who have some down time to fix the completed ones and making sure the new ones we create have the right tokens assigned. Design is looking at a new way of tying the motion to the components that reduces perf issues by 67%.

[gouttierre]

📢

• Karina to finalize and sell the V1 proposal to Shift by end of Feb, with cross-team collaboration.
• Finalize the design in March and the have game plan to present it to Shift

[gouttierre]

📢

• Design (Karina) is doing the final edit of the audit that will be presented to the motion squad.
• Design required Fluent ENG + PM input for the presentation for this week.
• There are APIs to create motion components based on custom definitions that Teams will use to migrate from v0. (Shift)

[gouttierre]

📢

• Design presented the plan and the new tokens to Mark Swift and get alignment from engineering and leadership (Karina and Brandon)
• The meeting with Mark is Friday morning. Karina will let the team know how it goes.

[gouttierre]

📢

• The APIs were completed by Teams team for motion went to stable the previous week.
• The UXE developers will continue on implementing motion primitives. Brigette Lundeen to allocate developers (i.e., Robert, or Alexander) to the remaining implementations.

cc @brandonthomas , @tudorpopams , @JustSlone , @paulgildea , @jurokapsiar

[gouttierre]

📢

• Robert has a good chunk of context and is the go-to person.
• Shift has synced with Brigette, so she should also have a bit more context.
• Robert & Alex will work on motion components and Shift is helping them with onboard to Fluent repo.
• Karina will stay to help with the designs, but Isaac from Jason's team will drive the spec.

cc @robertpenner , @miroslavstastny , @JustSlone , @tudorpopams , @paulgildea