Fat Llama Frontend Challenge

Challenge:

To keep the Fat Llama business moving, our Operations team reviews transactions, verifies user identities and deals with many other user support issues.

In this challenge, we would like you to build a feed for our ops team to monitor the most recent transactions and view information about that transaction and that user, and approve transactions if it is all correct.

If you are applying for a web frontend-focussed position, build this as a web app. If you are applying for a mobile-focussed position, build this as a mobile app. It is your choice what technologies to use, but please include a short (<500 words) summary explaining your choices in terms of technology, structure and design.

Set up

Start by cloning this repo (please do not fork it, see instructions). Bitbucket offers free private repos if you don't want to use a public one. Please do not name your repo 'fat llama' or anything similar (we don't want future candidates copying your code).

You'll find a pre-built binary for Linux, OSX and Windows in the repo which provides a sandbox backend environment for you to build your frontend against. We promise that these binaries do nothing underhanded!

Requirements:

Feed view: where ops team can see all most recent transactions, ordered either by most recent or by status.

Transaction view: where ops team can see information about a transaction, approve the transaction.

Endpoints:

• GET /transaction/:id
• GET /transactions/:page
• PUT /transaction/id
• GET /user/:id

Documentation for the API and instructions for the challenge are deliberately sparse as we want to see how you make decisions based on incomplete data.

Criteria/Guidance

• The challenge is about your grasp of user experience as well as about your coding ability
• Use of frameworks and libraries is up to you. We suggest you use a boilerplate (e.g. create-react-app for web) to get yourself up and running quickly and save time.
• Try to implement appropriate separation of concerns & modular code
• Think hard about naming of functions and variables
• Code style & file structure is up to you, but make sure it is consistent and legible

Checklist for the challenge

• Duplicate this repo (please do not fork it, see instructions). Bitbucket offers free private repos if you don't want to use a public one. Please do not name your repo 'fat llama' or anything similar (we don't want future candidates copying your code).
• Build frontend with feed view and transaction view
• Ensure all code is sufficiently tested
• Write brief summary on the approach you took, the tools you used, and anything you would do differently given more time (max 500 words)
• Include instructions on how to build/ run your solution
• Send us a link to your new repo.