Missing top priority features in Organic Maps and GNOME Maps
Introduce and describe the topic
Organic Maps came first in the apps poll and GNOME Maps was a very close second. https://codema.in/d/phU1JlaV/pick-and-fund-a-maps-app
So we need to list out the missing top priority features in both apps. We can try to crowd fund missing features in at least one app (may be both apps).
Why is this important?
We need this to provide good Maps/Navigation experience.
How would you like people to respond?
Add the missing features of both apps (features that came at the top in this poll https://codema.in/d/lvQjiUo6/ideal-maps-navigation-app-features will have a higher priority)
alevix Tue 24 Sep 2024 3:43PM
@Pirate Praveen organic already can load and record gps tracks since latest version, almost 3 weeks ago! kml and gpx (kmz will come next). still missing to edit them, with a little bug on beta probably already fixed for next release. at least on android.
from what i can see, it just really need a good linux binary.
baarkerlounger Tue 24 Sep 2024 4:12PM
Given that:
Gnome Map's main advantage over Organic Maps is that it's GTK based
Organic Maps is a common C++ core with various frontend's (currently Java, Swift, QT?)
The QT frontend is far from parity with the others
Does it maybe make sense to try to fund development of a GTK frontend for Organic Maps?
This assumes of course that building that front end would be less work than trying to implement all the core features Organic Maps already has in Gnome Maps.
Badri Sunderarajan Wed 25 Sep 2024 10:55AM
@baarkerlounger I was thinking the same...
Silmathoron Thu 26 Sep 2024 11:38AM
Since KDE has a workflow to generate apps for both linux and Android, it might be worth discussing with the people from OrganicMaps whether using that single workflow instead of having one for Android and one for linux could make sense for them.
Pirate Praveen Fri 27 Sep 2024 7:16AM
@Silmathoron I think it will take long for the Qt front end to reach feature parity with current Android front end. So even if they wanted to use Qt for android, this would take a while.
Item removed
Pirate Praveen Fri 27 Sep 2024 7:19AM
@baarkerlounger I think we generally underestimate the ongoing maintenance costs when thinking about writing something new. In my opinion having both Qt and GTK+ front ends for Organic Maps is wasted effort. We can discuss with Organic Maps developers if they are willing to switch.
We can also ask GNOME maps developers if they are willing to adopt Organic Maps core which will bring features like offline maps and turn by turn navigation.
Update: asked gnome maps developers https://gitlab.gnome.org/GNOME/gnome-maps/-/issues/416#note_2232928
baarkerlounger Fri 27 Sep 2024 7:30AM
Sure, both questions worth asking though I think the answer is likely to be no in both cases.
I'm not sure a QT + GTK+ front end is wasted effort since it being native in Gnome/Phosh is one of the highest priorities for people, I imagine the same might be true of people using KDE on their Linux mobile. But yes there'd be ongoing development and maintenance effort.
Pirate Praveen Fri 27 Sep 2024 8:23AM
@baarkerlounger I imagine eventually GNOME maps will catch up on these features and we will have two GTK+ Maps apps to maintain if we go down this path. We are trying to reduce fragmentation by focusing on less number of apps/projects for the same feature.
Pirate Praveen · Tue 24 Sep 2024 12:43PM
Organic Maps:
Adapt to mobile screen - https://github.com/orgs/organicmaps/discussions/6420
(low priority) load and record GPS tracks
GNOME Maps:
Offline Maps - https://gitlab.gnome.org/GNOME/gnome-maps/-/issues/416
Turn by Turn Navigation - https://gitlab.gnome.org/GNOME/gnome-maps/-/issues/335
Some UI/UX improvements (we have to make a list, I think bigger buttons would be one)
(low priority) load and record GPS tracks