For most of the app experience, we'll rely on the DCAR component #15704 and atom #15867 to include the header/nav on relevant pages.
However, for the tables and results pages (which are native) the apps team will add the menu component natively as this is the same effort as adding the atom and would offer users a better experience.
To unblock this work whilst the URLs to the different items in the navigation are being finalised, we need to make the URLs and link text configurable through a new endpoint in MAPI. We have agreed with the apps team to pick up this work on their behalf, as their MSS developers are focussed on Live Activities.
For most of the app experience, we'll rely on the DCAR component #15704 and atom #15867 to include the header/nav on relevant pages.
However, for the tables and results pages (which are native) the apps team will add the menu component natively as this is the same effort as adding the atom and would offer users a better experience.
To unblock this work whilst the URLs to the different items in the navigation are being finalised, we need to make the URLs and link text configurable through a new endpoint in MAPI. We have agreed with the apps team to pick up this work on their behalf, as their MSS developers are focussed on Live Activities.