Use Bottom Navigation according to Material spec

[camtheman256]

Because the ManaTEAMS app has few screens to switch between, a bottom navigation bar would better suit the app. This is a new addition to the Material spec and I'm not sure what its implementation would look like in code. This type of navigation tends to be used with apps with 3-5 screens; ManaTEAMS has 4.
Here is the design spec for bottom navigation bar and here is its behavior.

[patil215]

Does the bottom navigation bar remain on the screen even once a user has "drilled deeper" into one of the tabs? For example, if a user was to click a class in the "Courses" page to view assignments, does the bar disappear or remain on screen?

IMO, the bar should disappear - since it's a little more navigationally confusing to be able to jump between each section of the app even when drilled deeper into a section - but I think that would lead to more confusing behavior than the current navigation drawer that stays hidden at all times.

I'm a little perplexed by Google's decision to switch back to the navigation UI of 2008 - though the app states "(alternative: a persistent navigation drawer accessible from anywhere in the app)", so this might not be that necessary of a change to fit within Material spec.

[camtheman256]

I would imagine that the bar should disappear; there isn't really anything in the Material spec to dictate its behavior. It would seem irrelevant to have a bar present while looking at course-specific grades.
Yes, it is a bit more confusing than a navigation drawer, and there's nothing wrong with using one, it's just bottom navigation could help simplify the design of the manaTEAMS app. It's up to you if you want to try and implement it. If you need some direction on the programming half, I found this article.