10
105
Fork
You've already forked web
30

Focus the search bar on desktop by default #1865

Open
opened 2026年03月24日 14:32:32 +01:00 by laem · 18 comments
Owner
Copy link

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.
source

Well Google Maps has no larger top bar but yes it is automatically focused, good idea :)

> 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. > [source](https://codeberg.org/cartes/web/issues/1863) Well Google Maps has no larger top bar but yes it is automatically focused, good idea :)
Author
Owner
Copy link
![image](/attachments/2e99ca36-0133-4776-b555-4228ccd66382)
453 KiB
Author
Owner
Copy link

Oh, @hayriokcu you probably meant on mobile ? If so, can you share illustrations of yours ? I don't have Gmap on my phone (can't install) and the Web version is quite different from the mobile version (that often changes, by the way).

Oh, @hayriokcu you probably meant on mobile ? If so, can you share illustrations of yours ? I don't have Gmap on my phone (can't install) and the Web version is quite different from the mobile version (that often changes, by the way).
Author
Owner
Copy link

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.

The search bar should not be hidden on cartes.app. Can you share your experience visually or more precisely ?

> 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. The search bar should not be hidden on cartes.app. Can you share your experience visually or more precisely ?

@laem wrote in #1865 (comment):

Oh, @hayriokcu you probably meant on mobile ? If so, can you share illustrations of yours ? I don't have Gmap on my phone (can't install) and the Web version is quite different from the mobile version (that often changes, by the way).

There is no focus on mobile, it would open the virtual keyboard!

@laem wrote in https://codeberg.org/cartes/web/issues/1865#issuecomment-12025170: > Oh, @hayriokcu you probably meant on mobile ? If so, can you share illustrations of yours ? I don't have Gmap on my phone (can't install) and the Web version is quite different from the mobile version (that often changes, by the way). There is no focus on mobile, it would open the virtual keyboard!
Author
Owner
Copy link

Yes, there's something I don't understand here.

Yes, there's something I don't understand here.

@laem wrote in #1865 (comment):

Oh, @hayriokcu you probably meant on mobile ? If so, can you share illustrations of yours ? I don't have Gmap on my phone (can't install) and the Web version is quite different from the mobile version (that often changes, by the way).

image

Hi @laem, yes I referred the mobile. Here you have the comparison. That could be nice a readily available top search bar rather then clicking on bottom left corner.

@laem wrote in https://codeberg.org/cartes/web/issues/1865#issuecomment-12025170: > Oh, @hayriokcu you probably meant on mobile ? If so, can you share illustrations of yours ? I don't have Gmap on my phone (can't install) and the Web version is quite different from the mobile version (that often changes, by the way). ![image](/attachments/dffbcc47-920e-43e6-9714-e98a7a101753) Hi @laem, yes I referred the mobile. Here you have the comparison. That could be nice a readily available top search bar rather then clicking on bottom left corner.
726 KiB

Also when we click to the bottom left button for search button. It occupies much more space than it suppose to be. For me the one on the right could be much better default view. Of course you need to reposition compass and current location icons.

image

Also when we click to the bottom left button for search button. It occupies much more space than it suppose to be. For me the one on the right could be much better default view. Of course you need to reposition _compass_ and _current location_ icons. ![image](/attachments/9df949ed-127f-431f-a3a5-4c65d0794b3a)
961 KiB
Member
Copy link

@hayriokcu

Is your bug also "by default when opening the app, the search bar doesn't show up"

that's right?


I agree that the language selector makes the bottom space bigger than necessary

@hayriokcu Is your bug also "**by default when opening the app, the search bar doesn't show up**" that's right? --- I agree that the language selector makes the bottom space bigger than necessary
Member
Copy link

#1863 (comment):

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.

https://codeberg.org/cartes/web/issues/1863#issuecomment-12051615: > 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.

En listant les tickets qui parlent de la barre de recherche, je remarque que ce ticket est en fait un doublon de #713

En listant les tickets qui parlent de la barre de recherche, je remarque que ce ticket est en fait un doublon de #713
Author
Owner
Copy link

For me the one on the right could be much better default view. Of course you need to reposition compass and current location icons.

We went for Apple's take on map design, not Google's. I'm pretty sure it's the good options : smartphones are enormous these days, and your fingers are at their bottom, not at their top.

> For me the one on the right could be much better default view. Of course you need to reposition compass and current location icons. We went for Apple's take on map design, not Google's. I'm pretty sure it's the good options : smartphones are enormous these days, and your fingers are at their bottom, not at their top.

I agree Google top bar is not enough ergonomic bottom is a better approach.
However, if I compare the apps uses the bottom active notch: Cartes.app has:

  1. The narrowest search bar, that's good enough but could be better to get a little bigger
  2. The bottom bar covers too much space, given there is the light blue top bar (at the top of the screen) which is unusable (and idk why the color is not dark blue but light). Therefore, we have the smallest map area amongst other apps.
  3. Amongst them Cartes has the clunkiest bottom bar. It doesn't move smoothly. Sometimes you have to directly use the notch part to move. That is not an issue for the other apps.
  4. Again on the bottom bar personally the "saved locations" such as Home, Work etc. are more important than filter icons (resto, cafe, etc.). As you see Here nicely applies that. Imagine the user is in somewhere and wants to quickly check the route to home. They can open the app and click only Home to check the possible route. If they want to access to the filter icons they click to search bar. it is more logical for me, first click to the search bar then the filter icons appear.

image

  1. I am not very fan of having a exhaustive text explaining the functions and mentions Google and Apple. Actually Cartes.app alternative to other navs as well. So a simple line saying "A free and open-source map." is way more sufficient and readable by people. And in the mobile app the language bar could be on the right side of the text, so it wouldn't occupy more vertical space.

image

I agree Google top bar is not enough ergonomic bottom is a better approach. However, if I compare the apps uses the bottom active notch: Cartes.app has: 1. The narrowest search bar, that's good enough but could be better to get a little bigger 2. The bottom bar covers too much space, given there is the light blue top bar (at the top of the screen) which is unusable (and idk why the color is not dark blue but light). Therefore, we have the smallest map area amongst other apps. 3. Amongst them Cartes has the clunkiest bottom bar. It doesn't move smoothly. Sometimes you have to directly use the notch part to move. That is not an issue for the other apps. 4. Again on the bottom bar personally the "saved locations" such as _Home_, _Work_ etc. are more important than filter icons (resto, cafe, etc.). As you see Here nicely applies that. Imagine the user is in somewhere and wants to quickly check the route to home. They can open the app and click only Home to check the possible route. If they want to access to the filter icons they click to search bar. it is more logical for me, first click to the search bar then the filter icons appear. ![image](/attachments/d012ef7b-2642-4fba-b72c-189c78cad80a) 5. I am not very fan of having a exhaustive text explaining the functions and mentions Google and Apple. Actually Cartes.app alternative to other navs as well. So a simple line saying "A free and open-source map." is way more sufficient and readable by people. And in the mobile app the language bar could be on the right side of the text, so it wouldn't occupy more vertical space. ![image](/attachments/a5205069-d9cd-4445-9a3b-87edc9697d45)
1.6 MiB
324 KiB

@hayriokcu wrote in #1865 (comment):

4. Personally the most important thing is saved location to appear like Home, Work etc. rather than filter icons (resto, cafe, etc.).

Save some favorites and you will see them and the explanation text won't be visible anymore on the default opening snap point.

And so most of the points will be solved 😉

You raise some good points overall but my point of view it's a lot of time consuming adjustments that requires a lot of discussions.

Are youhable to fix some of them if we settle on changes to do?

@hayriokcu wrote in https://codeberg.org/cartes/web/issues/1865#issuecomment-12170988: > 4\. Personally the most important thing is saved location to appear like _Home_, _Work_ etc. rather than filter icons (resto, cafe, etc.). Save some favorites and you will see them and the explanation text won't be visible anymore on the default opening snap point. And so most of the points will be solved 😉 You raise some good points overall but my point of view it's a lot of time consuming adjustments that requires a lot of discussions. Are youhable to fix some of them if we settle on changes to do?

Hi @pmiossec, thank you for your answer indeed that solves 4 and 5.

And in general, I am sorry if my comments sound time consuming. I am just a user, as I have mentioned #1863 0.Context. I would like to contribute in coding level but it is beyond of my capability. I will be more careful for the following comments.

Hi @pmiossec, thank you for your answer indeed that solves 4 and 5. And in general, I am sorry if my comments sound time consuming. I am just a user, as I have mentioned #1863 0.Context. I would like to contribute in coding level but it is beyond of my capability. I will be more careful for the following comments.
Member
Copy link

@hayriokcu wrote in #1865 (comment):

And in general, I am sorry if my comments sound time consuming. I would like to contribute in coding level but it is beyond of my capability. I will be more careful for the following comments.

All idea are welcomed. They just need to be approved and a (random) contributor can implement it ;)

I think cartes.app is providing multiples things that the user doesn't know at first sight. E.g the favorites mentioned by @pmiossec ;)

@hayriokcu wrote in https://codeberg.org/cartes/web/issues/1865#issuecomment-12178635: > And in general, I am sorry if my comments sound time consuming. I would like to contribute in coding level but it is beyond of my capability. I will be more careful for the following comments. All idea are welcomed. They just need to be approved and a (random) contributor can implement it ;) I think cartes.app is providing multiples things that the user doesn't know at first sight. E.g the favorites mentioned by @pmiossec ;)
Author
Owner
Copy link
  1. Bigger mobile elements : yes ! #1926
  2. The bottom bar covers too much space, given there is the light blue top bar (at the top of the screen) which is unusable (and idk why the color is not dark blue but light). Therefore, we have the smallest map area amongst other apps.

We can't act on the blue bar at the top, nor set it to dark mode I'm afraid.

Therefore, we have the smallest map area amongst other apps.

Not exactly : Google has lots of area used by non-map elements. Also : we have to advertise oursleves to new users. Big tech don't.

  1. Amongst them Cartes has the clunkiest bottom bar. It doesn't move smoothly. Sometimes you have to directly use the notch part to move. That is not an issue for the other apps.

Yes, precisely because big tech reject the Web, and hence bottom sheet libraries are quite bad on the Web, but perfectly engineered on mobile :/ Follow this subject here : #1027 (comment)

Low hanging fruits possible !

1) Bigger mobile elements : yes ! #1926 2) The bottom bar covers too much space, given there is the light blue top bar (at the top of the screen) which is unusable (and idk why the color is not dark blue but light). Therefore, we have the smallest map area amongst other apps. We can't act on the blue bar at the top, nor set it to dark mode I'm afraid. > Therefore, we have the smallest map area amongst other apps. Not exactly : Google has lots of area used by non-map elements. Also : we have to advertise oursleves to new users. Big tech don't. 3) Amongst them Cartes has the clunkiest bottom bar. It doesn't move smoothly. Sometimes you have to directly use the notch part to move. That is not an issue for the other apps. Yes, precisely because big tech reject the Web, and hence bottom sheet libraries are quite bad on the Web, but perfectly engineered on mobile :/ Follow this subject here : https://codeberg.org/cartes/web/issues/1027#issuecomment-11189528 Low hanging fruits possible !

thanks @laem! For top bar I totally understand, only aesthetically it would be quite nice turning to the dark blue in dark mode activated.

  1. Amongst them Cartes has the clunkiest bottom bar. It doesn't move smoothly. Sometimes you have to directly use the notch part to move. That is not an issue for the other apps.

Just to clarify the point 3. When I compare (all in mobile) Here, Waze and Apple Maps it appears Cartes have some response issues. Such as the scrolling up and down stucks occasionally so I have to use the notch itself to use the bottom bar. Also the motion is a bit lagging compared to others. And the other apps perform very similar behavior not many issues on responsiveness and lagging.

thanks @laem! For top bar I totally understand, only aesthetically it would be quite nice turning to the dark blue in dark mode activated. > 3. Amongst them Cartes has the clunkiest bottom bar. It doesn't move smoothly. Sometimes you have to directly use the notch part to move. That is not an issue for the other apps. Just to clarify the point 3. When I compare (all in mobile) Here, Waze and Apple Maps it appears Cartes have some response issues. Such as the scrolling up and down stucks occasionally so I have to use the notch itself to use the bottom bar. Also the motion is a bit lagging compared to others. And the other apps perform very similar behavior not many issues on responsiveness and lagging.
Contributor
Copy link

Pour éviter le clique inutile, il faut utiliser en html l’attributs autofocus ou en js la fonction [input element].focus()

Pour éviter le clique inutile, il faut utiliser en html l’attributs autofocus ou en js la fonction [input element].focus()
Sign in to join this conversation.
No Branch/Tag specified
master
chore/i18n-missing-strings-step-3
abostats
SynchroM-master
gps
embeddings
lysios-patch-5
lysios-patch-4
lysios-patch-3
lysios-patch-2
lysios-patch-1
abo-serveur2
clim
zone-en-favori
categories_toujours_visibles
rechercher_ici_avant_resultats
test-2365
panoramax-contribution
add-categories-validations
gel-bug-prod
osm-note-2
broken
wikidata_booking
fuse7.3
lysios-patrimoine-3
gps2
atproto-fix-2
styles-secondaires-mais-maison
atproto-scopes
itineraire-printemps-2026
modal-sheet-5.6
nlnet-cost-climate-perf
pb-icones-religieux
couvoiture
etiennejr-patch-2
meteo-fainéante
logo-static-url
poc-page-vitrine
remove-compass
test-reproduce-1795
display-cycleway-lanes-2
poc-image
add-media-condition
mapterhorn
test-indoor-equal
outdoors-VS-indoorEqual
hiking-colors
fix-blog-typing
poc-next-international
fix-map-style-modal-not-closing
i18n
hide-odd-zoom-levels
filter_categories
resume_wikipedia
deplacement_bouttons
fix-1095
mobile_permettre_selection
position-carte-initiale
dégradé-icônes
better_wikipedia
affichage_donnees_wikidata
mobile-permettre-selection
avis-details
perf-seo
modal-sheet-5
plans-novembre
display-cycleway-lanes
fix-1227
fix-1234
etiennejr-patch-1
update-1240
fix-1236
fix-1131
photon-search-street
fix-1221
article-avis
net-haut-zoom
baies-moins-visibles
belles-fiches-lieu
fix-1157
bug-page-vie-privée
use-watername
fix-1176
carte-du-onde
fix-1166
page-news
tchou
add-icon-alias
vitesse
photon-opensearch
private-in-italic
bâtiments-3D
merge-categories
handle-private-highway
improve-findcategory
injection-pmtiles
fix-1128
check-icons
update-readme
category-rugby
bug-position-carte-vs-lieu
limites-vitesse
improve-find-category-from-tags-v2
integrer
document-osmfeature
translate-document
velo-fin-aout-25
velo-ete-2025
moins-de-maptiler
planet-pmtiles-tilemaker
fix-1048
panoramax-leger
plume
horaires-i18n
planet
maj-deps-juillet-2025
improve-find-category-from-tags
bug-encart
interactions-encart-mobile
clic-on-station
fix-1028
fix-1014
edit
add-big-rivers
add-shortbread-tiles
handle-deleted-osm-elements-v2
codeberg
improve-useEffect
immoloc
update-dashboard
analyze
terradraw
sombre2
calendar
poi-sprites-using-svg
style-sombre
sprites
annuaire
motis-gtfs-attributes
next-styled-components
dev
cool2
cool
panoramax-angle
env-static-urls
borders-only
panoramax2
intelligence
debug-iles
nouveau-serveur
france-protomaps
turbo
fouss/cartes-#338
blog2
legislatives
presentation
pas-de-geoloc-si-hash-different
protomaps
vaul
carte-trains
citiz
maj-paquets
icones
ui2
bblog
voyagevoyage
test-image-origine
bugimagefin
searchParams
voyage
avion
perf
studio
piscine
journée
année
journée-transition
score-dès-acceuil
fix-space-problem
rebase-5août
correspondance
règles-séparées
indeps-acre
demo
indeps
indeps-cachés
indication-temps-plein
indeps-refactor-simulations
indeps-vue-comparaison
indeps-inversion
barème-continu
indeps-démo
textes-branches-sécu
engine-enum
2019
transport
publicodes
as
infrance-nouvelle-landing
better-translation
co2
simplifATMP
controle-SMIC
webi18n
bug-avantages-en-nature
revert-352-infrance-navigation-v2
laem-patch-1
robots.txt
improve-perf
iframe-bugfix
quickfixes
lib
irsimple
hiringinfrance.com
dégradé
refstate
johan
zrr
logo-interactif
revert-216-improve-tracking
redesign2
zrr2
fixtrad
correction-salaire-brut
petit-state
alien-consolidate
translate-ui
npm
alien-brut-net
translatable
différent
ir18
fix-typo
add-tracking
fix-collect-missing
défauts-partout
fix-double-unfold-three
fix-double-unfold
versement-transport
blocker-questions
v3
v2.1
v2
v1
v0.6.4
v0.6.3
v0.6.2
v0.6.1
v0.6.0
0.7.0
v0.5.1
v0.5.0
v0.4.2
v0.4.1
v0.4.0
v0.3.3
v0.3.2
v0.3.1
v0.3
v0.2
v0.1-cdd-alpha
v0-démo-tag-nav
Labels
Clear labels
🎨 Design
À propos de l'interface et de l'UX
💡 Idée
Nouvelle feature à intégrer
question
Further information is requested
🌍 OSM
À propos de l'affichage et l'édition des éléments OSM
🌱 Amélioration
Amélioration/fix de l'existant
🐞 Bug
Something isn't working
📊 SEO
📋 Catégories
À propos des catégories de recherche et de l'annuaire
📖 Wiki
📝Avis
A propos de la fonction avis et de bluesky
📢 Oyez
📷 Photos
A propos des photos (sources, affichage)
🔍Recherche
A propos de la barre de recherche et de photon
🔥 Actuel
🔧 tech
🖌 Styles
Styles de la carte
🧝i18n
🧪 R&D
🚍 Transports
🚙 Voiture
🚨Prioritaire
Ticket à traiter rapidement
🚲Vélo
Cartes
climat
Communication
demo
Cette branche doit être déployée comme une démo
dependencies
Pull requests that update a dependency file
javascript
Pull requests that update javascript code
Pas urgent
Plein-air
Tuiles
Verso
Vieux
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
6 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
cartes/web#1865
Reference in a new issue
cartes/web
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?