User-Centered Review of Cartes: UX&UI, Navigation, Language Priorities, Dedicated App and Advertisement
publié le , mis à jourDécrivez votre problème, votre suggestion
0. Context
I wanted to give my humble experience and thoughts in here. I aim to give you a first-hand user experience so you can have an external idea to inspire you in your future planning and prioritizing some of your tasks. With that I hope I can contribute to have an app which feel as natural as possible, which can satisfy more users.
Therefore, here is a brief feedback this morning I wrote and wanted to share with you.
1. UX & UI Suggestions
1.1. Search Bar
Click-Free Search Bar
When I open the app, the most important function is searching. As Steve Krug says in Don’t Make Me Think, it should be as natural as possible. So requiring an extra click to access the search bar is unacceptable. Google Maps dedicates a large top bar for search, which is an effective approach.
Cartes Search Bar
In Cartes, the search bar is hidden in the bottom-left corner. Clicking it reveals a search field, an advertisement text, language options, and multiple icons—some recognizable, others unclear. This clutter disrupts the user experience. The squeezed text "A free and open map..." is better suited for the homepage, not the search interface.
Language Setting
Language preferences should be set once and retained. There’s no need to switch between Italian and French on different days. This setting could be tucked away in app preferences. Two options could work: either prompt the user to set their preferred language when requesting location permissions (with the ability to change it later in settings) or default to the device language, falling back to English if unavailable.
Icons in Search
Google’s categorical suggestions, like recommending a brasserie when searching for restaurants, are often inaccurate. Cartes handles this better, but the icons still clutter the map when searching. For example, searching for restaurants should hide unrelated icons, not just make them translucent. A clean background improves focus.
Search Errors
Features like rain precipitation and interior floor information are impressive, but search accuracy is much more critical. For instance, searching for "Arax" directs me to Morocco, even with the search here option enabled. Only searching for "Epicerie Arax" gives the correct result. This is a major issue that undermines the app’s usability, regardless of other features. Fixing search errors should take priority over adding new functions.
1.2. Map View
Colors and Contrast
A navigation map should emphasize roads over buildings. In Cartes, roads and buildings lack sufficient contrast, unlike Google Maps, where roads are clearly highlighted. This makes navigation more intuitive.
Building Colors
Some buildings are colored differently, such as red, but the meaning is unclear. Without a defined hierarchy (e.g., public buildings or accessibility), color differentiation is unnecessary and confusing.
Density of Icons
The map starts minimal, showing only essential (maybe even too empty) locations like stations, schools, and hospitals. However, zooming in suddenly floods the screen with icons for everything from clothing shops to drinkable water sources. Google Maps maintains a consistent icon density. Also, they display colored dots, which expand into full icons upon further zooming. This approach preserves clarity and density.
Big Blue Square
Clicking a location displays a large blue square, which feels clunky and definitely unsatisfying to see that, more look like a bug.
Order in place description When I click a place it shouldn't provide a panoramic photo of the point and then the Wikipedia image. I think all the images should be in the same line. And in one click I should be able to see the name of the chosen place, and opening details without scrolling down.
1.3. Navigation
Default Point A
When selecting a café and clicking "navigate," the app asks for a starting point. This is quite frustrating because the default should be the user’s current location. If not user can change the initial point.
Navigation Button
The navigation button prompts for departure and arrival points, which is counterintuitive. Users very often don’t know both points in advance. The search bar should handle this function, in my opinion there is no need for a separate navigation button which occupies space.
2. Language Priorities
Language selection defines the target audience. The primary market for this app is likely France, including expats who may prefer English, German, Italian, Spanish, or Arabic over French.
The language options should prioritize:
- French
- English
- German
- Italian
- Spanish
- Arabic
Including regional languages like Occitan and Brezhoneg is interesting but adds almost no practical value. Their presence only raises questions about their relevance. Of course, I am open if you have some other aspects.
3. A Dedicated Application
In my opinion a dedicated app would be more effective than relying on a web app. Excuse me if you have already planned that in future but in any case I take the opportunity to highlight that.
Browser Dependency
Cartes.app lacks support on all browsers. For example, I use Brave, but Cartes do not support, so I have to use Safari and provide more telemetry to Apple. A dedicated app would reduce reliance on browser performance and internet speed, possibly it provides a faster, and more efficient offline functionality.
Limited User Information
Mobile devices provide sensor data, such as compass information (in my iPhone), which my browsers cannot access at least I do not know how to give the permission. A dedicated app would improve accuracy by utilizing these sensors which I benefit in all the other navigation apps.
Default App Option
Currently, location links open in Google Maps or Apple Maps by default. Indeed, being able to set Cartes as the default would enhance its usability.
Crowdsourcing
I am not sure if you are already doing this, but there are some users like me who are willing to contribute happily by sharing some anonymous data to a local open-source application. So asking consent-based telemetry has no ethical problem in here.
4. Advertisement
I am quite sad no one knows this gem. Even European tech sovereignty sites (1, 2) do not mention Cartes but Organic Maps. It needs maybe some important bug fixes as I mentioned above. But then definitely needs advertisements and YouTube videos in French. Also, some French channels like Underscore_ which has almost a million subscriber.
Système d'exploitation
iPhone
Navigateur
Safari
laem
First of all, thanks for these comments :) I'll answer them progressively, here or on other issues.
Language Setting Language preferences should be set once and retained. There’s no need to switch between Italian and French on different days. This setting could be tucked away in app preferences. Two options could work: either prompt the user to set their preferred language when requesting location permissions (with the ability to change it later in settings) or default to the device language, falling back to English if unavailable.
They are retained, forever. Can you describe your experience more precisely ?
This is my cookie when I chose italian : Expiration / Durée maximum :"Wed, 24 Mar 2027 13:35:53 GMT"
There might be a bug of course, but your information is not enough to caracterize it.
Search Errors Features like rain precipitation and interior floor information are impressive, but search accuracy is much more critical. For instance, searching for "Arax" directs me to Morocco, even with the search here option enabled. Only searching for "Epicerie Arax" gives the correct result. This is a major issue that undermines the app’s usability, regardless of other features. Fixing search errors should take priority over adding new functions.
Yes you're right, but it's also way more difficult, hence our lag on the subject. Lots of issues talk about better search :)
About the native mobile app : we won't, it's explained here : https://codeberg.org/cartes/web/issues/606
Browser are capable : please describe your Brave bug in a new issue, so that we can fix it if we can.
As for compass, it also should work. We're the first online map to provide compass ;) Should work on iphones too, despite Apple's plans to make the Web underpowered.
hayriokcu
@laem wrote in https://codeberg.org/cartes/web/issues/1863#issuecomment-12025224:
They are retained, forever. Can you describe your experience more precisely ?
My point is not retainability issue, Cartes have no problem on that.
I imagine an applications like layers zero click access, one click access, two ... etc. Very crucial things such as search button, current location button etc should be on top layer (zero click access).
Coming back to language. I think this is an setup based preference it doesn't necessarily on top layer. You enter your language preference once, you login once or connect to your Bluesky once and they all retained in cookies. So my point there should be a settings icon on bottom left corner on PC web, and somewhere in mobile includes those retained preferences. The language option shouldn't be such top layer properties to demonstrate to the user.
@laem wrote in https://codeberg.org/cartes/web/issues/1863#issuecomment-12025329:
About the native mobile app : we won't, it's explained here : #606
Browser are capable : please describe your Brave bug in a new issue, so that we can fix it if we can.
As for compass, it also should work. We're the first online map to provide compass ;) Should work on iphones too, despite Apple's plans to make the Web underpowered.
Okay I am well convinced it is not a good timing to dive into apps with such a limited labor and financial resource. Then I suggest putting the summary of explanations in #606 in the website. Because I searched and couldn't find any explanation why you do not have app and are you planning in future. If you want I can also create a text and let you to put into the website.
I will create a ticket for Brave but definitely not priority. I think the most critical bug problem to focus is search issues. With that problems we cannot expect solid 10.000 users/month in my opinion.
@laem wrote in https://codeberg.org/cartes/web/issues/1863#issuecomment-12025329:
As for compass, it also should work. We're the first online map to provide compass ;) Should work on iphones too, despite Apple's plans to make the Web underpowered.
To avoid confusion, I refer the hardware compass of the device. Whenever I use Google Maps and Apple Maps the arrow in the navigation application detects where my phone directs and rotates the arrow in the app accordingly. This is not the case in Cartes. I have an arrow with a fixed direction I believe doesn't have access to compass sensor of the device in browser level (safari).
n4n5
Thanks for the comments and feedback
For example, I use Brave, but Cartes do not support
It would be nice to know more about that. I already used cartes.app with Brave without. I'm curious the issue you encountered
I will create a ticket for Brave but definitely not priority
Yes please create a ticket. Note that since cartes.app is open source some contributors are more likely to fix and implement some tickets they find more interesting! Every issue is relevant and even more: an issue blocking access to cartes.app is important (since without access you cannot do anything)!
I believe doesn't have access to compass sensor of the device in browser level (safari).
This needs investigation! I think another ticket "compass on iOS" is the way to go ;)
Edit by @laem : here you go : https://codeberg.org/cartes/web/issues/1882
About the languages: I think that the language selector contains many languages and may need a little update to not take the whole screen where there will be more languages. Also the fact that there are Occitan and Brezhoneg languages can invite the user to add or improve languages.
A Dedicated Application
At first I also thought that an app would be useful. But looking at the phone applications gatekeeping made by Google and Apple (https://codeberg.org/cartes/web/issues/606#issuecomment-10909538), I think having a web app is nice
More personnal note:
Cartes.app is still in early development and needs some work, it's always good to have feedback and to report issues. I agree for the majority of the points on this ticket but some points are based on personal opinion which may not be the same for everyone.
Just one example from your text
the most important function is searching
I don't 100% agree for that. Some people just like to go on the map and discover some places (notably with 360 view or satellite view) !
For me, the most import functions are the basics
- can the user access cartes.app?
- is cartes.app working or is there any bugs?
Hi @n4n5 thank you. I will try to create tickets for the points I made in this post.
At first I also thought that an app would be useful. But looking at the phone applications gatekeeping made by Google and Apple (#606 (comment)), I think having a web app is nice
I totally agree after I see the arguments of @laem but I suggest you to summarize those arguments in A propos which I suggested in #1868.
I don't 100% agree for that. Some people just like to go on the map and discover some places (notably with 360 view or satellite view) !
I agree what I have posted here is highly personal, actually that is the point. However please check the other apps when we compare, the only app does not provide direct search bar access is Cartes.
@hayriokcu wrote in https://codeberg.org/cartes/web/issues/1863#issuecomment-12050967:
I agree what I have posted here is highly personal, actually that is the point. However please check the other apps when we compare, the only app does not provide direct search bar access is Cartes.
Oh okay I did not understood it like that. But with the screenshot, I understand now "by default when opening the app, the search bar doesn't show up" that's right?
If that the case, I think it's a bug, since on other devices, the search bar always shows up when opening cartes.app. @laem can confirm it
Could you give use the iPhone model and resolution and create an issue "search bar does not open by default on iOS" after @laem confirms that it's a bug
Thanks
@n4n5 wrote in https://codeberg.org/cartes/web/issues/1863#issuecomment-12051207:
Could you give use the iPhone model and resolution and create an issue "search bar does not open by default on iOS"
Edit this is linked to #1865
I am sorry its my mistake, apparently in Cartes I didn't restarted. So I confirm when I restarted the app it provides a search bar intially. Just now I realize the other apps do not allow me to hide the search bar permanently like Cartes. So there is no bug to be reported at the moment.
pmiossec
@laem wrote in https://codeberg.org/cartes/web/issues/1863#issuecomment-12025329:
Browser are capable : please describe your Brave bug in a new issue, so that we can fix it if we can.
Or you can choose stop using Brave now that you know that it is a browser by a CEO who is very detestable...
@hayriokcu wrote in https://codeberg.org/cartes/web/issues/1863#issue-3931056:
- Advertisement
For info, this is discussed a little here https://codeberg.org/cartes/web/issues/1533
@pmiossec wrote in 1863#issuecomment-12053205">https://codeberg.org/cartes/web/issues/1863#issuecomment-12053205:
@laem wrote in #1863 (comment):
Browser are capable : please describe your Brave bug in a new issue, so that we can fix it if we can.
Or you can choose stop using Brave now that you know that it is a browser by a CEO who is very detestable...
Actually I didn't know there was such a CEO. Thanks for the information I will be going back to Firefox then. I had chosen Brave because of privacy and being protected from telemetry. :/
@hayriokcu wrote in 1863#issuecomment-12053541">https://codeberg.org/cartes/web/issues/1863#issuecomment-12053541:
@pmiossec wrote in #1863 (comment):
@laem wrote in #1863 (comment):
Browser are capable : please describe your Brave bug in a new issue, so that we can fix it if we can.
Or you can choose stop using Brave now that you know that it is a browser by a CEO who is very detestable...
Actually I didn't know there was such a CEO. Thanks for the information I will be going back to Firefox then. I had chosen Brave because of privacy and being protected from telemetry. :/
You still have some alternatives: https://librewolf.net/ , https://zen-browser.app/ or https://vivaldi.com/
@laem
Une autre idée pour recueillir du feedback
Faire un bouton "feedback/retour d'expérience" avec un simple formulaire texte qui transmet directement le texte jusqu'à une issue codeberg spécifique
*Faut pas oublier de forcé a ce que ça soit du texte et pas des images, ou du html
Faire un bouton "feedback/retour d'expérience" avec un simple formulaire texte qui transmet directement le texte jusqu'à une issue codeberg spécifique
Oui j'avais fait ça pour un autre projet, mais on avait des centaines de tickets à traiter par mois. C'était nosgestesclimat.fr, et aujourd'hui cartes.app a le même niveau d'audience. Donc même si le filtre codeberg va clairement filtrer les publics les plus geeks, ça ne me semble pas déconnant de le maintenir pour éviter l'inondation :)
À l'inverse, des tests utilisateur auprès du grand public seraient à mener, c'est certain.
@laem wrote in https://codeberg.org/cartes/web/issues/1863#issuecomment-12123822:
Oui j'avais fait ça pour un autre projet, mais on avait des centaines de tickets à traiter par mois.
Oui je comprends, mais je voulais dire un formulaire qui crée un commentaire dans un ticket, pas un ticket directement. En plus si c'est un seul ticket on peut se désabonner uniquement de celui-ci (si ça spam trop par exemple)
Je pense que le "filtre codeberg va clairement filtrer les publics les plus geeks" peut nous empêcher de voir des problèmes "bateaux" que beaucoup de gens ont. Par exemple des problèmes d'accessibilité que les plus geeks ne perçoivent pas