fixing google Geocoding API repetitive request in IOS and Android application

Hello? I'm an experienced Website & Graphics Designer with a degree in Computer Science and a masters in cyber-Security and Computer Forensics. ( Documents available on request.) I have been working as the head of Cyber Security for Standard Media Group (leading media group company in the country) for 4 years key responsibilities involving: website optimization, performing upgrades to all the company’s security systems, security auditing, Approval of online uploads and downloads ensuring concrete security is maintained. I have been doing graphic designing and website development for 13 years and I’m fully vast with adobe photoshop, adobe illustrator, adobe dreamweaver, wordpress, payment gateways etc. I have read your project description and based on past experiences, fell that I’m fully equipped to deliver on your task within your budget limit and with professionalism taking the shortest time possible. Thank you for viewing my bid and I thank you for your project. Kindly contact me so as to discuss more on your project. Regards, Kenneth M. Computer and Web Security Systems Expert. Website Designer and Graphics Specialist.

Dear client, how have you been? I've read your project description carefully. Presenting this proposal with 100% confident. How about discuss in chat? Waiting for your reply. Best regards.

I have over 5 years developing mobile applications in different sectors. From your description it sounds like you will need to cache the results from the search instead of making a fresh call to the API when the customer goes back to the search page. This will ensure that the API is only called when someone enters something in the search. Once the results are cached then that is what should be loaded on the page instead of a call being done again to the API. A new call to the API should only happen if someone enters something in the search box. This should reduce the number of API calls. This will require a review of the search code for both the app and the website to see the best way of implementing the change without disruptions. Thank you for your consideration. I hope to hear back from you.

Hi, it is a tricky situation you have there! It might be a bug in the system, should it be a server (back-end) we can cache easily {great if you have a cloud plan} from my experience with google's geolocation API services, there is possibility that the client (web|mobile apps) could potentially need to enable cookies. I can offer you lasting solution depending on the hosting plans you have for your server. Thus, feel free to to inbox me that we can chat more solutions for your setup architecture, look at the issue and hopefully begin the work not less than 24 hrs. {my working time = GMT +3hrs}