I shot and published a video (www.youtube.com) yesterday, which is the second part of my “PinePhone as a daily driver” challenge, in which I am currently just trying to solve the most immidiate issues and figure out the most necessary features I would require to use the PinePhone as my primary smartphone. This time it is about Maps and Navigation.
In the first part of my PinePhone as a Daily Driver series, I had noticed problems with the Gnome Maps app. I wanted to make this video about productivity and Maps, but as the Gnome Notes app mysteriously stopped showing my Nextcloud Notes, this is just about Maps and other “where am I” and “how do I get to”-problem solving applications.
First I have another look at Gnome Maps, which is quite short and does not get into many of its features because these are not really usable due to Gnome Maps not being optimised for mobile (yet), I switch desktop environment sides and continue with a KDE app. Marble Maps, which is in the Mobian repos, is not even being featured prominently on the Marble website. It does not scale well on Phosh, but has a long history on Android and Nokias Linux smartphones N9 and N900.
Then I have a rather long and exhaustive look at Pure Maps (Github), which is not only available for Sailfish, Nemo Mobile and UBports, but can be installed as a Flatpak on every other PinePhone distribution, too. It is quite full-featured and can serve as a simple maps app and also be used for navigation. It does not feature an easy way to use it with offline maps for increased privacy and operation in areas without network access; that requires another software called OSM Scout Server to be installed and set up.1 The postmarketOS Wiki claims that the combination of OSM Scout Server and Pure Maps can use up to 2 Gigabytes of RAM, rendering it likely unusable on the PinePhone.
Now go and watch it