Local caching (persisted to disk on the Android device)
Server-side caching
They should be entirely transparent (it should be possible to call the flight API directly from the device, bypassing any caching layers, and get the exact same result)
Add in the logic for all API requests to check for API key flag before fetching (can fetch more frequently if API does exist; otherwise, just fetches on load)
Depending on #27, gotta check the text field the user inputs the API token to
Add in the caching logic (from the Proxy Design Pattern)
Save us money on the 30 cent search by caching the request
Planning to have 2 layers of caching:
They should be entirely transparent (it should be possible to call the flight API directly from the device, bypassing any caching layers, and get the exact same result)