Android Mobile Engineer - Technical Test

Summary

Looking at the design spec attached, you will see a market watchlist of currency pairings. Your task will be to recreate this screen which will contain some dynamic elements.

Obtaining the data

There are a few options:

a publicly-accessible API available here however this has been less reliable recently.
sign up to a brokerage that offers API access such as Oanda. You should never have to pay any fees for forex pricing data.

Specific requirements:

Use Kotlin (Android), or SwiftUI (iOS)
Use MVVM
The app should available on both landscape and portrait mode
The amount of forex pairs displayed will be determined by the amount available on the API. (Please choose 5 forex pairs at least)
Because the API DOES NOT provide Sell/Buy prices, you can assume that the price returned from the API is the mid-price and create the sell/buy price by adding/removing 1-10% randomly from that price (the random element would simulate the variable spread that you would see from a real broker).
The prices need to be regularly updated (e.g.: per second). (You can add the local MOCK service for the prices changing.)
When the prices update, the % change Needs to also update, ordinarily this would be calculated from the day’s open price, but since the API DOES NOT provide that, you can base the % change from the first price you receive once you launch the app. The UI should change to reflect the increase or decrease.
Assume the account base currency is in USD:
- Imagine you go long $10,000 USD worth units on Each forex pairing at the first price you received.
- The Equity is calculated by the current value of your total assets, it is also expected to change dynamically.
- The Balance should be $10,000 USD * Number of forex pairings available.
- The Margin / Used values on panel can be hardcoded $12,345.

Include Unit Tests where appropriate

Submission

Push the app to a private GitHub repo and collaborate with GitHub user ywsing-msrl.

How we will judge the test:

We will evaluate how closely the finished result matches the design. In terms of the code, providing tests, documentation, demonstrating architectural knowledge and error handling, using threading correctly where appropriate and especially correctly leveraging the functional aspects of the language (Kotlin/Swift) are all things that would be considered beneficial.