The tab bar keeps its hand-drawn implementation. It was hand-drawn because DDS prohibited Material's pill indicator. That reason is gone — but it is four equal cells with an active label in blue_text, it works, and swapping in BottomNavigationBar now would be a change with no user-visible benefit. 🚨 The desktop menu is a TOP menu, and it is always on screen. The first answer was a 232px left rail and Ted killed it the day he used it: "depending on the screen on the right, this panel disappears". The disappearing act was structural, not cosmetic — the shell drew the rail, only the four destination screens used the shell, and every card, topic, place and settings sub-page is pushed OVER those four as a full-screen route. Any menu a screen owns has that bug, and widening the rail would not have touched it. So the menu is not owned by a screen: it mounts once above the router's Navigator, and no route can cover it. §6.1, §7c.