Taking the (finite) breadth of query data for Huntsville and Madison and putting it in a database that updates with the app could remove the need for online access, and possibly reduce search time in the event of variable mobile internet speed. Also, further in the future, it might circumvent the issue of Google API query fees (>1,000 in 24 hours, or >150,000 with ID verification). This would be an advantage of a local app like this over apps like Yelp and Google Maps that don't have the option of saving the breadth of their (global scale) data set offline to the user's phone without massive hard drive consumption.
Taking the (finite) breadth of query data for Huntsville and Madison and putting it in a database that updates with the app could remove the need for online access, and possibly reduce search time in the event of variable mobile internet speed. Also, further in the future, it might circumvent the issue of Google API query fees (>1,000 in 24 hours, or >150,000 with ID verification). This would be an advantage of a local app like this over apps like Yelp and Google Maps that don't have the option of saving the breadth of their (global scale) data set offline to the user's phone without massive hard drive consumption.