** Caveat: The OpenBanking API doesn't allows Cross Domanin Requests (see cors); so had to use a some-what unstable web proxy. Still should work 95% of the time.
Solution: Use our own "middleware server" that makes the call on our behalf, probably will extend this by saving the results in our own database (for data that doesn't change too often; like ATM location) and have some sort of back-end job (cron job) that will populate our database.
For the scope of this demo, there wasn't enought time to implement. On the local development server there is a file that handles the proxy through the Angular CLI
proxy.conf.json.
Clone project and run npm i to install all dependencies.
Run ng serve for a dev server. Navigate to http://localhost:4200/ on any browser of your choice.
-
lodash (lodash) - Allows for more readable code, and offers a shorthand for some trivial calculations / operations
-
@agm/core (Angular Goolge Maps) - Prebuilt components and directives for common Goolge Maps elements.
Additionaly, there are a number of things that could have been done if this was to be an actual feature, just to name one; Having a fall-back if someone doesn't allow the geolocation permission. Would show error message and / or use their IP address to get a rough location.
Map View: The map view shows the nearest 30 ATMs (from Barclays & Natwest) around you (initial start position).