OSM is the database containing all the data. Navigation is not exactly "data" that is stored in a database, it's the result of computing a path between two locations based on the data stored in OSM.
Maybe a comparison would be this: if you want to hike somewhere the "old school" way, with a compass and a paper map. You will buy a paper map made by someone else, you will localise yourself on this map, and then you will trace a path between where you are and where you want to go. As you hike, you will update your location on the map (by using e.g. your compass) and choose your next steps accordingly.
In this example, the paper map is not doing any navigation. It doesn't know what GPS is, it doesn't have a compass. It's just map data printed on paper. You are the one making the navigation, right?
- OSM is the paper map.
- Organic Maps, or OSMAnd, or whatever app you use as a frontend to OSM is "the navigator" (you).
Maybe a comparison would be this: if you want to hike somewhere the "old school" way, with a compass and a paper map. You will buy a paper map made by someone else, you will localise yourself on this map, and then you will trace a path between where you are and where you want to go. As you hike, you will update your location on the map (by using e.g. your compass) and choose your next steps accordingly.
In this example, the paper map is not doing any navigation. It doesn't know what GPS is, it doesn't have a compass. It's just map data printed on paper. You are the one making the navigation, right?
- OSM is the paper map.
- Organic Maps, or OSMAnd, or whatever app you use as a frontend to OSM is "the navigator" (you).
Does that help?