ayanova/devdocs/todo.txt

@@ -47,7 +47,18 @@ All platforms and browsers
 	- Check about page localization code, is it firing in the right place because on Edge and iPad firefox it didn't show localized at first until a refresh so it fetched the keys but didn't display properly
 	- Calendar on iPad in two occasions with ff and opera the calendar date could not be selected until a time was changed then the date worked.  Before that it would always stay the same no matter what selection was made and the UI would not show a change on select or press of date either.
 	
-	- FORM MENU
+	- FORM MENU / NAVIGATION BAR / OVERFLOW MENU
+		- According to official specs:
+			- Nav bar should show where you are in the title part
+				- Name of form or object in nav bar itself, possibly an icon also indicating the item in question?
+			- It should change colour when in a sub screen and not the main screen with only a back button
+				- I like being able to go anywhere any time from the navigation menu so I'm not sure I can support only a back button, but I can see having a back button 
+				- I like it changing colour to indicate it's become contextual in the overflow and options
+				- So, when in any main view it's standard coloured but as soon as you're editing a record or in any form that demands a contextual menu item then it flips to black
+			- It should have the most used features surfaced adn the least in an overflow 3 dots menu to the far right.
+				- Search, save, whatever is most used on that form
+				- As the screen gets smaller items progressively move into the overflow until, at the smallest they are all in the overflow
+		- So what I'm reading is I should enable only one app bar at the top and morph it for states where appropriate
 		- Try to make a menu in the top bar APP.VUE and if not then explore options inside the form
 		- Is a fab appropriate for save and new the most common options??
 		- See the best way to do this, either in the very top bar or in somethign in the page itself