I think that's way too reductionist and presumptive. Not only do other solid applications exist to use OSM, but I'd even say that a lot of users won't like CoMaps for how barebones it is (I'm one of those users).
Users might like more features like in OsmAnd, they might like specialty features in apps like Alpi Maps, they might like the OpenStreetMap web UI, and I think it's patronizing to decide for them that "people will get confused" and railroad them for that presumption. It also outright assumes someone wants to use it specifically on their phone. Edit: TIL CoMaps has a desktop version for macOS and Linux (Flathub).
If nothing else, I'd link to the OpenStreetMap Wiki, specifically their using OpenStreetMap guide and the 'Software' page.
I appreciate what you're saying, but I think saying "actually, just use CoMaps" isn't a good general way to go about introducing people to OSM.
Edit: But to hopefully alleviate some common confusion: OpenStreetMap is just the database. It's key–value pairs that get applied to points, lines, areas, and relations between those objects. The key–value pairs get decided on by community consensus. That's all OpenStreetMap actually is.
Everything else is using that underlying database. So the map you see on OpenStreetMap.org is a map called "Carto". The editor on the website is called "iD". CoMaps is an app for iOS/Android that takes that data, renders it, and periodically sends you an offline map. StreetComplete is a gamified Android app that lets you do little "quests" to fill in gaps in the data. So on and so forth. Anything where you're visualizing or changing that underlying data is just a frontend for OpenStreetMap.
Which frontend best suits your needs (navigation, editing, etc.) is up to you.