niccorder / fbu-mvp Goto Github PK

In order to be open to our users, we will display the company name/icon on each article item in the news list. There must be a way to identify the news source for each article, but implementation of UI is up to the assigned engineer.

Set up parse server with herko, and make sure that the parse-dashboard works.

When the user clicks on the name, or icon of a company on an article item in the news adapter, we should show a screen which displays all information (including liberal bias percentile) to the user.

This will help the user understand how biased the news article may be based off the data source.

The news adapter should be able to sort by time of article creation, and the user should be able to click the triple dot menu to select how to sort the articles.

The only selections available to the user should be:

• Oldest first
• Recent first

Although the functionality for ErrorCallback and SuccessCallback is absolutely necessary, it seems odd to have the functionality split. There may be some rare cases where we will only care about one of these callbacks, but in almost all cases we care about both.

We need to circle back post-MVP release and see if this statement holds true!

PULL REQUEST #8

Implement the functionality to pull-to-refresh on the news list. The data will be mocked out, and always the same, but we should have the functionality implemented and ready to work once the implementation has been swapped out.

We should have a triple dot menu on the action bar which users will be able to click to preform actions on article sorting/viewing.

Once the MVP has gone out, we will need to move the article diff calculation to a background thread as to ensure we do not block the main thread.

PULL REQUEST #9

The article viewing fragment should allow users to read an article. It will open on click, and can have extremely basic animations for now.

A fragment will be used to allow for nicer animations should time permit.

The application should have a splash screen to make the cold-start transition cleaner, and more friendly to users.

The launching activity for the application should always be the splash screen (for deeplinking + cold starts)