It would be very tough to implement "collision avoidance" without being overbearing on what the user can or cannot do. For example, it would be extremely annoying if the robot's collision avoidance made it actively try to stay away from walls "because the user could potentially make a sudden turn at full speed towards the wall, and then a collision could result, so therefore we should try to avoid that scenario because, damn it, we promised collision avoidance!".
The net effect would be that the user might have a very good reason for wanting to drive close to a wall, but can't because of artificial limits imposed by the software.
It's better to not waste time on those kinds of 'features' and instead focus on making the core experience better. In this case, focusing on the two-way video and reducing chat lag time.
Incidentally, those kinds of 'features' seem like exactly the kind of thing that a mature company would focus on (waste time on) and lose sight of making the actual product better, because it combines so many things that mature companies would like -- delivering on promises to the user, it sounds good on paper, etc. But it loses sight of the fact that the goal is to make the end product better, not to deliver a laundry list of things.