Abstract
The controversy about the burger button triggered in 2013 is that it is difficult to know what the hamburger button itself means and that it is difficult to predict what will happen when the button is clicked, Could. This controversy was found to be fundamentally out of touch, and it could be seen that it caused conflict with Apple's navigation structure with iOS. Therefore, in the case of Apple, it is often used in the form of a tab at the bottom instead of using the slide menu, but it is preferable to be used for the purpose of the hamburger button. I've looked through a variety of documents and found that the amount of content you want to offer on your app or the web is large, and there are five or more categories. And if a sub-category needs to exist in the main category like a large shopping mall, the hamburger button could provide the best UI. Apps and webs that can be curated, such as news and pinterest, are better used to enhance the search filter than to place a hamburger button, and for apps or the web that has a longer amount of content on a page Scrolling was available as an alternative to the burger button. In other words, depending on the amount of content to be provided, it is possible to decide whether to use the hamburger menu from the time of designing the information architecture.