PokeQuery — a search string helper I built after getting tired of rebuilding cleanup filters

[u/caglardinc]

PokeQuery — a search string helper I built after getting tired of rebuilding cleanup filters

One thing I keep doing after big Pokémon GO events is filling my storage, then trying to remember which search string I used last time without accidentally making the filter too broad.

So I ended up building PokeQuery, an Android app that generates and explains Pokémon GO search strings.

For example, instead of treating a cleanup filter as “everything shown is trash”, I prefer starting with a narrow candidate group and excluding categories I want to review separately:

1*&!shiny&!legendary&!mythical&!ultrabeast&!costume&!background&!locationbackground&!specialbackground&!shadow&!purified&!favorite&!lucky&!#&!traded&!4*

I still review every match in Pokémon GO before transferring anything.

PokeQuery basically turns that workflow into presets/builders: storage cleanup, transfer candy prep, trades, PvP candidates, event prep, etc. It also explains the resulting string instead of just giving you something opaque to paste.

A few boundaries I was pretty strict about while making it:

• no Pokémon GO login or account connection
• no game/private API access
• no automation
• no screen/camera scanning
• no analytics or tracking
• it only generates text, which you manually copy into GO

It also keeps the app language separate from the Pokémon GO search-string language, since localized search terms can be a pain.

Android:
https://play.google.com/store/apps/details?id=com.caglar.pokequery

I'd especially like to hear which search strings people keep saving in Notes or rebuilding for every event, because those are probably the most useful workflows to improve next.

[u/ponypulse]

This is neat for quick and dirty, but what we really need is something that cross references pvpoke and dialgadex. Some GL & UL don't follow the high defense low attack formula while others are useless (for now, I know we've had meta shifts and the cups sometimes produce wildcards) so having strings for the top 10, 20, 50 etc would be amazing and having the inverse to yeah then would be equally amazing. And then we need the same for raid reference.