While I'm still a big proponent of mobile/Android/iOS integration with ROS, as the price point of availabile hardware and prevalence of device ownership with youth makes it a compelling platform to teach robotics with, it's not without it's own limitations.
Although you get all these cool sensors, connectivity, and interfaces bundled into a compact form factor: e.i. cameras, excelometers, gyroscopes, barometers, GPS, microphones, speakers, touch screens, USB ports, battery with integrated charging circuits, arm CPUs, expandable storage, SDKs, etc. They do have a number of limitations such as OS access restrictions from a users perspective, as well as all the quirks and rough edges such as hardware fragmentation and vendored software/firmware restrictions.
For example, missing kernel features for UDP multicast networking for DDS in ROS2:
In that respect, the SteamDeck and other Linux enabled mobile gaming devices look to be a promising alternative to the previous norm of giving students underpowered net book and balancing them precariously on turtle bots. The screen and controls as one unit makes tasks such as tele-operation or telemetry monitoring more practical for field robotic deployments and experiments. Still not something one could strap to a turtlebot or a quad rotor like an old Android phone, but suitable as a mobile base station.
BTW, while there are a few SteamDeck communities already on Lemmy, you may find this community of particular interest, that migrated from r/steamdeck_linux: