That’s a separate problem, and I have experienced it. Many of the destinations I navigate to have only an street name, not a full address. But the problem I have is when multiple streets have the same name, Organic Maps (and it is definitely an OM problem, not inherent to OSM’s underlying data) doesn’t display sufficient disambiguating data to know which of those streets you’re looking for.

Here’s Organic Maps, with a search for a road I happen to know is a common road name in my area, without using one of the real similar examples that I’ve encountered (and which could help identify me). See how all of those examples say they’re various kinds of roads in “Brisbane, Australia”? That’s…not helpful. Because I know they’re all in Brisbane. But what I need is to know which suburb they’re in. Because I know I need to go to a particular suburb. The best option I have with OM is to guestimate how many kilometres away the suburb might be. Or to just guess and check if I’ve clicked the right one.

And this is what Google Maps looks like. Far, far more useful.

For completeness, here’s what I get in OpenStreetMap on the web. It’s showing more useful data, with the suburb and postcode shown. But doing some weird things with which results it decides to return for some reason. Probably because it doesn’t properly utilise location data. There are also multiple results of the same road (the top two, one says “City of Brisbane”, the official local government area, and the other “Greater Brisbane”, the statistical area used by ABS for census etc. purposes).

edit: reuploaded screenshots with precise distances covered up, for privacy reasons. Both OM and GM show the approximate distance, in kilometres, to each result.