maychell / upcoming_movies_mobile Goto Github PK

Currently, our ​BaseActivity​ is solely used to hold a reference to the ​api object. We don't feel this is a strong enough reason to have a ​BaseActivity​ and we feel this leads to some issues (e.g. each activity holding a different ​api​ instance even though they could share the same).

We want to allow our users to search for movies from the TMDb API by entering a partial or full movie name.

We currently have all our logic within our views. Since right now our logic is pretty simple, it might seem like that's not an issue. But as we grow in complexity and functionality, this might lead to several problems. We'd like to get any non-view related logic out of the view classes in order to reach a more organized and maintainable structure.

Once the user clicks on a movie, they should be redirected to the details screen. The details screen should present the following movie data: name, poster image, backdrop image, list of genres, overview, and release date.

We currently have the splash screen only for ensuring that we have the genres cached before requesting the upcoming movies. However, we came to an understanding that ​splash screens are evil​, so we want to get rid of it. We want to make sure we still properly show the movies genres in the movies list, though.

The list of upcoming movies currently only shows the first page of content. We want to make sure the users can see all the content by automatically requesting and showing the next pages as the user scrolls down through the movies - in an infinite scroll manner

Whenever the orientation changes, we're unnecessarily reloading the list of movies. Loading the list should not be tied to orientation change events.

The ​TmdbApi​ class has some architectural issues that we would like to address.