If the searchbar is selected but there is no content in it, selecting a book will crash the app. This may be due to checking condition in tableView(cellForRowAt) and tableView(numberOfRows..) ignore the empty string case and return the book list at that time.

The color sort allows the user to sort books by their icon color (I figure the order of the colors doesn't matter so I just made it easy and did it alphabetically: Red --> Purple --> Green --> Gold --> Blue). We won't want to keep this as it is because we will not want to have five sorting options for the reading books. I was thinking we could just have one option for "% Complete" rather than two different options for sorting by progress. What would you think about that?

The ReadingBooksView will be barely fill with a lot of books at a time, but the CompletedBooks will totally have the potential to be filled with lots of books, since those are the books that users have read in all time. Therefore, a search bar for the CompletedBooksView may be necessary.

If you do it from the Book Details page then it just resets to zero. But if you do it directly from the reading books tab then it will crash and be zero when you re-open the app

The first thing users do when they try to change the status of a book is tap on it and are surprised that there is not a button at the bottom that allows you to move it to a different tab or delete it. They do not initially resort to swiping, but eventually after messing around for a bit can figure it out. The suggestion was to include a bottom of the BookViewController saying "Move to ____"

If user leave any of the field in the add book view blank, the bug will be crashed. This happens due to the force unwrap text from those fields.
Suggestion for solution:

• Make the SAVE button not active until all the fields are filled

The user might not know what the color selector means. Based on user testing

Right now, the tableView will display any books that has been modified the current page to be on the top. However, changing the current page in the BookDetailsView will not update this variable, making this not consistent in the app design.
Suggested solution:
Since whenCreated will always be updated if currentPage is set to new value, we can take advantage of this by set a didSet for currentPage:

currentPage: Int {
 didSet {
      self.whenCreated = Date()
}

It would be more intuitive if the keyboard would pop up when they hit "edit" and disappears when they hit "save"

I think that because we are having author's name in the other 2 scenes, it should be included in the Reading Scene as well, so our app will have a consistent theme.

The default filter is Recent, but all the scenes are displaying the default is A-Z. However, the books are displaying is correct order (Recent). This maybe problem from setting up UISegmentedControl programmatically.

When user tap on Add button to add a book, the titleTextField in the AddBookView should become the firstResponder immediately, since there is no other things user can do on that screen.

Users were a little confused because we do not give a number for % complete, so they assume that it is supposed to sort by current page number. One person said it would help to give the percentage so that they could see it

Right now, the app is storing the icon color name of the book to Realm, and base on this name, the app looks up a given dictionary (inside BookManager) to find the corresponding image of each color. In order to use the feature of getting book's information (including cover image) from GoogleAPI, the cover image might need to be stored into Realm.

On the process of researching for the problem with users not know about how to use the swipe function, I see some examples that we can make a tutorial scene, only appear on the first time the app is launched, that displays a simple picture showing that user can swipe left and right to interact with the book. I believe that this will solve many of our solution.

User thinks that you do that while editing the book. Based on user testing

The PF was confused as to what exactly it does. The other two people I had test it were able to figure it out very quickly. One person, though, asked what it does and was expecting for it to have some functionality. He suggested adding another sorting option to sort by color so that if users want to, they would have the option to use the colors to sort by genre or, really, however they want to utilize it

The AddBookView now is having too much spaces on top, making the keyboard cover the color buttons if it appear. Users may not see that color buttons if they are using keyboard. Also, the keyboard is covering the textField of current page and total pages now if tested on iphoneSE screen size.

Users may want to sort their completed books by rating, so they can see the one that they have rated highest (maybe to suggest it to friends, or to pick up some old good book for re-read). Rating can be under the name of author in the cell (so it looks like the AppStore when it displays all the apps)

When you tap on the search bar in "History" and go from "History" to "Reading" and back to "History", the search bar will be in its active state when you re-open the "History" tab