Remove pre-populated prefix from cache search

[+-KROP-]

When I'm searching for a specific cache on the app I'm usually copy/pasting it so having the "GC" prefix pre-populated just adds 3 extra button presses to delete it or you end up with GCGC12345

 

It adds enough extra time and interrupts the user flow enough that I.felt it worth making the post rather than just deleting it each time I do a search for a specific cache!

[+Max and 99]

2 minutes ago, -KROP- said:

When I'm searching for a specific cache on the app I'm usually copy/pasting it so having the "GC" prefix pre-populated just adds 3 extra button presses to delete it or you end up with GCGC12345

 

It adds enough extra time and interrupts the user flow enough that I.felt it worth making the post rather than just deleting it each time I do a search for a specific cache!

Yes!!

[+kunarion]

Maybe 50% of the time, I’m trying to remember/type at least the part of the code that comes after “GC”.  The code seen someplace where “copy” wasn’t feasible such as on my handheld GPS.  But, yeah copy/paste would be more convenient for the other 50%.

 

 

Edited April 13, 2021 by kunarion

[+Max and 99]

Why is it only the GC is pre-populated when searching for a geocache but not TB when searching for a trackable? Just remove the GC!!

I get it. Travel bugs have two different numbers and geocaches don't.

I still wish the GC would be removed.

Edited July 26, 2021 by Max and 99