CIS 3515 Lab Worksheet 10 An application that will allow a user to search for and store a list of stocks, called their portfolio, for which they'd like to keep track. The application should use the standard dual-pane display mode, with a list displayed in one pane (Portfolio pane), and details displayed in the other (Stock Details pane). Large screens and landscape layouts should display both panes simultaneously (dual-pane mode), while smaller screens in portrait mode should display one pane at a time (single-pane mode) starting with the navigation pane. A user must be able to: Add a stock to their portfolio by using the stocks symbol (e.g. MSFT for Microsoft) The search function should be initiated from the action bar Have their portfolio persist across application restarts (the data must be saved) The various methods to do this will be discussed in upcoming lectures, but you can get a head start here: https://developer.android.com/guide/topics/data/data-storage.html The main interface of the application must implement fragments. The navigation fragment will display a list of stocks that the user has previously saved to their portfolio. They should be displayed in a ListView (or similar mechanism that allows seeing multiple stocks at once) that displays the stock symbol for each stock saved in the portfolio. Selecting a stock from the navigation fragment will display details of that stock in a details fragment. Those details must include: The Company Name (see appendix ii) The 1 day stock chart (see appendix ii) The current stock price (see appendix ii) When your application is running, it should continuously update all the stocks stored in a portfolio, even if a user is not currently looking at that stock. This must be done with a service. The service should be started once the application begins and continuously update the stock price in the background (update each stock every 1 minute or other reasonable interval). When it receives an updated stock price, it should save the information to a file. This file can then be read by the stock details fragment whenever the user attempts to view a particular stock. This way the user will always see a price instantly. (You can attempt to have the stock details fragment continuously update the displayed stock price at the same interval that the service updates the file, but that is not a requirement), Upon launch, if the application does not have any stocks saved, it should display a message in the navigation fragment instructing the user to add a stock. The message must be fixed (a textview inside the navigation fragment, you must not use a temporary message mechanism such as a toast). All string displayed to the user must be retrieved from a string resource. Additionally, there must be an additional string resource file in a non-English language of your choice. Please see the appendix II for the APIs to obtain all required information.