Apps with maps use a specific and different Mercator projection which produces a nice quadtree for dynamically loading data. This is possible with other projections too, but reprojection and training users to expect a different looking map is expensive.
Almost nobody plots courses of constant bearing on a map. Almost nobody uses a map to measure area either.
99% of the use cases for maps these days are for local navigation where artifacts are minor. The differences in map projection are basically irrelevant to users in these cases.