For searches by flight code, we might need to convert the airline's IATA code to ICAO before sending the search query to the API – this mapping can be imported as csv directly to the android device
If we're unsure whether a substring represents an IATA code or not (e.g. in "air SUnshine", is "SU" an IATA code?), I say we just make 2 queries and combine the results... but if you think it's possible to build a regex to differentiate then that's okay too
For searches by airport code, or airport name, we can just look through that same csv directly
If it's too difficult or impossible to search by departure/arrival city, then we don't need to do it